|Add wordpress to an existing website|
Updating from pure HTML to a wordpress CMS
| 6:16 pm on Jun 23, 2012 (gmt 0)|
Good afternoon all,
So Im in a situation where I have a website in pure html and the client wants WP added.
My concern is there's a LOT of content on the site as it stands... something like 150pages worth.
I'm somewhat lost because adding a CMS is usually the first thing I do, so I need to know if I install WP, what happens to the existing content?
On a side note, there is not theme that "needs" to be integrated. The plan is to install a generic theme once WP is online. The concern is just to preserve the content.
| 6:42 pm on Jun 25, 2012 (gmt 0)|
It depends on the existing content. As long as it does not invoke /index.php, you should be able to do just fine.
By default, if the page requested is an actual file, WP doesn't actually get invoked.
| 6:48 pm on Jun 25, 2012 (gmt 0)|
You need to configure the webserver so that URL requests for the old pages and for images and CSS/JS are served from the static files and URL requests for the WP pages are served by the wordpress PHP script.
That could be as simple as putting WP in a folder or using extensionless page URLs in WP and retaining whatever extension you currently use for the static pages.
Think about this in terms of requested URLs and not as folders and files inside the server.
| 2:10 am on Jun 30, 2012 (gmt 0)|
I don't see a problem. I'm doing this with a static html site (all files have .htm extension). I've installed WP in a /blog folder I created, and all WP files in in that folder. Everything stays separate from the pre-existing site pages. Even if I had installed WP in the root directory, there probably would not have been a problem, since the file extensions are different--as long as the names of the two CSS style sheet files are different.
| 2:39 am on Jun 30, 2012 (gmt 0)|
Lots of choices:
You can install WordPress in the webroot and it should ignore existing files. (set up the permalinks however you'd like. the rewrites should ignore an existing file. Make sure this is the case for your server) where you can serve the existing .html files and WordPress side by site.
You can install in a subdirectory, ex. domain.com/blog. Then link as needed into the static site's navigation.
Or you can import the .html pages into WordPress, serving with the same .html extension for the .html *pages* via plugin, adding the blogging functionality. (this if they'd like to manage the whole site from one place. the blog related posts/categories/tags related pages won't necessarily have the .html extension unless you config that way.)
In the first two cases, theme WordPress to match-up with the main site, in the last, it's a theme for everything on the site. Lots of choices for you.