HueLifeCMO Knowledge Base

Naming documents in this knowledge base

← HubSpot

How to title a document so people can find it. Written after the HubSpot category reached 54 documents and became hard to scan.

The short version

Why this exists

The HubSpot category has 54 documents, and 24 of them used to begin with the word "HubSpot". Sorted alphabetically, that put almost half the page in a single unreadable block under H, where the only thing distinguishing one entry from the next was the seventh word onwards.

The fix has two halves. Documents are now grouped by what they are for, which is derived from the folder they live in. And titles should lead with the subject, so that scanning a group tells you something.

The pattern

Area: what the reader gets
Instead ofWrite
✓Set up your HubSpot booking linkMeetings: set up your booking link
✓Segment (List) Naming Conventions & CleanupLists: naming conventions
✓Custom Contact Field Fill Rates (FULL population), HueLifeContacts: which custom fields are actually used
✓Sequences vs Workflows, when to use whichWorkflows: sequences vs workflows
✓Making WordPress & Arlo registrants marketable in HubSpotContacts: making registrants marketable
✓HubSpot CLI commands overview (reference)CLI: commands overview

The area list

Keep to these. A new area is fine when something genuinely does not fit, but two words meaning the same thing is how the problem started.

AreaCovers
ContactsContact records, properties, fields, data quality, marketable status
ListsLists, segments, audiences
EmailMarketing email, templates, deliverability
FormsForms and what happens after a submission
WorkflowsAutomation, sequences, enrolment
MeetingsBooking links and calendar
CoursesThe Course object, classes, sessions, cohorts
CampaignsCampaign records, naming, attribution
AdsAd accounts, pixels, audiences
ReportingDashboards, attribution, analytics
CLIThe hs command line tool and the developer platform
AIBreeze, assistants, agents, MCP
AuditThe state of our own portal, as found

Prefixes that are not areas

Source:Somebody else's material, HubSpot's docs, a vendor blog, a video transcript. Signals "useful, but not our decision."
Start here:The one document a newcomer should read first in that area. Use sparingly, two per category at most.

Where a document goes

The group a document appears under on a category page is derived from its folder, not its title. So putting the file in the right place matters more than what you call it.

FolderAppears under
hubspot-audit/Our HubSpot
planning/, segment-strategy/, class-operations/How we work
hubspot-automation/, smart-email-clients/hubspot-automation/Automation & CLI
onboarding-doc/transcripts/Learning
anything named source-* or *sources*Reference

Overrides live at the top of public/_build-category.py for the handful of documents where the folder is misleading.

Adding a document

  1. Write the .html file into the right folder under public/.
  2. Add a card for it anywhere in the category page, position does not matter.
  3. Run python3 public/_build-category.py public/hubspot.html. It regroups, re-sorts and rebuilds the filter.
  4. Update the count on index.html and add an entry to search-index.json.
  5. Commit and push. Sevalla redeploys on push.

The filter box

Each category page has a filter that matches as you type. It tolerates typos and partial words , bookng finds the booking link document, audt finds the audits, by matching the letters you typed in order, within a single word of the title. Groups with no remaining matches hide themselves, so what is left on screen is only what is relevant.

It only searches titles, which is the reason titles have to be good. The site-wide search on the front page searches full document text as well.


Written September 2026, after the HubSpot category passed 50 documents.