Bring Your Bills — site map

Every page on the website, who it's for, and what you need to open it.

Everything lives under bringyourbills.org.au. The same list is on the site itself, as All pages — linked from the footer of every page. The links below go to the live site. The staff pages are not named anywhere public — you reach them by signing in at the hub, and the passcode, not the address, is what keeps them shut.

• bringyourbills.org.au Also reachable as bringyourbills.com.au, bringyourbills.au and byb.org.au — all the same site.
  • For anyone coming along The chat bubble, BYB Helper, is on every page in this branch.
    • Home /index.html Open The next event, what to bring, what happens on the day.
    • Can't wait for an event? /need-help.html Open National Debt Helpline, Lifeline, 1800RESPECT, Beyond Blue, Kids Helpline, and what to do in an emergency. Linked as a red button from the home page header, at every width.
    • See all events /calendar.html Open "Find an event near you" by postcode, then every upcoming event as a list.
    • Can't make it? Hear about the next one /keep-in-touch.html Open A mobile number or email to be told about the next event, plus optional tick boxes for why they can't come and which days and times suit. Linked from the home page and every event page. Staff read the list in Supabase and send the messages by hand; the dashboard shows counts only.
    • Map of events /map.html Open A pin per event. Events with no address are listed underneath so they're never lost.
    • One event's page /event.html?id=<event id> Open Reached from the calendar or the map. Full details, who's attending, add to calendar, directions.
    • Let us know you're coming /attend.html Open Optional. Name, phone and email can all be left blank.
    • All pages /pages.html Open This same list, on the site. Linked from the header of every page.
    • Your privacy /privacy.html Open Plain-English. Linked from the footer of every page.
    • Page not found /404.html Open Shown for a mistyped address; points back to the calendar.
  • For services & partner organisations No chat bubble on these — they're working pages, and the email address is printed on them.
    • Register your service for an event /register.html Open No code needed — this is the way in. SECL approves it by hand, and approving a service's first registration is what creates its service code.
    • Add, change or remove an event /request.html Service code Also where a logo is submitted. Partner requests wait for approval; SECL's own passcode applies instantly.
    • Record who you helped, on the day /seclinternalsurvey.html Service code One entry per person helped, about twenty seconds. Never a name or contact detail.
    • Your service's own numbers /impact.html Service code Each service sees only its own. Add ?service=Name to pre-fill it.
  • SECL staff Behind one door. The staff pages are not named on the public site — sign in at the hub and your own links appear. They are hidden from search engines, and the passcode is checked again by the server on every request.
    • Staff & partner sign-in /hub.html Staff passcode Also takes a service code, and shows that service its own set of links instead. Signing in here means the pages it lists don't ask for the code again.
    • Behind it, for staff: the review queue, registrations & stallholders & service codes, and the impact dashboard. For a service: the survey, its impact page, the event form and stallholder registration.
  • Guides Linked from the footer of every page.
    • Guides index /docs/guides/ Open Four printable PDFs, plus a longer written guide per audience.
    • 1 — How services register PDF Open
    • 2 — How we approve PDF For staff
    • 3 — Using the website on the day PDF Open
    • 4 — How to use the website PDF Open

How someone actually moves through it

Who	The usual path
Someone needing help with a bill	Home → See all events → (postcode search) → the event's page → optionally Let us know you're coming. They can also just turn up.
A service, first time	Register your service → SECL approves → confirmation email with their service code → on the day, the survey → afterwards, their impact page.
A service, after that	Register your service (2 minutes, details remembered), or Add/change an event with their code.
SECL staff	Review requests → email the new code → Registrations for planning and exports → Dashboard for reporting.

Files, not pages

Published alongside the pages. Worth knowing they exist, because anything in them is public.

File	What it is
/events.json	Every event. Downloaded by every visitor, so nothing private can go in it.
/services.json	The service directory — names and logo paths.
/sitemap.xml	The map for search engines. Deliberately lists the public pages only.
/robots.txt	Tells search engines to leave the staff pages alone.