Every kind of Kit page

An explainer page can hold up to four hands-on blocks, and a lesson page (public name: Lesson Kit) up to twelve, laid out as sections that run from a hook through the idea, worked examples, practice and a check to a cheat sheet.

The blocks are: a number line you drag a marker along, a function graph with sliders, a simulation you can play and scrub (a thrown ball, a pendulum, a falling body and more), a 3D model you can turn and zoom with labelled hotspots, a quiz, a set of flashcards, and a worked example that reveals one step at a time.

Every block can be used with the keyboard and still reads as plain text with JavaScript off. A 3D model is copied into the page when it is published (up to 1 MB), so the page never loads anything from elsewhere.

Quiz answers and known flashcards are saved on the link and shared by everyone who opens it; if saving is not available, the block still works. The same blocks are available in Playworks games, and a finished 3D Lesson Scene game can be exported as a lesson page.

A course page (public name: Course Kit) puts a whole short course on one page: a welcome with the course map, two to twelve lessons, and a certificate at the end. Each lesson ends with a short quiz, or with an "I've finished this lesson" box to tick when it has no quiz.

A lesson counts as done once every quiz answer in it is right, and the learner can try again as often as they like. The course map opens with a "Your progress" card (the percentage done, how many lessons are complete and a progress bar), shows each lesson as Not started or Complete, and marks the next lesson to do as "Up next". When a lesson is done, its end turns into a "Lesson complete." panel with the course tally.

When every lesson is done, the progress card offers a "Get your certificate" link, and the certificate unlocks: the learner types their name and the date and uses their browser's Print command, and only the certificate prints, on one landscape page. Nothing the learner answers or types is saved or sent anywhere, and the page says so; closing or reloading it starts the course again.

Every look draws its own certificate, from a classic diploma to an engraved gold frame or a bright sticker.

On a published link the browser's Print command prints the certificate from anywhere on the page, so there is no need to scroll back to the top first.

A puzzle page (public name: Puzzle Kit) holds crosswords and word searches, on their own or inside a lesson or explainer for vocabulary practice.

The agent only lists the words and clues: Yardmaster lays out the crossword, numbers it, and places the word search so that every word can be found exactly once, and it refuses a puzzle that would be unfair (a word that cannot fit, a word listed twice, or a word hidden inside another) with a plain explanation.

The grid fits a phone with no sideways scrolling, every clue is in a numbered Across and Down list, and the answers sit behind a Show the answers fold-out. Puzzles are playable on the page: readers type crossword answers, check and reveal them, and find words in a word search by dragging, tapping or using the keyboard.

The page also prints as a clean puzzle to solve on paper, and puzzle pages published before play arrived stay printable until the agent republishes them. Nothing a reader does is saved or shared with anyone else.

A page can hold a calculator for things like a price estimate, a payback check or "what if we add 10 more sessions". You move sliders, type numbers, pick from a list or flip a switch, and every result updates at once, with a note showing how far the main results have moved from the starting values.

Ready-made scenarios (such as Light, Typical and Intensive) sit one tap away and line up in a side-by-side table, and a small chart shows how one input changes the result.

A result that cannot be worked out, such as dividing by zero, says "Not defined" instead of showing nonsense. Yardmaster checks the numbers before the page goes live, and with JavaScript off the page still shows the starting values. Nothing you change is saved or shared; the next person to open the link starts from the same starting values.

A project page (public name: Project Kit) shows where a piece of work stands. It can hold a roadmap (a dated plan of bars and milestones, with every date written out), a status board (columns of cards such as To do, In progress and Done, with owners, due dates and anything that is blocked) and a risk register (each risk scored by how likely it is and how much it would hurt, labelled Low, Medium, High or Critical, with a grid that shows them at a glance).

The page never guesses today's date: the agent says what date the information is true, and the page shows an "As of" date, draws a line there on the roadmap and marks cards past their due date as Overdue.

Readers can look but not move cards, and nothing they do is saved, so the agent can update the same link with a fresh version at any time. The one exception is a board the agent makes movable (see Sign-offs, ranked votes, Q&A boards and movable cards). Clicking a stat tile such as "High risks" narrows the register to the matching risks. On a phone the roadmap, board and register stack into easy-to-read cards, and every status is written as a word, never shown by colour alone.

