Forum Moderators: open
the front page would be the blog, which I would want run by wordpress.
the rest of the site however [the non blog posts] I'd like to run outside of wordpress to avoid the overhead and have more control. I'd still like to use the same layout used from the main page.
Is this possible? Is it a bad idea for any reason? how would i go about that in the most efficient manner?
If you wanted your home page static and WP in a /blog directory, that would make more sense, but once WP is running the home page, I don't see much advantage to not use it elsewhere.
You can always build additional page templates that you assign to non blog pages, so you have a fair bit of control in that respect. It only really gets touchy if you have forms and AJAX and highly interactive stuff on particular pages.
>>bad idea for any reason?
- Two templates to maintain will make it that much harder every time you want to tweak your layout.
- You'll have to keep manually integrating site navigation every time you change that.
is there any easier solution I'm looking over to run news on the main site without filtering all of our content through whatever blog/cms uses that?
I didn't care for it, but I've done a hybrid solution where you don't have any truly static pages, but you generate them using simple PHP includes for the templating. At least that way you only have to make changes in two places.
Of course, you can reuse the same CSS files, so any CSS changes propagate through both sets of pages. But when you have to change the HTML, you need to change your WP templates and your non-WP templates.
I "inherited" a site where everything was thrown into / and it's a huge mess trying to figure out what script owns what file. And having /img /image /images /uploadimages is fun too.
In the future if you want to "dump" wordpress all you have to do is get rid of the /blog/ directory and not worry about what files off of root are needed by other programs.
I "inherited" a site where everything was thrown into / and it's a huge mess trying to figure out what script owns what file. And having /img /image /images /uploadimages is fun too.
Ha! Me too. Presumably disgust plans on better organization than that and I think he plans to segment out the non-WP parts in their own subfolders, so it's not that hard to maintain.
any problems with that approach I should look out for?
If you have custom apps and such running the other pages, that's the only reason I wouldn't have it all under one system.
Finally, even if you do that, I would still have the front page running under WP.
Problems to look out for with the approach you mention? The ones that I mentioned previously: maintaining your site will involve extra steps and will increase the effort required to maintain a consistent look and feel as your site evolves. And you'll give up being able to leverage WP throughout the site (say, "related pages" or site search plugins).
Other than that, no technical problem with what you suggest and lots of people *do* indeed do it that way. I just don't and lorax doesn't, but we're just two guys who like to keep our lives simple (I was going to say lazy, but didn't want to speak for lorax).
[edited by: ergophobe at 1:26 am (utc) on Oct. 12, 2009]
:)
