Not meant to diminish your efforts, but: If the customer explicitly wants Wordpress (which could be the case because of the quiet big community around it, availability of ready-to-use plugins etc.) then this isn't solved by just providing another CMS, is it?
Thanks for raising this point. It's ultimately up to the individual developer / team to have the conversation with the customer to understand their core business needs and then determine the best solution. There may cases where a client insists on WordPress for reasons that can't be overcome. However, in the vast majority of cases, the end-needs of the client don't truly "require" WordPress. Clients generally overvalue plugins as a means to an end that can be solved just as easily with a non-WordPress plugin or light custom solution. Plugins aren't a free lunch – they come with their own baggage of security issues, updates, dealing with 3rd-party code, etc. In most cases, for Ruby developers, WordPress requires significantly more time and complexity to setup and maintain than something that drops into an existing Ruby app... that's why tools like ButterCMS exist :) Hope this helps!
The problem is that wordpress is not built for the use it sees in many cases, where a more customized webapp nightmare starts, your solution is awesome
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Not meant to diminish your efforts, but: If the customer explicitly wants Wordpress (which could be the case because of the quiet big community around it, availability of ready-to-use plugins etc.) then this isn't solved by just providing another CMS, is it?
Thanks for raising this point. It's ultimately up to the individual developer / team to have the conversation with the customer to understand their core business needs and then determine the best solution. There may cases where a client insists on WordPress for reasons that can't be overcome. However, in the vast majority of cases, the end-needs of the client don't truly "require" WordPress. Clients generally overvalue plugins as a means to an end that can be solved just as easily with a non-WordPress plugin or light custom solution. Plugins aren't a free lunch – they come with their own baggage of security issues, updates, dealing with 3rd-party code, etc. In most cases, for Ruby developers, WordPress requires significantly more time and complexity to setup and maintain than something that drops into an existing Ruby app... that's why tools like ButterCMS exist :) Hope this helps!
The problem is that wordpress is not built for the use it sees in many cases, where a more customized webapp nightmare starts, your solution is awesome