Alfred Co.Host docs portal
I owned the Alfred Co.Host docs portal end to end — information architecture, visual identity, the build, and every word inside it. The hard part was never the writing; it was staying genuinely helpful without ever being obvious.
Role
Docs portal owner
Timeframe
2023 – present
Scope
Information architecture · Visual identity · Content · Multilingual
The challenge
Alfred Co.Host is an enhanced hospitality AI assistant. Through the Alfred Co.Host Platform, owners build its knowledge base — text and media — run subscriptions in parallel across properties, and wire up every touchpoint. It isn’t a static interface product: you’re configuring something destined for an AI, which is a different mental model entirely.
That’s exactly where the documentation challenge lived. Alfred’s audience is worldwide and spans 25 to 65, and I couldn’t assume that everyone — given who they are — arrived equally fluent in tech, let alone in how to think for an AI. I had to make genuinely new concepts clear enough for a first-timer without ever talking down to a pro. Helpful, never obvious.
The approach
How I kept it clear
Strict information mapping
Every page answers one question and one job-to-be-done, mapped out before a single word was written.
Shallow, scannable structure
A deliberately flat hierarchy — fewer levels, less nesting — so no one gets lost three clicks deep.
Disambiguation hubs
Clear hub cards that route lookalike concepts to the right place — before confusion ever starts.
UI-identical terminology
Every term mirrors the product UI exactly, and stays consistent across every translation.
Conversational by design
The docs answer back
The GPT assistant underneath is one I built and wired up myself — not an off-the-shelf widget. It doesn’t just read pages back: it surfaces resources that are genuinely relevant, because I curated and piloted what it’s allowed to recommend.
Curated, not generic
It points to the right guide, not the nearest keyword match — every recommended resource is one I vetted and steered.
Dynamic multilingual
It detects the language from the user’s browser and replies in it — unless they write in another language — and builds links straight to the correctly translated page.
Built with
A lean docs-as-code stack, shipped continuously.
GitHub
Single source of truth for the docs — versioned, reviewed, and the trigger for every deploy.
Netlify
Continuous delivery — every push to GitHub ships the portal live, no manual steps.
Docsify
Powers the site, but the components are overridden and designed by me — not the default theme.
GPT assistant
A custom AI assistant I built and wired in — integrated directly into the portal.
Pain points
Honest about what’s left
Full accessibility optimization isn’t done yet — a matter of time and resources, not intent. Even so, the design-led choices I made (informed by the accessibility training I’ve taken) carry their weight: the portal already scores 93.4% on Eye-Able. The mobile experience can be sharper too — I know it, and closing both gaps is next on my list.
See it live
Explore the portal
See widescreen website ↗Get in touch
Let’s talk.
Got a project, a role, or just want to swap kitty pictures and plant-based recipes? I’d love to hear from you.