A comparison, brief or report page can hold a decision matrix (public name: Decision Kit): two to six options scored out of 10 (or 5) against two to ten things that matter, such as cost, travel time or weather. Each of those things has a weight slider.

Move one and the scoreboard glides into its new order, the new leader's card lifts for a moment, and a banner names whoever is ahead right now (with reduced motion turned on, it simply re-ranks at once). Ready-made sets of weights (such as "Budget first") are one tap away, and Reset goes back to where the author started.

A plain sentence says how close the call is, for example "If Cost counted 2 instead of 5, Kyoto would lead". The full table of scores sits underneath, with the best score for each row marked in words; on a phone it becomes a short card for each row so every score shows without scrolling sideways.

The agent writes the options, the scores and the starting weights, and Yardmaster checks every number before the page goes live. It suits the calmer looks best (Calm Product, Blueprint, Editorial and Newspaper), and it works in all nine.

Weights you move are never saved or shared: the next person to open the link starts from the same starting weights, and with JavaScript off the page shows the starting standings.

A status page (public name: Status Page Kit) shows how a set of services is doing, like the status pages big online services publish. A banner at the top says in one glance whether everything is working, followed by each service with its state (Operational, Degraded performance, Partial outage, Major outage or Under maintenance) and a strip of up to 90 days of history with its uptime.

Below that come incidents (what went wrong, with timestamped updates, current ones first and past ones showing how long they lasted) and planned maintenance. Times are shown in UTC with an "Updated" time, because the page never guesses the current time.

To keep it live, an agent republishes the same link on a schedule, and anyone with the page open sees the new version appear on its own within about half a minute. Every state is written as a word with its own icon shape, never shown by colour alone, and the page reads fully on a phone and with JavaScript off.

A troubleshooter (public name: Troubleshooter Kit) is the help page someone opens while something is broken. It asks one calm question at a time with big answer buttons (Yes and No, or up to four choices), shows a picture beside the question so the reader can find the right part, and offers a tip where it helps. Go back and Start over appear as soon as you answer.

After a fix, a result check asks whether it worked, with two big buttons: Yes, it works now and No, I still need help, so a fix that did not work still leads somewhere. Pictures sit in a neat frame with an optional caption under them, and on a phone Go back sits right under the answers.

Before the first question, a Before you start card beside the title can say how long it usually takes, how many questions to expect and what to have to hand (your phone, a paperclip). When a question is about a light's colour, each answer can show a small colour dot next to its words. When it is fixed, the Solved card shows a calm tick and can list a few tips to avoid this next time.

Every path ends somewhere useful: a fix with numbered steps, a piece of good-to-know information, or a way to reach support with a real button to call, email or open a support page, plus a line with the opening hours or how fast the team answers.

Under the wizard, See every step opens the whole flowchart on one page as numbered cards along a line, and printing gives that map. Yes and No carry a tick and a cross as well as the words, and the page reads on a phone and with JavaScript off.

A proposal (public name: Proposal Kit) is the page you send a client: what you heard, what the work covers, the milestones, the price and a way to accept. The scope shows what's included and what's not included side by side, with the assumptions the price relies on as fine print underneath.

The pricing shows up to four packages as cards, each with its price and what it includes, and the one you recommend is lifted with a "Recommended" label. Under the cards, Build your package lets the client pick a package and switch on any extras: a receipt beside it lists the package and each extra they added by name, and the total updates as they choose.

When packages share features, a Compare packages table between the cards and the builder lines them up with a tick or a dash for each one. On a phone the running total stays in a small bar at the bottom of the screen while the client is choosing, and a printed proposal shows a clean quote without the switches.

A short Next steps list just before the sign-off says what happens once they accept. Nothing is ever charged: the page says so, and the client accepts with a sign-off (they sign in with Google, and you see who accepted and when).

Every price, label and column is written in words, never shown by colour alone, and the page reads fully on a phone, with JavaScript off and on paper.

An incident review (public name: Incident Review Kit) explains what went wrong and what will change, the way the best engineering teams write it up. A header card shows how serious it was (for example "Severity 1, critical"), whether it is resolved, how long it lasted, how long it took to notice and how long to stop the damage, who was affected and which services were hit.

A coloured bar shows the stretches of the incident, with the start, detection, mitigation and resolution times marked under it like a chart. On a phone the headline facts all sit at the top of the screen, and a printed review puts this card on a page of its own.

