Reinforcing that we don’t want to design websites, we want to implement websites to support our content distribution strategies with minimal configuration, customization, and deployment timelines. Aside from some specialty applications like event calendars, FAQs and photo galleries, we’re building around a few basic engines. The engine choices for a particular site are driven by a few brief questions:
- What is the purpose of the site?
- What is the target audience?
- In the case of sites built to support fiction projects:
- What real world component is the site supposed to emulate (a business, a media outlet)
- How dynamic will the site’s content be?
- Will the site’s content be required to follow or synch to a specific timeline?
- Will the site require user registration?
- Will parts of the site be restricted to specific users or user groups?
- Will the site have an ecommerce connection?
- Does the site have any specific requirements for look and feel?
Once these questions are answered, we apply them to a grid and drill-down process to determine the technology.