Help site language guardrail
Sniffopotamus has a product site, an app, and a help site. This Docusaurus site is the help and setup manual. It should be organised by audience and task, not by internal implementation order.
Help front-door rule
The homepage and top navigation should make immediate sense to someone looking for help:
- Fragrance lovers
- Couples and gifters
- Creators and reviewers
- Online stores
- Physical boutiques and counters
- Fragrance brands
- Developers and agencies
- Research and trend teams
Use clear guide language before internal vocabulary. Say "single users and collectors" before "consumer acquisition", "retailers and Shopify stores" before "B2B wedges", and "MCP and AI agent users" before "commercial agent access" unless the page is specifically technical.
Where internal language belongs
Revenue, billing, implementation, schema, MCP scopes, corpus rules, and Shopify readiness belong in deeper guide pages. They are still important, but the first job of this site is to help the reader find the right guide.
Main site cover
The consumer app at sniffopotamus.com needs a separate polished public cover
before broad promotion. That is not this Docusaurus homepage. The .com cover
should explain the product. This .dev site should explain how to use, set up,
connect, and build with the product.
Copy checks
Before shipping public pages, check:
- Could a non-technical fragrance lover understand the headline?
- Does the page explain what the reader can do next?
- Are internal words like "monetisation", "sellable surface", "substrate", "substrate", "corpus", and "commercial path" pushed below the help intro?
- Are retailer, brand, and builder sections framed by benefits first?
- Is private user data described as protected, aggregated, and consent-aware?