I discovered early on that coding websites was easy. Getting a client to actually know why, and what type of site they need, is what requires the work. I have a few Q&A type docs that I send out to clients before I build, wire, set-up, purchase or even fix anything. Plz note that I did not reformat it for Steemit. It is only intended to use as a resource to make your own Q&A. You can steal it if you want, but my business model may not help you.
Planning:
- What is the purpose of this website?
- Who will use this site?
- What are the users’ computing environments?
- Who owns and authors the information on the web site?
Analysis: - What tasks do the users need to perform?
- What information is useful to the users?
- What process considerations must be made?
Design and Development: - How many pages will the site include?
- How will pages be organized?
- What type of structure is appropriate for the content?
- How is the content best presented for use?
- What file naming convention will be employed?
- What will the folder structure look like?
- Will all standards be applied throughout the development cycle?
- What multi- or mixed- media will contribute properly to our site?
- Can we have access without limiting usability?
- Will we reach, local, state, national, or international audiences?
Testing: - Are our pages W3C and HTML5 compliant?
- Is the site content correct? Spelling?
- Does it function? Flow?
- Is navigation clear?
Maintenance and Implementation: - Can we attract users and will they “revisit”?
- How is the site updated?
- Who is responsible for content?
- Who is responsible for structural updates?
- Can we notify users of our content updates?
- Will the site be monitored?
- How is the site published?