Below that comes a minute-by-minute timeline, with the clock time in your team's time zone, the time since the start ("+0:12"), and what kind of moment each one was (Trigger, Detected, Escalated, Mitigated, Resolved and so on), grouped into the stretch before anyone noticed, the response and the recovery, each stretch labelled with how long it lasted. A long quiet wait between two moments is marked (for example "16 min later") so it stands out.

Then why it happened: the root cause, the contributing factors (each can link straight down to the action item that fixes it) and a "five whys" ladder that asks "Why?" at each step, often followed by what we learned (what went well, what went poorly and where the team got lucky), and finally the action items, each with an owner and a due date. Ticking an action needs a sign-in, and everyone sees the same ticks.

The review is blameless: it names roles ("on-call engineer"), not people, and says so on the page. Every severity and moment is written as a word, never shown by colour alone, and the page reads fully on a phone, with JavaScript off and on paper.

A meeting page (public name: Meeting Kit) records a meeting so people can act on it. It shows who came (with the date, time, place and call link, and anyone who sent apologies), the agenda with how long each item took and how it ended (Decided, Discussed, Deferred, For information or Skipped), a numbered list of decisions with the reason for each, and the actions with an owner and a due date.

After signing in with Google, anyone can tick an action off, and the page shows who ticked it and when. Actions that are past due are marked Overdue in words, measured against a date the agent sets or the date of the meeting, and ticking one clears the mark at once.

When the actions belong to two or more groups of people (actions with no owner count as a group) and no more than twelve named owners, a "Show" filter narrows the list to one person. A weekly meeting can keep one link: the agent republishes the page each week and the ticks stay on the same actions.

A form page (public name: Form & Poll Kit) lets the people you share it with answer. It can hold a poll (pick one option, or several), a sign-up sheet (slots with a set number of places, such as volunteers for a session, which fill up as people take them) and a short form (written answers, a choice or a 1 to 5 rating).

To answer, a reader signs in with Google, and can change or remove their answer until it closes.

You choose who sees the results: only you, everyone as answers come in, or everyone once voting closes. Written answers are only ever seen by you. Under each block the page says plainly who will see what, and those lines always match your settings. Answers open once the page is published; ask an agent to read, export, close or reopen them for you.

Four more ways for the people you share a page with to take part, each after signing in with Google.

A sign-off asks readers to press I approve (or I acknowledge) on a short statement, such as approving a plan. Before anything is recorded, a separate box drawn by the share itself shows the statement again and asks the reader to confirm, so nothing on the page can sign for them.

The page can list the people expected to sign; each is recognised by the Google email address you give for them, and that address is never shown on the page or anywhere else. The list of who has signed fills in as people sign, and a reader can remove their own signature until it closes.

A ranked vote lets readers put three to ten options in order of preference with buttons (Rank this, Move up, Move down, Remove), so it works with a keyboard or a finger, no dragging needed. The result is worked out by instant runoff and shown round by round, with a table.

A Q&A board lets readers ask short questions (up to 280 characters) and upvote other people's questions, one vote each, sorted by Top or New. You can mark a question answered or hide it, and you can choose to see questions before anyone else does.

On a movable project board, readers move a card to another column with a Move to list on the card, and everyone with the link sees who moved it and when. If you later update the page with a card in a new place, your placement wins.

Under each block the page says plainly who sees what, and those lines always match the settings. Before the page is published, and with JavaScript off, every block shows with its buttons turned off. Every look styles these blocks in its own way, from a signature line to an "approved" stamp.

Two things to know for now: in Chrome on Windows and Linux and in Firefox, pressing the arrow keys on a closed Move to list moves the card one column per key press, so open the list first (or use the mouse). And if you take more than ten minutes to finish signing in after moving a card, the card goes back; if the move is saved after all, the page may announce it as if someone else made it.

An event page (public name: Event Kit) is an invitation that guests can use on a phone. At the top an invitation card, laid out like a ticket, can open with a cover photo of the place or the occasion: a wide picture with a short description for guests who cannot see it, cropped to a strip so the buttons still fit on a phone screen. On a phone, a taller card (such as a several-day event or one with a notice) shows a slimmer strip or none.

Under it comes the date in large type, then the buttons, then the facts: the time with its time zone (for example "10:00 to 17:00, Lisbon time (UTC+0)"), the place with an Open in Maps link, an online link if there is one, and the hosts.

