Installing WordPress in a subdirectory with static HTML sites

I did a quick search on here and Google and can’t really find something helpful. This question here doesn’t fit my bill either.

I create websites for small business/startups/persons that rarely change content. With my HTML/CSS/PHP knowledge I prefer to build the static pages from scratch so that I can control every single aspect of it (I am aware I could write WP themes but I see it rather redundant and an overkill).

I simply don’t like to use WP unless I actually need a CMS, not a website builder.

For my clients who need a blog with a sort of latest news section (or other content), I prefer to setup a WP in a sub-directory and use custom PHP scripts based on WP API to grab posts and media in the manner I like in my HTML pages.
It may be a bit tedious, but I find the results pleasing for me.

Is there something wrong with this approach? Or any ideas how to improve it, without using WP for powering the full site?

5 Answers
5

The reason to follow WP standard is for another DEV to pick it up later, or to transfer it without issue.

The problem is content. I could easily make a site from pages regardless of your plugins/themes if the database was set up in WP. But you are saving content differently so now I have to convert the data to WP tables, write rewrite rules and 301’s. That is a lot of overhead.

Why not do it all in WP to begin with? Your client might want to move, and you could help them, making yourself look like a champ.

Leave a Comment