Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
4.0 KiB
You write the words for one page of a website for this business.
Business: Nordvik Bygg About: We survey old buildings, draw up rehabilitation plans, handle the permit application, and do the building work with our own carpenters plus subcontractors for electrical, plumbing and scaffolding. Contact: Ingrid Nordvik ingrid@nordvikbygg.example Language to write in: en
Everyone the site serves:
- building-problem: A housing board or private owner with a problem with a building - wants: Someone to come and look at it, and tell them what it would cost to fix. Handled by project_managers. Stages: open -> surveyed -> quoted -> won -> lost -> declined.
- known-project: An owner who already knows what they want built - wants: Drawings, a permit application and a price. Handled by project_managers. Stages: open -> surveyed -> quoted -> won -> lost -> declined.
- subcontractor-application: A trade firm that wants to be on our list of subcontractors - wants: To be approved as a subcontractor. Handled by project_managers. Stages: open -> checking -> papers_requested -> approved -> rejected.
- job-application: A carpenter or apprentice asking if we are hiring - wants: To apply for a job with us. Handled by project_managers. Stages: open -> interview -> hired -> declined.
- site-report: Crew on site, ours or a subcontractor's - wants: To report a hazard, near miss or wrong materials before it is forgotten. Handled by safety_officer. Stages: open -> closed.
The page: questions/received/building-problem.yaml It is a page shown right after someone has sent a form. Say who reads it, when they answer, and what happens next.
Below is the page as JSON. Every value is a slot that says what to write there. Return the same JSON with every slot replaced by your words. Keep every key exactly as it is. A slot left as it is counts as no answer.
Rules for the words:
questionis a question the reader could ask themselves.- A heading says what the reader gets, in the reader's own words, and must work without its description.
- Lead with what a thing enables. No negations in headings. No trade jargon the reader would not use.
- Descriptions are one or two short sentences. Labels and buttons are a few words.
- The button says what pressing it does; the encouragement says what happens next or how little it takes; the form's guidance line says what to have ready. Placeholders are example answers in the reader's words.
- An icon is one name from this list, chosen for what the reader is doing, or empty: house, building-2, store, school, map-pin, route, footprints, trees, leaf, snowflake, sun, users, user, user-plus, user-check, baby, heart-handshake, hand-helping, handshake, smile, mail, phone, message-circle, megaphone, bell, send, inbox, alert-triangle, siren, shield, construction, hammer, wrench, ruler, package, truck, car, bus, train-front, bike, calendar, clock, file-text, clipboard-list, receipt, wallet, coins, banknote, credit-card, key, lock, search, star, gift, shopping-cart, lightbulb, flag, thumbs-up, check-circle, briefcase, stethoscope, activity, camera, pencil, refresh-cw, list, layers, vote, scale
- Write the way people in this trade and country actually speak.
{ "back": "<WRITE: a button, one to three words, saying what pressing it does>", "description": "<WRITE: one or two short sentences>", "next_description": "<WRITE: one or two short sentences>", "next_heading": "<WRITE: a heading, at most eight words, saying what the reader gets>", "question": "<WRITE: the one question this page asks its reader>" }
Reply with the JSON object only.
=== REPLY ===
{
"back": "Back to home",
"description": "Thanks for telling us about the building. We've received your report and logged it.",
"next_description": "One of our project managers will look over what you've sent and get in touch to arrange a site visit, usually within a few working days.",
"next_heading": "A project manager will call you",
"question": "What happens now that we've sent our building problem in?"
}