CostThe development cost is a function of the complexity of the project and the CMS that we are using. The range is somewhere between 45 and 160 hours for a moderate sized site ( 50-200 nodes, moderate functionality/interactivity ). The hourly rate depends also on the CMS, the designer ( see notes ) and if there are any fancy things that require specialized programming. But should be in the range of $50-$100. That means on the low end $2,500 and $15,000 on the high end. There is probably also a $500 - $2000 solution ( possibly using Wordpress or similar product ) but this requires designing to a preexisting template. Development Process ( medium sized site ) Planning ( 1 day, 4 hrs ) Determine requirements ( see questionnaire ) Chose a CMS Choose a web layout ( theme, template )
Build Prototype ( 1-2 weeks / 10-40 developer hours ) Designer should produce a basic design(s) as .psd template ( or HTML with images if possible ), Editor should create an initial site outline. Developer should setup the CMS, create test domain, user accounts, email and construct the initial template(s), and create stub content Editor should add initial content to the CMS All QA Review prototype with client identify design/technical/content issues scope next round determine delivery date for next revision ( determine work hours )
Alpha ( 1-2 weeks / 10-40 developer hours ) Designer should revise graphics, font styles, . Developer should add any functional components, revise templates and CMS configuration. Editor should review/produce next rev of content All QA Review version with client determine final list of updates/bugs/enhancements scope/schedule
Beta ( 1-2 weeks / 10-40 developer hours ) Designer should finalize graphics Developer should address bugs, setup analytics, and SEO setup Editor finalize content All QA. Soft launch to client and friendlys
Production (1-2 weeks / 10-20 developer hours) All address and review feedback/bug reports ( on daily/weekly basis) Developer monitor analytics and error logs, address issues, SEO review Final review with client, and approval to go into maintenance mode.
Maintenance ( monthly / 2-10 hours ) Review logs, analytics Review SEO
Choosing a CMSThe first step is to determine which Content Management System to use. There are several choices from extremely simple to powerful and complicated. But a CMS is pretty much mandatory for clean and controlled development ( even if there is extensive Flash within the site ). The answers to the following should assist in choosing a CMS. ( Of course if a client has a legacy system or a preference this would be unnecessary ). Questions Users How many end users will there be ( optimistically ) ? Can users login to the site? Can users contribute content? What are the primary user cases ? Finding information about a product, service, organization Purchasing Collaboration/Forums Other
Editors
-
How many editors of site content? How technically proficient are they? How frequently will edits be made?
Content What different content types are there? ( e.g. Pages,Blocks,Blog Entry,Newsletter,Product,Media, Video ) What is the estimated amount of content? What is the intended content growth rate?
Design How many different layouts are there Is the template fluid or fixed width Are there dynamic menus How does the design degrade for small screens How frequently will the design be updated
Technical What is the ISP? Is the setup the developer's responsibility? Is there a current site to be migrated Is there a current content/user database Are there third party API's or databases to be interfaced (e.g. Facebook,Twitter,Blogspot,Flickr,YouTube,Salesforce,AdWords,Google Ads … )
Budget What is the project budget for development What is the monthly maintenance budget
NotesThe biggest issue in development is the Design-Developer battle. Where the designer feels cheated because the product doesn't look like the design, and the developer has to do a lot of extra work to satisfy the designer. The solution to this problem is to realize that both are designers and developers and the submission of both to : Often the designer is unwilling to make compromises to facilitate development and expects a literal translation of static design into a dynamic medium, this can be reinforced by the client who has likely seen the static design. This seems course de rigueur, but it does add to the development time and headache, and expense, as we make 100's of little images for everything from buttons to titles. If the design is templatized up front the development can proceed more efficiently. There are projects, where graphic design and web development and content development are equal. |