Multi-stepKnowledge
Give useful knowledge a familiar address.
Organize guides and resources, publish a browsable hub, and use an already verified custom domain.
A complete worked example
Make the approved guidance easy to find under your own name.
Acorn has several published client guides and a verified custom domain. The next step is giving those materials a clear home.
Fictional project and sample data. This preview does not submit, publish, or change access.
Intended resource readers · illustrative result
A useful place to start.
Find the guidance for the part of the project you are working on.
- Getting started
- How the project works and what happens next
- Brand guide
- Approved logo, color, and type guidance
- Handover
- How to use the finished deliverables
Maintained guidance
The old campaign checklist is flagged for its owner rather than silently treated as current. The custom domain provides the address; linked documents still enforce their own access settings.
What the recipient can access
The hub and guides explicitly available to each reader.
Kept out of this handoff
Restricted guides, unpublished drafts, and the maintenance checklist.
How it runs
- Choose the resourcesIdentify the guides and files that belong in the library.
- Publish the structureOrganize folders and a clear landing page with useful navigation.
- Keep it usefulPublish on the verified domain and revise the existing pages as guidance changes.
- You getA branded starting point for guides that can keep improving at stable links.
A prompt to start with
Copy this into your AI tool after connecting it to Fermium. Replace the bracketed details and let it ask for the context it needs.
Create a resource hub for [audience] from [approved resources]. Organize the navigation, preserve each document’s access, and publish using our already verified custom domain [domain]. Keep source links and flag outdated material.
What this workflow needs
Custom domains require an eligible plan and completed DNS setup. Publishing a hub does not grant access to every linked resource.
Can it also proxy another application under this domain?
Current custom domains host Fermium content. Arbitrary application proxying is separate planned work.