The buttons are Add to Google Calendar and Download .ics (for Apple Calendar and Outlook), plus RSVP when the page takes replies. For a typical invitation (one to three days, with or without a notice, and a title up to about 40 characters) they sit on a phone's first screen in every look; a much longer title can push them down, so keep the title short and put the rest in the subtitle.

The calendar buttons put the event in each guest's calendar at the right hour wherever they live, even when the clocks change during the event. A guest whose clock is in another time zone sees one more line under the time, for example "That is 19:00 to 02:00 your time".

Below the card the page can hold a schedule (the programme by time, with parallel rooms side by side on a wide screen and stacked on a phone, plus breaks and meals) and speaker cards that the schedule links to, each with a photo or initials, the speaker's role above their name, their organisation and a short bio. During the event the schedule marks what is on Now and what comes Next.

RSVP uses a sign-up sheet or poll on the same page, so guests sign in with Google to reply. When the reply form has a section of its own, it is drawn as an RSVP panel that matches the invitation. You can ask an agent to read the replies. If the event is cancelled or postponed the page says so and hides the calendar buttons.

While a guest has the page open, a countdown sits beside the date: "Starts in" over tiles for the days, hours and minutes, which switch to minutes and seconds in the last hour (a guest whose device asks for reduced motion keeps whole minutes), then a "Happening now" badge during the event and "This event has ended" after it.

Each look draws its own tiles, and on a phone they sit beside the date as a small readout, so the buttons stay on the first screen. Screen readers hear one sentence instead, for example "Starts in 3 days, 4 hours", which changes at most once a minute. A page published before this countdown keeps its one-line countdown, which updates once a minute.

On an iPhone or in Safari the Download .ics button may do nothing, so there the card adds a short line under the buttons: "If nothing downloads, use Add to Google Calendar." If an event page is shown as tabs or slides, the RSVP button and the speaker links still work: they open the right tab or slide and bring it into view.

A scavenger hunt page (public name: Scavenger Hunt Kit) is a trail of clues for a party, a classroom, a museum night or a team day. A trail map runs across the top and the first clue is open.

Players solve it, type the answer and press Unlock: the next clue's wax seal cracks open and the trail draws on to the next stop. A wrong answer just says "Not quite, try again.", and Show a hint helps when someone is stuck. A chip on the trail map shows how far along players are ("Stop 3 of 6") and the pin hops to each new stop. The last answer opens the finale: a medal stamps down, then confetti and how long the hunt took.

Answers are checked loosely, so capitals, accents, punctuation and a leading "the" don't matter, and the agent can list a few alternates for each clue. The answers, the later clues and the finale are locked inside the page and are never shown as text, so peeking at the page source gives nothing away.

That lock keeps an honest party honest, nothing more: someone determined could still try guesses on their own computer, and a short or common answer would not hold out long. So never put a real secret, like a password or a door code, in a hunt.

Nothing a player types is saved or shared. If someone reloads the page, they press Already partway through? and type the latest answer they solved, and every clue up to there opens again.

Ask your agent for the printable clue cards: one card per stop with its code word in large type and a QR code that opens the hunt, plus a placement sheet that only you see, saying where to hide each card. The cards are made on your computer from your own copy and are never put online.

A hunt published before the Kit update that made hunts playable shows only the first clue, "This hunt opens soon." and the sealed stops. Publish it again to make it playable.

A time capsule page (public name: Time Capsule Kit) is a set of doors that open on their dates: a one-door-a-day advent calendar, a launch reveal, a countdown to a wedding, or a letter to open in a year. Each door shows its title, the date it opens and an optional teaser.

Until its date, what is behind a door is not in the page at all: not in its text, its hidden data or its downloadable source, so nobody can peek. It is kept in a private file, and on the day the door opens for everyone who has the link. A date-only door opens at midnight in the time zone you choose.

Each locked door shows its opening date, and readers get a live countdown to the next door on clock tiles that flip as the time runs down. A door that opened in the last day swings open when the page loads (in the reveal look it waits behind a curtain the reader pulls open).

If a door opens while someone has the page open, a note asks them to reload. You can change a door that has not opened yet by updating the page on the same link. A capsule published before this update stays a static page (each locked door shows only its date) until it is published again.

A wishlist page (public name: Wishlist Kit) is a gift list for a birthday, a baby shower, a wedding or housewarming, or a classroom. Each gift is a card with a photo, a price, a note and a Where to get it link. Something wanted more than once (four place settings, say) shows how many are needed and its price each, and up to six gifts you care about most can carry a Most wanted tag.

