I see where this idea is coming from as someone who had loathed doing Wordpress client projects and I’m not shitting on AI. You can see from my comments that I use AI a lot. But you’ve got to edit presentation material into a human voice. It’s your brand. It’s my first impression of you. It’s lazy.
Claude has written so many of the phrases in just the first handful of paragraphs for me in written material so often that I had to make a writing rule which is almost exclusively: here’s a list of phrases you may never use, scar tissue and all.
I wish you luck with your project OP, but I couldn’t get past the first page.
I read through the page, and thought it was precisely what it needed. It very adequately described its usage, differences, and it's key points.
This isn't a blog post, this is a homepage, and as a homepage it is selling its idea to its specific audience, which is developers who use WordPress as a CMS and deplore the rest of the tedious stack. Even if it's AI generated, its obviously been human-edited rather well.
OP, I thought it was well-done, great work, makes sense, I'll have to dig through the changes to see if its worthwhile, but I love the concept and limited attack vector size (a lot of WP security bugs are from their parsers and server-side rendering).
So a one-man show + Claude that forked the repository and removed a lot of code in one week[0]. With all respect for the presumably good intentions, why should someone who relies on WordPress use this if there's no solid maintenance story behind it yet and no obvious path to sustainability.
I see where this idea is coming from as someone who had loathed doing Wordpress client projects and I’m not shitting on AI. You can see from my comments that I use AI a lot. But you’ve got to edit presentation material into a human voice. It’s your brand. It’s my first impression of you. It’s lazy.
Claude has written so many of the phrases in just the first handful of paragraphs for me in written material so often that I had to make a writing rule which is almost exclusively: here’s a list of phrases you may never use, scar tissue and all.
I wish you luck with your project OP, but I couldn’t get past the first page.
I read through the page, and thought it was precisely what it needed. It very adequately described its usage, differences, and it's key points.
This isn't a blog post, this is a homepage, and as a homepage it is selling its idea to its specific audience, which is developers who use WordPress as a CMS and deplore the rest of the tedious stack. Even if it's AI generated, its obviously been human-edited rather well.
OP, I thought it was well-done, great work, makes sense, I'll have to dig through the changes to see if its worthwhile, but I love the concept and limited attack vector size (a lot of WP security bugs are from their parsers and server-side rendering).
So a one-man show + Claude that forked the repository and removed a lot of code in one week[0]. With all respect for the presumably good intentions, why should someone who relies on WordPress use this if there's no solid maintenance story behind it yet and no obvious path to sustainability.
[0]: https://github.com/gerharddt/dmpress/commits/main/
It says right at the top of the page “Pre-release: DMPress is at 1.0.0-beta.80 and is not yet recommended for production use.”