Welcome to the trustee area of the What Would Mia Do Trust website. This is where we handle grant applications, messages, donations and the website itself. Everything is kept here, with a record of who did what, so nothing gets lost in someone's inbox.
New here? Press Take the tour at the top of this page for a two-minute walk round the menu. The How-to guide tab explains every part in detail.
The golden rules
- Keep it in the trustee area. Reply to applicants and messages from here, not from your own email, so the conversation is kept with the application and the next trustee can see it.
- Children's details are confidential. Applications are about young people aged 5 to 18. Do not forward, print or download them unless you need to, keep any downloads somewhere secure, and delete them when you have finished.
- Never ask for bank details by email or phone. Payment details only come through the applicant's account on the website, where they are encrypted and deleted once the grant is paid. If someone emails bank details, delete the email and ask them to use their account.
- Trustees decide. The AI assistant summarises applications, checks documents and drafts replies, but it can be wrong. Read every application yourself before deciding.
- Two trustees approve every grant (unless an admin has turned sign-off off). One proposes the amount, a different trustee confirms it.
- Safeguarding comes first. If anything in an application or message worries you, follow the Trust's safeguarding policy straight away, and do not contact the family about it from here.
- Look after your sign-in. Use a strong password and your second step (an authenticator app or a passkey; with a passkey, always sign in with it). Never share your account. If you lose your phone, ask an admin to reset your second step.
A typical week
- Check the Dashboard: it shows what needs attention, what is assigned to you, and the budget.
- Answer Messages waiting for a reply. The red badges show what is new.
- Move Applications along: ask for anything missing, discuss with other trustees in private notes, propose or confirm grants, and record payments.
- Editors: post news and events, and Publish when you are done.
What you can see
What appears in the menu depends on your groups, which an admin sets under Team:
| Group | What it lets you do |
|---|---|
| Trustee | Sign in to the trustee area, and read and answer messages |
| Grants | Applications, referrals, payments, donations and Gift Aid |
| Editor | Website posts and events, page text, the banner and publishing |
| Admin | Everything, plus the team, settings, sign-in security and deleting applications |
Getting help
- The How-to guide tab covers every page, step by step.
- The ? next to the bell at the top of every page brings you back here.
- Something not working, or a question the guide does not answer? Ask one of the admins (see Team).
Everything in the trustee area, step by step. Start with Read me first if you are new, and press Take the tour for a quick walk round the menu.
Signing in
Go to wwmd.org.uk/admin. You sign in on the Trust's sign-in page (login.wwmd.org.uk) with your email address, password and the code from your authenticator app. The first time, use the temporary password from your invitation email; you will be asked to choose a new one, and the trustee area then asks you to add a second sign-in step: an authenticator app on your phone (recommended), a passkey, or a code emailed to you each time you sign in, if that is switched on. It takes about two minutes, and you cannot use the trustee area until it is done.
If you choose a passkey, you add it on the Trust's sign-in page, then sign in again with it. From then on, always sign in with your passkey: signing in with only your password brings you back to the set-up page, so a stolen password on its own never opens the trustee area. You can add an authenticator app later as a backup.
Your sign-in (at the bottom of the menu) shows how you can sign in, which second step you use, lets you switch to the other one or move your authenticator app to a new phone, and lets you add a passkey. With a passkey you sign in with your fingerprint, face or device PIN instead of your password and code: on the sign-in page, enter your email address and you are asked for it. You can remove passkeys there too, and Sign out everywhere if you signed in on a shared or lost device. Lost your phone? Ask an admin to Reset second step for you under Team.
Everyone uses the same sign-in page and the same kind of account: supporters, applicants and trustees. What lets you into the trustee area is being in its groups, which only an admin can give you (see SETUP.md). If you already had an account as a supporter, it is the same one. Forgotten your password? Use "Forgot your password" on the sign-in page.
Finding your way around
- The menu on the left (or behind the menu button on a phone) shows the pages your groups allow: grants, the website, and admin settings.
- Red badges show what is new: messages waiting for us, and applications where the applicant has replied.
- The bell at the top lists recent things that need you; click one to go straight there.
- ? next to the bell opens this guide and Read me first, with Take the tour.
- Your email alerts chooses what is emailed to you (see below).
Your email alerts
Under Your email alerts you choose which things email you: new applications, applicants replying, approvals needing a second trustee, safeguarding flags, new messages, replies to messages, referrals and donation changes. You only see the choices your groups cover, you are never emailed about something you did yourself, and Only mine limits replies to the ones assigned to you. The emails leave out personal details and link straight to the right page.
Admins can also switch on a shared trustees inbox there, which gets every alert. Only use it for a mailbox that exists and someone reads: email to an address that does not exist bounces, which harms the Trust's email reputation.
Groups
Access to the trustee area comes from Cognito groups, which an admin adds by hand under Team:
| Group | Can |
|---|---|
| Trustee | Sign in to the trustee area. Everyone needs this (or Admin). |
| Grants | Applications, payments, donations and Gift Aid |
| Editor | Website posts and events, page text, the banner and publishing |
| Admin | A separate group: everything, plus the team, settings, sign-in security, the audit trail and deleting applications |
So a trustee who handles grants has Trustee and Grants; one who looks after the website has Trustee and Editor; someone can have both. Grants or Editor on their own give no access, and someone with neither Trustee nor Admin cannot sign in, even with the right password or single sign-on account. Changes take effect within an hour, or straight away the next time the person signs in. Admins cannot remove their own admin group or disable themselves, so there is always at least one admin.
Inviting someone: Team, then Invite someone. Someone new gets an email with a temporary password and is asked to set up an authenticator app on first sign-in. Someone who already has an account on the website keeps it, and gets an email saying they now have access. The Team page shows each person's second sign-in step (authenticator app or emailed codes), or that they have not set one up yet. Remove takes someone out of the trustee area but leaves their account (and any donations or applications); Disable stops them signing in at all, including to their own account. Reset second step is for someone who has lost their phone: they are signed out and emailed, and set up an authenticator app again next time they sign in. Sign out everywhere ends all their sessions within the hour.
The dashboard
The first page shows what needs attention: new applications, applications where the applicant has responded, anything the AI assistant has flagged, approvals waiting for a second trustee, and anything that has waited longer than usual at the same stage. Below that are the applications assigned to you, the grants budget for the year (approved and paid against the budget), and (for the roles you have) donation totals, Gift Aid waiting to be claimed and the state of the website. Editors also see stories you can share: updates from grant recipients who are happy for us to use them in a news post.
Grant applications
Applicants now apply from their own account on the website. They can save an application and finish it later; you only see it once they send it. Drafts are never shown in the trustee area.
When an application arrives, trustees who chose "New grant applications" in Your email alerts get an email with the reference and a link. The email deliberately leaves out personal details; they are only in the trustee area.
The Applications page lists everything sent to us. Search by name, reference, email, sport or postcode, filter by status, and use Export CSV for a spreadsheet of all applications. A red dot means the applicant has responded since a trustee last opened it.
Open the application to see everything the applicant told us, the supporting documents, the fraud and duplicate checks, and the full history.
Applicants can add documents from their phone without signing in on it: their account shows a QR code (or a short code to type in at wwmd.org.uk/u), and the photos they take appear on the application. These show as "sent from a phone".
Supporting documents
Click a document to open it in the page: PDFs and photos show in a viewer (use the arrows, or the arrow keys, for the next one), with Open in a new tab and Download. iPhone photos (HEIC) are shown from a copy made automatically. Word files can only be downloaded. Beside each document:
- Checks run on every file. They flag the same file sent with another application, a file that is not really the type its name says, PDFs made or changed in editing software (such as Canva or iLovePDF), PDFs changed after they were made, and photos saved by photo editors. They are prompts to look more closely, not proof: many genuine documents are made in ordinary software.
- AI review reads the PDF or photo and says what it is, who issued it, the date, amount and payee, whether it fits the application, and anything worth checking.
- Comments are notes between trustees about that document.
- Share makes a link to that one document for someone outside the Trust, such as a club treasurer confirming a quote. Choose how long it works (an hour to seven days) and who it is for. You can see how often it has been opened, and cancel it at any time. Every link is recorded in the history.
Fraud and duplicate checks
Each application has a Fraud and duplicate checks card. It links other applications with the same email, young person, address, bank account, internet address or sign-in, and flags warning signs, such as a bank account used by someone else, the same young person from a different account, a grant in the last year, a throwaway email address, an address outside England and Wales, an application filled in in a few minutes, far more than a usual grant, or warnings from the document checks. It ends with a Before you pay checklist. Like the document checks, these are prompts for a closer look; they never decide anything.
The history shows Seen by the applicant under each thing we sent once they have opened their application, so you know a request has been read.
The board, and who is handling what
Applications opens as a board, with a column for each stage: New, Under review, Waiting for the applicant, Approved (to pay) and Paid in the last 60 days. Each card shows how many days the application has been at that stage, turning red once it is longer than the Trust would like (set in Grant settings), who is handling it and the amount. Choose List for the table, with search and a status filter.
On an application, Handled by assigns it to a trustee with the grants role (or Take it on myself). They get an email, and it appears on their dashboard.
What applicants see while they wait
Each application's page in the applicant's account shows a progress bar, what the current stage means, what happens next, and when to expect a decision: "Our trustees next meet on 6 November. We aim to let you know by 13 November", from the next meeting date in Grant settings, or the usual time to decide if no date is set. Once a grant is approved, it says when we aim to pay it. If a date passes, it says it is taking a little longer than usual rather than showing a date in the past. Keep the next meeting date up to date, and applicants will always know where they stand.
Each morning the website also sends, once each:
- a reminder about a request the applicant has not answered after a week
- a reminder about a draft nobody has touched for a fortnight
- "How is it going?", three months after a grant is paid: the applicant can tell us in a few lines, add a photo and choose whether we can share it. Their answer appears on the application and, if they agreed, on editors' dashboards.
Admins can change all of these timings, or turn any of them off, in Grant settings.
What the application asks
The form asks everything the old WordPress form did, and more, in ten sections. Applicants can jump between sections, save and finish later, and check all their answers before sending:
- Before you start: four eligibility questions (age, England or Wales, sport, financial need). A "No" shows a gentle warning, but they can still apply and explain.
- About you: whether they are applying for someone else, and if so their name, relationship and phone.
- The young person: name, preferred name, date of birth, email, phone, school or college.
- Where they live.
- Their sport: sports, how long, what level, how often, the club, an optional coach contact (with permission for us to contact them), and what they enjoy and hope to achieve.
- Your circumstances: why they have approached us, optional circumstances (free school meals, benefits, young carer and so on), whether they have asked anyone else, and whether the family can contribute. We never ask for proof.
- What you need: a description, an itemised list of costs with optional links and a total, how it will help, when it is needed, how they would like us to help, and for a new sport, whether borrowing equipment would work.
- Documents and anything else: attachments, how they heard about us, a fundraising pack, and whether we may share their story (first name only).
- Check your answers.
- Declaration: accuracy, consent and a typed signature.
The trustee view shows each section, and the CSV export includes the club, level, experience and preferred way to help. Applicants can view, print or download a PDF of what they sent from their account.
Downloading applications
- Download PDF on an application gives a tidy, confidential copy: contact details, the AI check, every answer, requests and answers, documents, how the grant is to be paid (never bank details) and the full history. Useful for trustee meetings and your records.
- PDF and documents (ZIP) adds every file the applicant uploaded.
- Download as PDFs on the Applications list gives a ZIP of PDFs for the list as filtered (up to 100), for example all applications under review before a meeting.
Each download is noted in the application's history. The files contain children's personal data: keep them somewhere secure, and delete them when you no longer need them.
The AI check
When an application is sent, an AI assistant (Claude, running in the Trust's own AWS account through Amazon Bedrock) reads it, with any PDF or image attachments, and checks it against the grant criteria. A few seconds later the AI check panel shows:
- a short summary, written for trustees
- each criterion, marked met, not met or unclear, with a note
- a suggestion: looks eligible, needs more information, may not meet the criteria, or needs a trustee to judge
- anything that seems to be missing
If something is missing, the assistant asks the applicant for it (at most three things at once). The applicant gets one email, sees the requests on their tracking page marked as coming from our automated check, and the application moves to "More information needed". When they have answered everything, the application moves back to "Under review" and the assistant checks it again. After the number of rounds set under AI assistant (two by default) it stops asking and leaves the application to trustees.
If automatic requests are switched off, the panel shows Suggested requests instead. Edit them if you like, untick any you do not want, and click Send to the applicant.
Safeguarding. If the assistant thinks the application raises a safeguarding concern, it does not contact the applicant at all. The application is marked "Safeguarding" in the list and on the dashboard, and trustees with "Safeguarding flags" alerts (on by default for the grants group) get an email asking them to look at it. Follow the Trust's safeguarding policy.
What it never does. It never approves or declines a grant, changes a status to a decision, asks for bank, benefits or medical details, or sees the applicant's email address or phone number. Trustees make every decision. Treat its suggestion as a second pair of eyes, not a verdict: it can be wrong, especially about documents it cannot read (Word files, for example).
Check again runs a fresh check at any time, for example after you have added a note or the applicant has sent something by email. Every check is kept under "Earlier checks", and each one is noted in the history, marked "AI assistant".
To change the criteria, switch off automatic requests, or switch the assistant off completely, an admin goes to AI assistant. With it off, applications work exactly as before.
| Status | Use it when |
|---|---|
| Received | Set automatically when the application arrives |
| Under review | The trustees are considering it |
| More information needed | You have emailed the applicant with questions |
| Approved | The grant has been agreed |
| Grant paid | The money has been paid or the equipment ordered |
| Not successful | You cannot help this time |
| Withdrawn | The applicant has withdrawn |
- Update status changes the status and, if the box is ticked, emails the applicant (and the person who applied on their behalf) with the new status and any message you add.
- Email the applicant sends a message without changing the status.
- Add a private note records discussion that only trustees can see.
Everything is recorded in the history, with who did it and when. Applicants reply through their account, and their replies appear in the history marked "From the applicant". Every email to them asks them to reply on the website, not by email.
Asking the applicant for something
Use Requests to the applicant to ask for:
- a supporting document, such as a quote, an invoice or a letter from a coach
- an answer to a question
- grant payment or delivery details, once you are ready to pay
The applicant gets an email asking them to sign in to their account, where they see an "Action needed" card. When they respond, every trustee gets an email and the request shows "Answered, please review". Check it, then click Mark as done, or Reopen it if you need something different.
Applicants can also upload documents and send you messages at any time. Messages appear in the history marked "From the applicant". They can also withdraw an application from their tracking page while it is still open; you get an email and the status changes to Withdrawn.
Approving a grant
Use Approve this grant on the application (approving is not in the status list, so the amount is always recorded). Enter the amount and, if you like, a note for other trustees.
With two-trustee sign-off on (the default, in Grant settings), that is a proposal: the other trustees are emailed, and the application shows "Second trustee needed". A different trustee then opens it and chooses Confirm approval, which approves it and, if ticked, emails the applicant, or Not yet, with a reason. Both names are recorded in the history. The applicant is not told anything until it is confirmed, and they never see trustees' names or notes. With sign-off off, Approve grant approves it straight away.
The approval card shows how much of the year's grants budget is already approved, and what it would be including this grant. A grant can only be marked as Grant paid once it is approved. When it is paid, not successful or withdrawn, anything still asked of the applicant is closed.
Paying a grant
When you approve a grant, the applicant can tell you how it should be fulfilled:
- Pay the club or supplier directly (our preference): the club's name, contact, what it is for and the amount, plus the club's bank details or an uploaded invoice
- Pay into a bank account: usually a parent's, with the account name, sort code and number
- Buy and deliver equipment: what to buy, and where to send it
Bank details are encrypted and shown as "Account ending 1234". Click Show bank details only when you are making the payment; each time is recorded in the history. Your bank will check the name on the account (Confirmation of Payee) when you set up the payment. If it does not match, ask the applicant through a request rather than by email or phone.
Bank details are deleted automatically when you set the status to Grant paid, Not successful or Withdrawn. You can also delete them sooner with Delete bank details.
The Trust never asks for bank details by email or phone, and every email to applicants says so. If an applicant ever sends bank details by email, delete that email and ask them to use the account on the website.
Deleting applications (admins)
Admins can delete an application permanently: use Delete application at the bottom of its
page, or delete several at once (such as test applications) by ticking them in the List view
of Applications and choosing Delete selected. A box lists exactly what will go and warns
if a grant was approved or paid. To confirm, type the reference (or DELETE and the number of
applications) and press Delete permanently. It removes the application, its documents,
messages, notes, history and any share links, and cannot be undone. The audit trail records the
reference, not the personal details.
Use it for tests, and when the retention period in the privacy notice has passed (for example, two years after an unsuccessful application, six years after a paid grant).
Messages
Everything sent through Get in touch on the website arrives under Messages, with a
reference such as ENQ-7GDB3AV1, and is kept as a conversation. Any trustee can read and
answer. The list shows what is waiting for us; open one to see the conversation.
- Reply emails the person and adds the reply to the conversation, signed "The What Would Mia Do Trust" (they never see which trustee wrote it). Tick Close it after replying if that is the end of it; they can still reply, which opens it again.
- Private note is for other trustees only, and never shown to the person.
- Saved replies are standard answers any trustee can drop in and edit.
- Looked after by shows who is dealing with it. Whoever replies first takes it on, or use Take it on.
- AI summary sums up what they are asking and anything worrying; Draft a reply and Improve my reply suggest wording. Nothing is sent until you press Send reply.
- Mark as unread puts it back on the list as a reminder.
- Seen under our last reply shows when they read it.
People can send documents and photos with their messages, from their account, the tracking page or their phone. They show under the message: click one to open it in the page.
People with an account see the conversation in it. Without an account, they use the reference and a code we email them. Conversations are deleted two years after the last message. Trustees are reminded about messages waiting three days for a reply.
Referrals
Teachers, coaches and other professionals can refer a young person through the website, once the family has agreed to be contacted. We email the family an invitation straight away; when they sign in, an application starts with what the referrer told us already filled in. Referrals appear under Referrals (grants group), with where each one has got to: family invited, application started, application sent, or closed. The referrer is told when the family applies, but never the outcome, and the application shows that it came from a referral.
Donations and Gift Aid
The Donations tab lists every payment Square or GoCardless has confirmed, newest first, with how it was paid and any "in memory of" name. Direct Debit payments appear a few days after the donor signs up, once the money has been collected. Refunds and failed payments are handled in the Square or GoCardless dashboard.
What supporters can do themselves
Anyone who signs in with the email address they gave with sees Your giving in their account:
- every donation, grouped by tax year, with Gift Aid marked
- a printable statement for any tax year, for their records or Self Assessment
- their monthly Direct Debits, where they can change the amount, pause for 1 to 6 months, restart or cancel. The change is made in GoCardless straight away, GoCardless emails them to confirm, and we email them too. If someone cancels, trustees with "Donation changes" alerts get an email with their reason, if they gave one.
- their Gift Aid declaration, which they can add, update (name or address) or cancel. A new declaration also covers their unclaimed gifts from the last four years, as the declaration wording allows.
- a form to give again, monthly or once, choosing the collection day
Regular gifts can be monthly, every 3 months or yearly, by Direct Debit, or by card if you have turned that on under Donation settings. Card gifts are charged automatically by Square, and supporters manage them in the same way.
Monthly donors who signed up on the old WordPress site appear in their account after their next payment, once GoCardless has told us about it. If someone asks you to make a change for them, you can still do it in the GoCardless dashboard; the account updates itself.
Cheques
Supporters can give by cheque once they have signed in. They are given a reference (such as
CHQ-7KD2QX) to write on the back, and shown, and emailed, who to make it payable to and where to
post it. Trustees get an email too.
When a cheque arrives, go to Donations, find it under Cheques, check the amount and the date it arrived, and click Mark as received. The donor is thanked by email, it appears in their account, and Gift Aid is included if they declared it. If someone says they are not sending it after all, click Cancel (they can also cancel it themselves).
Donation settings (admins)
Donation settings controls the suggested amounts, which regular frequencies are offered, whether regular card gifts are allowed, and the cheque payee, postal address and instructions. The postal address is only shown to signed-in supporters. Amounts and options appear on the donation page after you publish.
Claiming Gift Aid
Every few months or at least once a year:
- Click Download unclaimed (CSV).
- Download HMRC's Gift Aid schedule spreadsheet from GOV.UK, and paste the rows in (they are in the same column order).
- Submit it through Charities Online.
- Back in the trustee area, click Mark all as claimed so those donations are not included next time.
Donors can cancel or update their own declaration in their account. Donations made before a cancellation can still be claimed.
Grant settings (admins)
Grant settings holds the next trustees' meeting date, the usual time to decide and to pay, when reminders and the "how is it going" follow-up are sent, how long before an application is highlighted as waiting, two-trustee sign-off, and the yearly grants budget with the month the financial year starts.
Audit trail (admins)
Audit trail lists everything anyone signed in has changed, and sensitive things they have looked at (such as bank details), with who, when and from where. Filter by person, or by Sign-ins only. What people typed is never recorded.
Import old applications (admins)
Import old applications brings in applications from the old website (WPForms or osTicket exports). The page explains each step and shows what it will import before anything is saved. Imported applications are marked as such.
Sign-in security (admins)
Sign-in security shows what the sign-in page does now, and has two settings:
- Second-step choices for trustees: for the authenticator app, passkeys and emailed codes, choose Available, Coming soon (shown greyed out with a badge, so people know it is on its way) or Hidden. This is what trustees see when they set up their sign-in and under Your sign-in. Anyone already using a method keeps it. The authenticator app (or emailed codes, once they work) must stay available, so new trustees can always finish setting up. Emailed codes can only be made available once the Trust's sign-in service sends email through Amazon SES.
- A passkey counts as both sign-in steps: leave it on, so trustees can choose between their passkey and their password with a code. It is put back automatically after every update of the website.
Email and spam protection (admins)
Email and spam protection sets how the website sends email (Amazon SES, or another mail server), sends a test email, and turns on the spam protection for the contact and donation forms.
Single sign-on (admins)
Under Single sign-on, admins can let trustees sign in with their Microsoft 365 or Google Workspace account, and supporters with Google, Apple or Facebook. The setup guide explains how to create each provider; the page shows the addresses to copy. Switch a provider on with Show on the sign-in page. Team shows who signs in with which provider.
Site status (admins)
Site status hides the website behind a holding page, for example before launch or while making big changes:
- Coming soon: "Our new website is on its way", with the Trust's email address.
- Maintenance: "We are making some improvements", asking people to try again soon.
- Open: the website as normal.
- Use the deployment setting: whatever the website was deployed with (see the setup guide).
You can add your own message, such as "We are back at 3pm on Saturday". The change reaches visitors within a minute, and nothing needs publishing. The trustee area keeps working, and every trustee's dashboard says when the website is hidden.
While it is hidden, the page gives a preview link. Opening it lets you see the real website on that device for a week. Share it only with trustees and people helping with the website, and use Make a new link if it has gone further than it should.
AI activity
The AI assistant page shows what the assistant has done in the last 30 days: application checks (and any that did not finish), writing suggestions for editors, tokens used and an estimated cost. Exact charges are on the AWS bill under Amazon Bedrock.
The website
Editors change the website from the trustee area. Nothing needs GitHub or any code.
Posts and events
Posts and events, then New post. Give it a title, a one or two sentence summary (shown on the news page and when the post is shared), and write the post. Use the buttons above the text box for bold, headings, lists, quotes, links and pictures, and Preview to see how it will look.
- Type: News, Story or Event. Events ask for the date, time and place, appear in "Upcoming events" on the home page until the day has passed, and can be filtered on the news page.
- Image: upload a JPEG, PNG or WebP photo (up to 5 MB) and describe it for people who cannot see it. Photos from a phone are fine.
- Status: Draft posts are saved but not shown on the website.
- Search description: what Google and social media show for the post. If you leave it blank, the summary is used.
- Suggest with AI reads the post and suggests a summary, a search description and titles, and Describe it with AI writes alt text for the photo. Nothing changes until you click Use this, and you can edit the result.
- Web address: made from the title. Change it before publishing, not after, or old links will break.
The first time, the Posts page offers to import the posts already on the website. Do this before publishing anything, or the existing posts will disappear from the site.
Page text
Page text lists the main pages (home, about, apply for a grant, donate, fundraise, questions
and answers, contact). Each one has
the wording that can safely be changed: headings, introductions, Mia's story, the testimonials on
the home page and so on. In headings, put words in *asterisks* to show them in the pink italic
style, for example Changing young lives *through sport.*. Use the original wording puts a part
back as it was.
- About: includes the charitable purpose, the list of trustees (one per line, "Name, role") and the accounts and governance paragraph. Update the income and spending each year after the annual return.
- Questions and answers: start each question with
##on its own line, then write the answer underneath. - The supporters' challenges on the Fundraise page, and the KidsOut partnership, are kept in
src/lib/charity.ts; ask whoever looks after the website to add new ones.
Banner
A strip across the top of every page, for something time-limited such as an event or appeal. Turn it on, write a short message, and optionally add a link.
Publishing
Changes are saved straight away but only appear on the website when someone clicks Publish the website now on the Publish page. It takes about three minutes, and the page shows when it has finished. You can make several changes and publish them together.
Developers can still add posts as Markdown files in src/content/news, but once posts are managed
in the trustee area, the trustee area is the one that counts when publishing.
Loading…