Audience-based routing tool
This page is for choosing the right read order for families, officials, skeptics, or supporters without making them improvise their own route.
By audience
Different readers should be able to find the right lane without guessing.
Families, helpers, officials, skeptics, and supporters do not need the same first click. This page turns the platform into clearer routes by audience so the next step is easier to choose.
The goal is not to hide the deeper pages. It is to stop making every reader decode the whole site before finding the right doorway, packet, or proof layer.
Use this page fastUse in orderFamilies + helpersPress + officialsSkepticsSupporters + buildersCarry a guide
Use this page fast Start here fast Packets + guides Flagship dashboard Sources + proof
Page identity
This is the audience-specific routing page.
Use it when the right read order depends more on who the reader is than on the exact practical problem.
Route by reader type
Use it when the same site needs to behave differently for a family under stress than for a reporter or skeptical reader.
Use Find Help Fast when the problem is situational, not audience-based
If the issue is about the task rather than the reader, the search-first door should take over.
Pick the route here, then leave this page
This page should send each audience into the right working pages, packets, and proof layers quickly.
Use this page in order
Pick the reader type, then get them off the routing page.
By Audience is strongest when it quickly identifies the reader, gives the right read order, pairs the right packet, and hands off into the working page instead of keeping everyone in the routing layer.
01
Decide who this route is really for.
The site should behave differently for a family under pressure than for a journalist, official, skeptic, or supporter.
02
Start with the narrowest useful page, not the largest one.
Give each audience the shortest serious doorway before adding packets, proof layers, or the initiative materials.
03
Carry one guide or pack that matches the audience.
The point is to keep the route useful and portable, not to dump the whole site into one send.
04
Move into the page that actually does the work.
Once the reader type is clear, let Family Hub, Dashboard, Sources, or the Platform take over.
05
Use the initiative and deeper packets after the route is clean.
This page should keep the audience logic orderly instead of sending everyone to the heaviest lane first.
In the same routing lane
Keep the nearby pages close.
These nearby pages help people choose the right door before they carry deeper materials.
Start here fast
Use the calm first-step page when the next move needs to stay simple.
Open Start here fastFind help fast
Search the platform in plain language when you do not yet know the right page.
Open Find help fastPackets + guides
Carry the printable public-use materials without hunting across long pages.
Open Packets + guidesFamily Platform
Use the architecture page to understand how the help, proof, and reform lanes fit together.
Open Family PlatformNeed help now?
Crisis support should stay closer than every other link on this site.
If child-access pressure, family-court pressure, or fear for safety is making today feel dangerous or unbearable, start with crisis support, counseling, and the cleanest Maine justice doors first.
Use this page fast
Match the first read to the person using the site.
This is a routing layer, not a substitute for the deeper pages. Use it when the question is which doorway should come first.
Practical help comes before the public argument.
Use the calmer first-step and Family Hub routes first when someone is dealing with a hearing, paperwork, child support, housing strain, or safety planning.
The flagship record should come before the campaign framing.
Use the dashboard, sources, briefs, and packet shelf first when the job is public explanation, oversight, or legislative review.
Give the shortest possible route from claim to receipts.
Use the flagship page, evidence center, proof packets, and review checklist instead of arguing from fragments or screenshots.
Stay attached to proof before moving into share or build mode.
Use the flagship page, packet shelf, platform architecture, and tracker/standards materials after the public record is clear.
Operating rule: Families under immediate pressure should not be asked to start with the same page a reporter or skeptic should use. This page keeps the routes separate on purpose.
Families + helpers
Use the practical lane first when the pressure is real and current.
This route is for parents, relatives, advocates, and helpers who need the next step to be clearer before the bigger public record becomes useful.
It now includes a clearer paperwork lane and a clearer after-hearing lane so families are not forced to improvise after the room or at the filing counter.
Use this order
- Start Here by Situation
- Family Hub resources and plain-English tools
- Forms + Filing or After the Hearing when the paper or post-room follow-up is the real job
- Packets + Guides for the matching one-pager or pack
- Dashboard or sources later, when the practical pressure has eased enough to use them
Best packet matches
What this route is not
It is not legal advice and not a substitute for urgent safety planning. It is a calmer order for finding the right practical door without making someone absorb the whole platform first.
Press + officials
Use the public record first, then the protected initiative lane.
This route is for reporters, legislators, staff, skeptical civic readers, and anyone who needs the strongest route into the public record without hunting across tabs.
Use this order
- State of Maine Families dashboard
- Sources + proof and Briefs + Data
- Packets + Guides for the record pack and fast reads
- Initiative page and protected materials after the proof layer is already in view
Best packet matches
What to keep separate
Families in immediate stress should not have to start here. This is the public-record route: dashboard, receipts, packets, then initiative materials in that order.
Skeptics
Take the shortest disciplined route from claim to receipts.
This route is for people who want to verify the site rather than absorb it whole. It is designed to reduce argument by fragment and move straight into the actual record.
Use this order
- Dashboard for the public summary
- Evidence center for direct chart and source inspection
- Briefs + data and the skeptic packet
- Standards and tracker only after the proof layer is clear
Best packet matches
How this route stays fair
The goal is not to dodge scrutiny. It is to make scrutiny easier by keeping the path from claim to chart to source card to packet obvious.
Supporters + builders
Share or build from the site only after the proof layer is stable in view.
This route is for supporters, allies, validators, builders, and civic readers who want the broader platform context after the public record is already clear.
Use this order
- Dashboard and proof packets
- Family Platform page for architecture and broader purpose
- Standards and reform tracker for discipline and follow-through
- About, open letter, or share materials only after that
Best packet matches
Keep the share layer honest
The site is stronger when support materials stay attached to the proof layer, not when they float free of it.
Carry a guide
Take the shortest audience-matched guide with you.
These quick-route downloads are meant to reduce the work of explaining the whole site. They point readers to the right shelf, page, and packet by audience.
Families and helpers quick-route guide
The calmest read order for practical users who need help, translation, or a next step before the deeper public record.
Press and officials quick-route guide
The disciplined read order for reporters, legislators, staff, and other public readers who need the flagship record first.
Skeptics verification guide
The shortest route from claim to proof packet to source review.
Supporters and builders guide
The honest route for people sharing, validating, or building around the site after the public record is already clear.
Keep moving through the routing layer
Choose the right door, then carry only what helps.
Use the shortest entry page that fits the reader.
Different people need different first clicks: a calm start page, a search page, or an audience-specific reading order.
Move into packets and one-pagers once the route is clear.
The packet shelf should hold the printable materials without forcing anyone back through every long page.
Hand off into either the proof layer or the practical doors.
Routing pages should never dead-end; they should move people cleanly into proof, help, or both.
Public-record hardening
The dashboard, evidence layer, and citizen initiative now have a review spine.
Evidence standards
Claim matrix, source ladder, and safe public wording for proof-heavy materials.
Open standardsDashboard 2.0
Metric freshness, source limits, success measures, and data gaps.
Open dashboard methodInitiative red-team
Public issue register before the next initiative revision.
Open reviewAdministration accountability
Sharper public pressure: receipts, metrics, safety routing, and correction loops.
The accountability page now frames administrative drift and institutional delay as measurable public failures without profanity, personal attacks, or unsupported motive claims.
Public packets + access
The site now has reader-specific packets, structured SEO data, and stronger keyboard/mobile affordances.
Use public packets for reporters, officials, family helpers, skeptical reviewers, and public meetings. This lane also adds author/canonical metadata, JSON-LD, skip links, focus states, reduced-motion support, mobile tap-target hardening, and print-safe styles.