How to write a website specification document

How to write a website specification document

A talk about how to write a website specification document, something which is an important part of any website project.

31af50af29856a3e6734bdae0a0d68cf?s=128

Mark Wilkinson

March 26, 2019
Tweet

Transcript

  1. How to write a website specification Mark Wilkinson Co-founder &

    developer at Highrise Digital https://highrise.digital @wpmark
  2. “What is a rough price for new house build?”

  3. “A detached house, 4 bedrooms, en-suite bathroom, garage?”

  4. “There is only 1 en-suite, what about the other bedrooms?”

  5. What is a website specification?

  6. “ A document that articulates the project’s goals, objectives and

    tactics. It should outline constraints, such as budget, deadlines, or technical restraints. It can also include project details such as the team involved, for example, stakeholders or points of contact.
  7. But, why?

  8. None
  9. None
  10. Giving clarity

  11. What to include

  12. Overview Team Goals Phases Content Design Functionality Accessibility Browser support

    Hosting Ongoing maintenance Assumptions Milestones Deadlines Budget
  13. None
  14. Overview What problem is being solved? High-level project scope Target

    market
  15. The team

  16. Goals Set 2 or 3 SMART goals Everyone should be

    clear on these
  17. Phases

  18. Content structure

  19. https://www.gloomaps.com/

  20. Content [post] types Taxonomies Page templates (layout)

  21. Design

  22. Functionality How the site actually works Detail, detail, detail -

    contact form example
  23. Search SSL eCommerce Users - roles/caps Performance & speed Multi-lingual

    API integrations - CRM
  24. Accessibility (a11y)

  25. None
  26. Browser device support Analytics Who are the users?

  27. None
  28. Hosting

  29. Ongoing support/ maintenance

  30. Assumptions

  31. Milestones & deadlines

  32. Mark Wilkinson Co-owner of Highrise Digital WordPress developer @wpmark @highrisedigital

    https://highrise.digital
  33. Questions ? Although not necessarily answers! @wpmark

  34. #askhighrise