Guests who sign in with Google tap I'll get this to claim a gift, so nobody buys the same thing twice. They see Claimed by you with an Undo, everyone else sees a Claimed ribbon, and a line at the top counts how many gifts are claimed. A big number says how many gifts are still needed, and readers can show only Still needed or Yours and sort by Lowest price first.

Claims are private: Yardmaster never keeps a name with a claim, and you see only how many of each gift are claimed. Anyone with the link can see which gifts are taken, so if you want the surprise, do not open the page yourself. Someone watching the page live may be able to guess from timing. A wishlist published before claiming arrived stays a static page (the list reads in full and the buttons say claiming opens soon) until it is published again.

A story page lets the reader choose what happens next: each passage ends with a few choices, and picking one moves on to the next passage. A story can keep track of simple things, such as an item the reader has picked up or a score, and some choices stay locked until the reader has earned them.

Before a story is published, Yardmaster follows every route and refuses one that leaves a passage out of reach, has no ending, or traps the reader with no way out. The page works with the keyboard, has Go back and Start over buttons, and still reads as a plain list of passages with JavaScript off. Where the reader has got to is not saved, because a saved value would be shared with everyone who opens the link.

A data story (public name: Scrollytelling Kit) keeps one chart or picture on screen while the reader scrolls through a short series of steps, and each step changes what it shows: a line that draws itself year by year, one bar picked out, a picture that zooms in on a spot with a pin, or a switch to a diagram.

The chart or picture stays pinned beside the steps on a wide screen and at the top on a phone, the current step is marked with a coloured edge and a filled number, and a small Previous and Next control moves one step at a time. Each block opens with its title set large in the page's look, beside the chart or on a card over the first picture.

A block told in pictures (the overlay layout) spreads its picture across the whole width of the screen while the steps scroll over it. As each step arrives its card fades in and its text slides into place, finishing well before you reach it.

With reduced motion turned on, nothing animates and the controls jump straight to the step. With JavaScript off, and when printed, it reads as a numbered list of steps, each with a small snapshot of what it shows and a sentence describing it, and nothing a reader does is saved.

A video page (public name: Video Kit) plays a recording such as a talk, a demo or a lesson. The agent gives it the video file from your computer (an MP4, up to 1 GB) and, if you have one, a captions file, and Yardmaster uploads the video with the page.

Under the player the page shows a row of chapters you can click to jump around and a transcript that highlights the line being spoken and scrolls along with it. You can turn Follow along off, click any line to jump there, and search the transcript. Captions are built from the transcript.

The video plays in Yardmaster's own player, styled to match the page's look: play and pause, a progress bar marked with the chapters (point at it to see the time and chapter), captions, speed from 0.5x to 2x, volume, picture-in-picture where your browser offers it, and full screen. While the video plays, the bar fades after a moment without the mouse (in some looks it sits under the picture and stays put), and comes back as soon as you move, tap or press a key.

With the player in focus, the keyboard works too: Space or K to play and pause, J and L to jump 10 seconds, the arrow keys for 5 seconds and the volume, F for full screen, C for captions, M to mute and 0 to 9 to jump through the video. If the video cannot play, the player says so plainly and the transcript still reads.

On a wide screen the transcript sits beside the video, on a phone it sits below. The video is part of the page, not a link to somewhere else, so it is protected by the same password or Google sign-in as the page, and videos from sites such as YouTube are not used. With JavaScript off the video plays with your browser's own controls and the page reads as plain lists.

To fix a chapter, a transcript line or the look later, the agent updates the same link and the video you already uploaded is kept, not sent again. The video counts toward your Share storage, and Yardmaster tells you plainly if it does not fit.

If Automatic transcripts is turned on (an in-development switch in Settings, off by default), the agent can ask for an automatic transcript instead of writing one: the page goes live at once, then Yardmaster makes the transcript on your own computer, free and with nothing uploaded for it, and adds it to the same link when it is ready.

It is added only while you are signed in with the account that published the page; if you are not, an inbox note asks you to sign in, and it gives up after a day.

If a transcript cannot be made or added, an inbox note says so; when the Share could not be updated for a day, that note offers Try again, and a transcript you or the agent supply yourself always replaces the automatic one. The same switch adds Captions (.vtt) and Captions (.srt) to the File Converter for audio and video files.

