# Sites and Distribution

Once a course exists there are several ways to get it to people, and they can all be
used at once.

| Channel | What it is |
|---|---|
| **Share link** | Best for quickly sharing one course with internal colleagues or learners. The permanent link's reach is set per course: workspace only, request access, or anyone with the link, within a ceiling the workspace administrator sets. |
| **Explore** | An in-workspace catalog with curated sections that can target specific groups. Off by default for team workspaces until an administrator curates it. |
| **Sites** | Branded external documentation, customer and partner academies, and public learning destinations on your own domain. Covered in detail below. |
| **Assignments** | Required or recommended work for named internal learners, students, or groups: a course or a slice of it, an optional due date, and completion criteria. See [assignments](https://honen.com/llms/assignments.md). |
| **LMS** | LTI 1.3, SCORM 1.2 and 2004, Google Classroom, and xAPI or cmi5. See [LMS integrations](https://honen.com/llms/lms-integrations.md). |
| **Standalone activity links** | A single topic or activity delivered on its own, with progress still counting toward the course. |

---

# Honen Sites

Honen Sites turns selected courses into a branded public learning destination with its
own home page, catalog and full course experience, while authoring, analytics and
learner management stay inside the same workspace.

**Sites is the public front door. The workspace is the house.** One content pipeline
serves internal teams and external community learners, and you decide what each
audience sees.

## The problem it solves

Organizations that want to offer courses outside their internal LMS usually stitch
together separate tools:

| The usual approach | What breaks |
|---|---|
| A marketing site plus a separate course platform | Two systems to maintain, inconsistent branding, learners bouncing between URLs |
| A public course library that only links out to enroll | No real preview; visitors cannot experience anything before signing up |
| Opening the full internal LMS to the public | Internal roles, permissions and cohort data get messy quickly |
| A custom-built branded learning portal | Expensive, slow, and diverges from the real product over time |
| A documentation or help site | Static reading only. No activities, no tutor, no evidence anyone learned anything |

## What it replaces

- **Course storefront platforms** such as Thinkific, Teachable and Kajabi, when Honen
  is already your LMS and you do not want a second content system.
- **Public course landing pages plus a separate enrollment flow.** The Site *is* the
  enrollment surface.
- **Custom-branded learning portals** built by agencies or internal developers.
- **Link-out resource hubs** that only list PDFs and video links.
- **Documentation and developer-docs portals** such as Mintlify, ReadMe, Docusaurus and
  GitBook. Product docs, API references and SDK guides become interactive courseware
  with real activities and an in-context AI tutor.
- **Customer-education and enablement academies** in the Skilljar mould: product
  training, certifications and community enablement from the same workspace instead of
  a separate platform and content pipeline.
- **Community, alumni and partner access** currently managed through ad-hoc invites and
  shared links.

Sites does not replace your internal workspace. Internal instructors, cohorts,
assignments and analytics stay where they are.

## Key benefits

**One platform, two audiences.** Build courses once, publish a subset publicly.
Internal and external learners share the same underlying content and see only what you
expose.

**Try before committing.** Visitors browse the catalog, open a course and start
learning with no account, and they get the real experience rather than a watered-down
demo. One login unlocks the tutor, projects and saved progress.

**Your brand, not ours.** Logo, social preview image, custom navigation links, custom
footer, your own subdomain on day one, and custom domains such as
learn.yourcompany.com.

**Clean external isolation.** People who sign up become community learners: a dedicated
role with its own permissions and usage limits, landing in a per-site group, seeing
only that site's courses, and getting a branded home rather than an admin dashboard.

**No duplicate content work.** The public experience uses the same components as
internal courses, so what visitors preview is exactly what they get after signing up.

**Curated like a storefront.** Arrange courses into rows: "Start here", "Advanced
tracks", "New this quarter". Hide, reorder and publish when ready.

**SEO-ready by default.** Published sites are indexable, course detail pages carry
proper metadata, and you control the social preview image, so a catalog can appear in
search rather than sitting behind a login wall.

**Controlled costs for public learners.** External learners have their own entitlement
limits, configurable per workspace, so you decide how much free access to offer before
a paid seat or internal enrollment.

## What is gated, and what is not

**Available with no login:** readings, flashcards, quizzes, lectures, podcasts, comics
and games, with free navigation through the lesson sidebar.

**Requires login:** the AI tutor, hands-on projects, saved progress, and the full
course experience.

Public browsing is read-only until login, so there are no phantom learner records.
After signing in, a visitor is auto-enrolled as a community learner in the site's
group, keeps their deep links, and continues where they left off.

## Documentation, developer relations and customer education

This is the use case most often missed. Static docs tools stop at reading; academy
platforms give you customer training as a separate platform and content pipeline. Sites
collapses both into the workspace you already run.

Point product docs, API references, SDK guides or onboarding playbooks at the
Course-Editor agent and they become interactive courseware: the same reading a docs
site would show, plus quizzes, hands-on coding and sandbox activities, and a tutor that
answers questions in context. Anyone can browse with no login; one login takes a
developer or customer into the tutor, runnable projects and saved progress.

- **Developer relations.** Ship API and SDK education on your own domain: public,
  SEO-indexed, hands-on, and matched to the same source your team maintains.
- **Customer education.** Product training, certifications and enablement tracks
  without a second subscription.
- **Community enablement.** Open courses with gated advanced tracks behind signup, and
  clean isolation from internal operations.

## Setting one up

Create a site and name it, drag published courses into sections, configure branding and
SEO, and publish. Optionally point your own domain at it.

Workspace administrators manage Sites by default, and can grant a Manage Sites
permission to instructors who should own the public storefront without full admin
access.

**A workspace can run several sites at once.** A university might run separate
continuing-education and alumni sites with different catalogs; a company might run a
partner training portal alongside a community hub.

Where a workspace has a primary custom domain configured, internal users signing in can
be redirected to the branded domain automatically, so the custom domain acts as a full
application alias rather than only a public skin.

## Concepts

| Concept | Meaning |
|---|---|
| Site | A curated, publishable storefront belonging to one workspace |
| Site sections | Rows of courses on the home page, like explore categories |
| Subdomain | Provisioned automatically when you create a site |
| Custom domain | Optional branded URL bound to a site or workspace |
| Community learner | External role for people who sign up through a site: limited permissions, site-scoped access, excluded from workspace seat counts |
| External group | Per-site group community learners are enrolled into automatically |
| Publish / unpublish | Controls public accessibility; unpublishing revokes external access |

## Typical deployments

| Organization | How Sites is used |
|---|---|
| Corporate L&D | Public onboarding previews for candidates; a partner certification portal on their own domain |
| Trade unions and associations | Member continuing-education catalog; apprenticeship resources open to prospects |
| Higher and continuing education | Alumni learning library; non-credit storefront separate from the formal LMS |
| Training vendors and consultancies | White-labeled delivery for clients without granting workspace admin access |
| Nonprofits and community organizations | Free public courses, with gated advanced tracks behind signup |
| Developer relations | A public API and SDK academy: docs that teach, with hands-on activities and an in-context tutor |
| Enterprise SaaS | A customer education hub on your own domain rather than a third-party platform |

## What Sites is not

- **Not a separate product.** It is a layer on the workspace you already have, not a
  second content silo.
- **Not anonymous progress tracking.** Public browsing is read-only until login.
- **Not a full website builder.** You configure navigation, footer, branding and course
  layout, not arbitrary CMS pages. Your marketing site stays your marketing site.
- **Not a replacement for internal cohort management.** Groups, assignments, grading
  and analytics for enrolled classes stay in the workspace.

## Standalone activity links

Separately from Sites, any topic or single activity can be delivered on its own: no
course navigation, just the work and a single onward action when it is complete.
Progress still counts toward the parent course. This is what makes a Honen activity
embeddable inside a chat message, an email, an onboarding flow, or another product.

## Catalog publishing and review

Catalogs have covers, descriptions, browse pages, audiences, courses, and ordered curricula. Connect them to groups or Sites. Team workspaces can require reviewers and an approval count per catalog; submitted versions remain fixed during review. See [Publishing and Review](https://honen.com/llms/publishing-and-review.md).

## Site access and documentation

A private Site can require approval after sign-in. Site owners review Access requests on the workspace Sites page and approve or deny visitors.
Owners can remove an approved visitor's access grant. Visitor access is separate from permission to edit or publish the Site.
Sites provide llms.txt and llms-full.txt for published guides, subject to Site access rules.
A visitor assistant can answer questions about the Site's published API reference. Refresh the imported specification when its source changes.
Use the workspace Brand in Site design and Site assistant instructions. Search results can provide an assistant action when the visitor assistant is enabled.
