3 ms·
You could ask the same question about any application that uses a database. The answer is you typically don’t do things that way. If all you need is a static s
by orev 3y ago
You could ask the same question about any application that uses a database. The answer is you typically don’t do things that way.
If all you need is a static site generator with code in git, then go ahead, however the use for Wordpress is an audience who needs a full application to manage a site.
- bsder 3y ago> the use for Wordpress is an audience who needs a full application to manage a site. The use case for WordPress is businesses who don't really need a website at all but everybody demands that they have one and they want to outsource running a website so you can blame somebody else when it gets hacked into and can tell your marketing and sales department go bother somebody else about the website. <Raises hand>. Anybody who actually needs an application to manage their site has staff and they don't use WordPress.
- h0l0cube 3y ago> needs a full application to manage a site. AFAICT it’s not that. It’s that most shops want the ability to edit content without a developer. But such a requirement doesn’t mandate that data lives in a database vs something like, say, a set of plain-text files, that would be amenable to version control and diffing