A podcast page (public name: Podcast Kit) is one episode: big cover art (or a cover drawn from the show's initials), the show and episode title, a player, chapters you can click, a transcript and the guests as cards with their photos, plus links to listen in other apps.

The agent gives it the episode's audio file from your computer (an M4A or MP3 file) and Yardmaster uploads it with the page, so it is protected by the same password or Google sign-in as the page. With JavaScript off it still plays and reads as a plain page. To fix a chapter or the look later, the agent updates the same link and the audio is kept, not sent again. The audio counts toward your Share storage.

A portfolio page (public name: Portfolio / Resume Kit) is a page about a person: a designer, a teacher, a photographer, a consultant or a student. The person's name is the page title.

It can hold a profile (a photo or initials, where they are, whether they are available, a short summary and their links), projects (each with a picture, their role, the year and the result it achieved), experience and education on a timeline, groups of skills, testimonials (quotes from people they worked with) and a closing contact panel with large links. Every link shows its address as well as its name, and only email, phone and web links are allowed.

The page looks at home in every look, and printing it (or saving it as a PDF) gives a clean, light resume on one or two pages, with project pictures left out and no entry split across pages. The page holds only the details the agent was given; it never adds contact details on its own.

A listing page (public name: Listing Kit) shows a home for sale or a rental the way a premium estate agency would.

It opens with a wide photo spread that runs to the edges of the screen, the home's name and price, a status such as For sale or For rent, and the key facts as big numbers (bedrooms, bathrooms, floor area, the year it was built). Show all photos opens a full-screen photo tour; press Escape or Close to go back.

On a phone, a slim bar with the price and a Contact button stays at the bottom of the screen while you look through the photos and facts. Homes for sale also show the price per square foot.

Below come the highlights, the agent's card with their phone and email, and a floor plan with numbered pins: tap a pin to see that room's size, a note and a photo. Every room is also listed beside the plan, and pointing at a room in the list lights up its pin. A home that is sold, under offer or leased shows that across its main photo.

It can add a monthly payment calculator (or a rent split for a rental), a neighborhood map with nearby places, and a contact panel. Everything works even with scripts switched off, and printing gives the photos, facts, plan and room list on paper. The page holds only the details the agent was given; it never invents a price, a size or contact details.

A trip page (public name: Map / Trip Kit) lays out a journey: a road trip, a city weekend or a site visit.

It can hold route maps, place cards (where to eat, stay or look, each with an optional photo, its address, opening hours, price and links) and a day-by-day itinerary (each day with its date, a small map, its stops in order with times, how you get between them, bookings shown as ticket stubs, tips, where you sleep and a button that opens the day in Google Maps).

Yardmaster draws every map itself when the page is published, so nothing is loaded from a map service: the page works offline and tells no one who opened it. A map wide enough (about 150 km or more) shows real coastlines and borders; a city-sized map is drawn on grid paper on purpose, because a coastline at that zoom would look wrong.

Places too close together to tell apart share one pin showing each of their numbers, and the list under a map, or the place cards or itinerary it draws, names every place with links that open Google Maps and Apple Maps. The agent supplies the coordinates and travel times itself, since nothing looks up addresses or plans routes.

Because anyone with the link can read a share unless you limit access, the agent is told never to put a full booking reference, passport number or door code on a trip page; it shows only the last few characters.

A recipe page (public name: Recipe Kit) is a cooking recipe, not one of Yardmaster’s automation recipes. It shows the ingredients, a numbered method and a shopping list.

Readers can pick how many servings to make and switch between metric and US units, and every amount changes to match (weights stay weights and volumes stay volumes, so cups of flour never turn into grams). Steps can carry an oven temperature and a timer.

A timer shows only the button you need next: Start, then Pause (or Resume when paused), and Reset to start over. When a timer ends it chimes, vibrates on phones that support it and says “time’s up” to screen readers; Pause or Reset stops it.

While a phone is locked or asleep the page is paused, so the countdown can stop with it and the chime comes late, after you open the page again; keep the phone awake while a timer runs if the timing matters. On an iPhone with the ring/silent switch set to silent the timer does not chime, and iPhones do not vibrate for web pages; the “Time’s up” badge and the spoken announcement still work.

The shopping list is private to each reader and not saved, unless the agent makes it a shared list for a household, so everyone with the link sees the same ticks. Every ingredient and every step also has its own tick box, so you can mark what you have got and what you have done; these ticks are just for you and are never saved.

When the recipe sits further down the page, a Jump to recipe link at the top takes you straight to it. Newer pages also have Cook mode: one step at a time in large text, with its timer, an Ingredients drawer and big Previous and Next buttons (press Escape or Exit to leave). Cook mode asks your browser to keep the screen on; if the browser says no, a short line tells you the screen may still dim.

A Copy list button copies the shopping items you have not ticked yet, in the servings and units you picked, ready to paste into a note or a message. Servings, units, ticks and the timer countdown work even with JavaScript turned off (the sound, Cook mode and Copy list need it).

A bracket page (public name: Bracket Kit) draws a knockout tournament of 4 to 64 entries (teams, dishes, books, ideas) as a classic bracket: the two halves flow toward the final in the middle, joined by lines, with a champion card that lights up with a trophy once the final is decided. Each entry can have a small picture. On a phone you see one round at a time and swipe or tap the round names to move along.

When the agent turns on picks, readers fill in their own bracket: tap your pick in each match to send it through (the entries can be teams, bakers, dishes or anything else), all the way to a champion.

A bar at the bottom counts the picks made and holds the Save my picks button; saving asks the reader to sign in with Google, and coming back later shows their saved picks. Picks lock at the time the agent set, shown in each reader's own time zone; after that nobody can change them. Once the champion is crowned, the page says picks are locked and shows the final results.

Readers can switch between Your picks and Results. After picks lock, a leaderboard ranks everyone who saved a bracket by points (later rounds are worth more), with the most points they can still reach and how many picks they got right; a reader's own row is marked, and tied readers share a place.

The top three wear gold, silver and bronze medals, and a line above the board tells each reader where they stand. While picks are open, a Next pick button jumps to the first match a reader has not picked yet.

You (or your agent) can advance the winners after publishing: every open page draws the new result as it arrives, the line to the winner draws itself in, and when the final is decided the champion card has its trophy moment (with a short burst of confetti, left out for readers who asked their device for less motion). Without picks, a bracket is simply a results page you keep up to date.

Brackets look at home in every look; Playful suits an office pool, Bold a sports night, Newspaper a sports page and Luxury an awards night. A bracket published before picks arrived stays a static page until it is published again.

A challenge page (public name: Challenge Kit) turns a shared goal into a calendar: 30 days of walking, a reading month, a 100-day drawing habit. Each day is a tile with its date, and the agent can give every day the same task or give some days a task of their own (those tiles are marked). At the top a big ring fills as the whole group ticks off days.

Readers sign in with Google and tick their own days. A Tick today button above the calendar does it in one tap, and the day's tile stamps itself done. With catch-up on (the usual choice), a reader can also tick a day they forgot; with catch-up off, only today can be ticked.

The streak board shows everyone taking part with how many days they have done, their current streak and their best one, the top three marked with a flame.

Each reader's own streak lights up as one chain across the calendar with a flame counting its days, and before day 1 the ring counts down to the start. A streak is not broken until a day is over, so an unticked morning still counts the run up to yesterday. The board is public: the page tells readers that their name and days will show there before they tick, and a reader who unticks every day comes off the board.

Days follow each reader's own clock, so day 1 starts at midnight wherever they are, and friends in other time zones tick at different hours. Once someone has ticked, the number of days, the start date and the catch-up setting can no longer be changed; to change them, start a new challenge or clear the check-ins first. A challenge holds up to 1,000 people. A challenge published before this update stays a static page until it is published again.

Challenges look good in every look; Playful suits friends and families, Bold a fitness push, Calm a wellbeing habit and Notebook a reading month.

A workout page (public name: Workout Kit) is a training plan you can follow on your phone. It shows the week at a glance, then each session with its exercises: how many sets, how many reps or how many seconds, the weight to use and a short tip.

Tap the circle for each set as you finish it: it fills with a check. The page counts your sets, marks an exercise done, highlights the one up next and shows a badge when the whole session is done. Each exercise can have a rest timer that works just like a recipe timer. Your ticks are private to you and stay on your own phone or computer, so they are still there when you come back (unless your browser blocks saving).

A team page (public name: Team Kit) introduces a group of people. It has a directory of people cards (a photo or coloured initials, their role, team, where they are and a fun fact) and an org chart that shows who looks after whom.

Tap a team chip to see just that team. Tap a name in the chart to jump to that person's card, or Show in chart on a card to jump back. Fold a branch of the chart away with its reports button, and pick Fit, Normal or Close to see more or less on each card. On a phone the chart becomes a tidy indented list, so it never scrolls sideways.

Type in Search people to find someone by name, role, team or place. It works together with the team chips.

A moodboard page (public name: Moodboard Kit) is a wall of pictures, colour cards and short notes, laid out in neat columns like a designer's studio wall. Each picture can have a caption and a credit, and a note can be one big word that sums up the mood.

When the page is published, Yardmaster looks at your pictures and picks out their main colours. They appear under the wall as a palette of big colour chips, each with a plain name, its colour code, its RGB numbers and how much of the pictures it makes up, and every picture gets a small strip of its own colours.

A line under the title counts what is on the board. Tap Copy on a colour to copy its code. If you already have brand colours, give them instead and they are used as they are.

A changelog page (public name: Changelog Kit) shows what changed in a product, release by release, newest first, on a timeline like the release notes of the best software companies. Each release shows its version and date, a short title and summary, an optional screenshot, and a list of changes.

Every change is labelled New, Improved, Fixed, Security or Removed, always written out in words, not only a colour. The newest release is marked Latest.

When a page has more than one kind of change, readers can pick one at the top (for example Fixed) to see only those changes; each choice shows how many there are, and releases with none of them close up. The filter works even with JavaScript turned off, and nothing is saved: reopening the page shows everything again. On an older browser that cannot do this, the filter is left out and every change shows.

When someone comes back to a changelog, every release that came out since their last visit is marked New since your last visit. This is remembered only on their own device, for that page alone, and nothing is sent anywhere; a first visit shows no marks.

On a phone the releases stack in one column with the version and date above each one. Printed, every change shows and no release is split across pages.

To keep one link up to date, ask the agent to publish with auto-refresh and refresh the same link after each release; anyone with the page open sees the new release on their own.

A family tree page (public name: Family Tree Kit) lays out a family generation by generation, with photos, dates, places and short stories.

On a computer it draws a real family tree: couples side by side, joined by a ring, and their children underneath. On a phone it becomes a tidy list, one generation at a time, so it never scrolls sideways. Tap anyone to open their card with their story, then tap a parent, partner or child on the card to move around the family. Press Escape or Close to go back.

A celebration page (public name: Celebration Kit) is a wedding, birthday, anniversary, retirement or graduation page guests love opening.

The first screen is made for a phone: the names in big lettering with a monogram, the date and place, a live countdown and an RSVP button, set on a photo or in soft light. Below it come the details: when and where with calendar buttons and a map, the plan for the day, your story with photos, the RSVP form, gift registry links and answers to common questions. Every look gives the first screen its own style, from an engraved invitation to a confetti party.

A menu page (public name: Menu Kit) is a restaurant or cafe menu that looks designed: sections with their own headings, each dish joined to its price by a dotted line, a short description, and sizes such as a glass or a bottle.

Each dish can show its dietary tags (vegan, vegetarian, gluten free, dairy free, nut free, halal, kosher), how spicy it is (mild, medium hot or hot) and its allergens, always written out in words (“Contains: gluten, egg”). A key at the end lists every mark the menu uses. A section can also have one set price, for a tasting menu or a Sunday supper, with an optional wine pairing; its courses are then listed without prices of their own.

Readers can tap filter chips such as Vegan or Gluten free to see only the dishes that match. Several chips work together: Vegan and Gluten free shows only dishes that are both, and a section with nothing left says so. A Show everything button clears every filter at once. The filters work even with JavaScript turned off, and nothing is saved: reopening the page shows every dish again. On an older browser that cannot do this, the chips are simply left out and every dish shows.

On a phone, for example when a guest scans a code on the table, a bar of section names stays at the top so you can jump to Plates or Wine, and every button is large enough to tap. Printed, the menu drops the chips and photos and sets itself in two columns for the table.

A Today’s specials card can sit at the top. If the agent publishes the menu with auto-refresh and updates the same link each day, anyone with the page open sees the new specials on their own, and the code on the table never has to change.

Dietary tags and allergens come from what you tell the agent; it is told to leave a tag off rather than guess, because a wrong one could hurt someone.