Saliem Talash

Worked example A site can look ready while the person who owns it still cannot make the next ordinary change. The useful test is specific: if the shop changes its Saturday hours on Friday afternoon, can the owner update the public page, check the result, and know where enquiries went? Below is a complete fictional demonstration of the Website Project Workbook. The shop, people, addresses and outcomes are illustrative. This is not a client case study or a claim that a real site passed these checks. 1. Write the brief as a visitor task Project: a small neighborhood flower shop website. Audience: someone nearby who wants to see the shop's opening hours, understand what can be ordered, and ask about a custom arrangement. Primary visitor task: find accurate hours and send an enquiry without guessing whether the shop is open. The brief should also say what the site does not do. In this example, it does not promise same-day delivery, take payment, or confirm custom orders automatical...

Written by Saliem Talash with AI assistance. A website handoff tends to fail in the spaces between tools. A brief lives in email, launch checks in a chat, and the instructions for the next editor in somebody's memory. I built the Website Project Workbook to put those decisions into one document an owner can keep. The workbook is a small HTML file, not an online account. Open it in a desktop browser and fill in the fields. There is no installation, sign-in or server-side storage. That choice has a tradeoff: the workbook cannot silently save your answers. You must choose Save progress before closing and keep the downloaded progress file. I state that prominently in the interface because a save button should never leave users guessing. Four parts of one handoff The first section is a project brief : the project's name, intended audience, the visitor's main task, scope and evidence. The aim is to make the purpose of the site specific enough to test. “Make it modern” is a ...