What would the going rate be for a web dev company be to put a website up using wordpress?
4/18/2009 8:13:21 AM
why don't you just do it yourself? wordpress isn't hard at all to install.
4/18/2009 8:16:46 AM
already paid for it. just saw the site under development and saw that its wordpress.= me not happy[Edited on April 18, 2009 at 8:22 AM. Reason : .]
4/18/2009 8:21:56 AM
Wordpress is just a CMS, just like Drupal, Joomla, EE, or anything else. Don't get all bent out of shape about it. You can do a ton of things that you could never do with a static site.If anything, having the site have a WP backend helps YOU maintain it without having to call your designers every time you want something changed.Although if you didn't know it was going ot be done in WP and you didnt know each of the stages ahead of time, your designers aren't keeping you in the process, and that's bad.
4/18/2009 9:02:10 AM
i use WP for all my basic sites, and i've never had a client who cared. I always explain to them what a CMS is, and that WP is a good and simple CMS that will allow them to keep the site updated by themselves, and that's all that's mattered to them. It still takes skill to customize or change a template or add features to the site. You can't get angry at a developer for doing something the "easy way" (wordpress instead of a more complicated CMS), as long as it gets the job done that you asked for.
4/18/2009 9:14:34 AM
4/18/2009 9:57:49 AM
You should not pay someone to set wordpress up for you. Wordpress has got it down to a science at this point to where you basically just upload the contents of Wordpress to your website and click an install button.Themes and additional plugins also auto install. Save time/money and do it yourself.
4/18/2009 2:52:23 PM
If he paid someone to just set up a WP install, then yeah, that's dumb, he got hosed. If the developer is simply using WP as the CMS, there's no problem with that.[Edited on April 18, 2009 at 2:57 PM. Reason : ]
4/18/2009 2:56:42 PM
if you're going to pay someone to setup/install/design/build a website for you, as long as the site, in the end, meets all the requirements and demands you laid out, then it doesn't matter hat CMS or backend was used. If the designer takes your requirements and says "hmm, ok, i think i can do all of that with a Wordpress install", then he should use wordpress. If he says "well, this is getting more complicated. maybe I should go to something more robust like Drupal", then he should use drupal. It's up to the designer if he wants to charge you less for Wordpress site than a Drupal site because of the ease of installation.But, if the client agrees on a price and the designer creates a website meeting the requirements, then the client has no right to cry over the price because he happens to know that WP is easier to set up than Drupal or Joomla or whatever. That should be taken care of in the negotiation. I think ti's perfectly reasonable for the designer to say "i'll do a wordpress site for $1000 and it will have features A, B, and C. However, if you want to add features D and E also, we'll have to use Drupal and it will be $1500." If that is not part of the negotiation, though, and the designer decides all the requirements can be handled in wordpress, then c'est la vie. In this case, KiLLm3rEd appears to be knowledgeable enough to know the differences in various CMSs, and should have asked what the designer was planning on using, and asked for a lower price if he felt it was too high for a WP install.
4/18/2009 3:47:45 PM
4/18/2009 6:51:15 PM
what if they don't want to have to maintain it or pay to maintain it?a custom backend is generally a lot more hackproof than a wordpress install that hasn't been updated in a while
4/18/2009 8:37:38 PM
that's quite a generalization......i don't think you can ever say "a custom backend is generally more secure" than anything
4/18/2009 8:43:25 PM
How is that quite the generalization?People make armies of bots to search for and exploit un-updated CMSes.People do not generally make armies of bots to search for and exploit some random one-off site.If it's kept up to date then yes, it's PROBABLY more secure than some custom thing.Now, if you got some random dude with a vendetta against your site then it's all up in the air.
4/18/2009 8:52:43 PM
ok, well then i guess I would say there is a difference between "secure" and "hackproof". If you include armies of bots searching out vulnerable CMS installations, then ok - i'll buy that an out of date CMS installation is insecure. but as far as hackability, I would bet that random Joe Schmoe, custom-built backends, if attacked specifically and individually, would generally be easier to crack than then professionally built, commercialized CMSs.
4/18/2009 9:45:16 PM