3 ms·

> wait, what use case? Blogging > toward the OP's use case No, they have moved toward general purpose site building, not focused on _blogging_

jrochkind1 5y ago
I thought OP was saying that they did not use WP for blogging, from the start, which always felt like a hack since WP was focused on blogging, but OP made it work anyway. Did I misunderstand? I don't think so. OP says: > I build websites for a living. Lots of them. These websites are designed by a team of designers who design complex, bespoke, heavily branded layouts. I take those designs and my team of developers and I turn them into corporate websites, generally for medium sized industrial clients. > Sometimes the websites are big brochures, sometimes they have complex functionality. Sometimes both. They run to hundreds of pages and posts, composed of multiple layouts, templates and using, typically, 20 or more discrete modules, each configurable in multiple ways by the end user when the sites are ultimately turned over for the marketing staff of these mid sized companies to edit. > Many of them use WordPress as a CMS. From the beginning this has felt like a hack OP does not describe what they do for a living as blogging or providing blogs. I see OP saying that they always used WP as a general "CMS", for "websites" that may be "big brochures" or "have complex functionality", which are not mainly blogs. Right?
- dabernathy89 5y ago
  Sorry - I thought you were referring to the parent comment (https://news.ycombinator.com/item?id=30172268 https://news.ycombinator.com/item?id=30172268). To answer your question, though - I believe OP's major concern is that the direction WP is heading gives the _client_ more control over the website structure and design rather than the original designers & developers. Making it less useful for their more rigid requirements and corporate environments.

jrochkind1 5y ago

I thought OP was saying that they did not use WP for blogging, from the start, which always felt like a hack since WP was focused on blogging, but OP made it work anyway. Did I misunderstand? I don't think so. OP says: > I build websites for a living. Lots of them. These websites are designed by a team of designers who design complex, bespoke, heavily branded layouts. I take those designs and my team of developers and I turn them into corporate websites, generally for medium sized industrial clients. > Sometimes the websites are big brochures, sometimes they have complex functionality. Sometimes both. They run to hundreds of pages and posts, composed of multiple layouts, templates and using, typically, 20 or more discrete modules, each configurable in multiple ways by the end user when the sites are ultimately turned over for the marketing staff of these mid sized companies to edit. > Many of them use WordPress as a CMS. From the beginning this has felt like a hack OP does not describe what they do for a living as blogging or providing blogs. I see OP saying that they always used WP as a general "CMS", for "websites" that may be "big brochures" or "have complex functionality", which are not mainly blogs. Right?

dabernathy89 5y ago
Sorry - I thought you were referring to the parent comment (https://news.ycombinator.com/item?id=30172268 https://news.ycombinator.com/item?id=30172268). To answer your question, though - I believe OP's major concern is that the direction WP is heading gives the _client_ more control over the website structure and design rather than the original designers & developers. Making it less useful for their more rigid requirements and corporate environments.