# Stage

> How to edit your site in place, publish, run campaigns and read the numbers.

- [Stage documentation](https://docs.stage.systems/index.md): Edit your website in place, publish when you are ready, and run campaigns you can measure end to end.
- [Quickstart](https://docs.stage.systems/getting-started/quickstart.md): Change a headline on your site and publish it. Five minutes, start to finish.
- [How Stage works](https://docs.stage.systems/getting-started/how-stage-works.md): You edit the live site, on the live site, and publish when you are ready. The two-minute version.
- [Opening the admin](https://docs.stage.systems/getting-started/opening-the-admin.md): Where the admin is, how to sign in, what the two roles can do, and what each part of the screen is for.
- [Troubleshooting](https://docs.stage.systems/getting-started/troubleshooting.md): The handful of things that go wrong, what each one means, and what to do.
- [Glossary](https://docs.stage.systems/getting-started/glossary.md): The words Stage uses, in plain terms.
- [Edit mode](https://docs.stage.systems/editing/edit-mode.md): Switch on Edit, click into the page, and publish when you are done. What you can click, and what happens when two people edit at once.
- [Text, links and images](https://docs.stage.systems/editing/text-and-images.md): Change words, format them, add links, and swap pictures, all in place.
- [Adding, reordering and removing](https://docs.stage.systems/editing/structure.md): Lists on the page, such as logos, cards, slides or questions, can grow, shrink and reorder. The layout never changes to make that possible.
- [Publishing](https://docs.stage.systems/editing/publishing.md): Publish makes your changes live. What that means for pages, articles and forms, and what to do when it fails.
- [Articles and the blog](https://docs.stage.systems/editing/articles.md): Write posts in the real design, keep them private until they are ready, schedule them, and publish.
- [Forms](https://docs.stage.systems/editing/forms.md): Build a form in place, publish it, and read every response in the Inbox with what the person read before writing.
- [Media library](https://docs.stage.systems/editing/media.md): Every image and video on the site in one place. Upload, generate, download originals, and delete safely.
- [Content shared between pages](https://docs.stage.systems/editing/referenced-content.md): Some content shows in several places. Edit it from any of them and every copy updates.
- [Team and private sites](https://docs.stage.systems/editing/team-and-access.md): Invite people, set roles, approve access requests, and put the whole site behind sign-in with one switch.
- [Settings](https://docs.stage.systems/editing/settings.md): What an admin can change under Settings, pane by pane.
- [Campaigns](https://docs.stage.systems/campaigns/overview.md): Post to X, LinkedIn and Instagram from one place, on a schedule, and see which post brought which visitor and enquiry.
- [Creating a campaign](https://docs.stage.systems/campaigns/creating-a-campaign.md): From a blank canvas to scheduled posts. Connect your accounts once, then compose, schedule, and let Stage post.
- [Channels](https://docs.stage.systems/campaigns/channels-and-posts.md): What X, LinkedIn and Instagram each support, what the visitor sees, and which numbers come back.
- [Campaign links](https://docs.stage.systems/campaigns/links-and-attribution.md): Every link in a post carries a short code. The visitor sees a clean address, and their visit counts toward the post for 30 days.
- [The funnel](https://docs.stage.systems/campaigns/funnel.md): Clicks, visits, engaged and enquiries for one campaign, per channel and per post. What each stage means and how to read it.
- [Setting up a tracking funnel](https://docs.stage.systems/campaigns/setting-up-a-funnel.md): From nothing to a campaign that reports clicks, visits, engagement and enquiries per post. About 20 minutes the first time.
- [Analytics](https://docs.stage.systems/analytics/overview.md): What the Performance tool shows, how fresh it is, and how it fits with Google Analytics if you use that too.
- [What is counted](https://docs.stage.systems/analytics/what-is-counted.md): What a visit is, when the consent prompt applies, and what Stage never stores about a visitor.
- [Inbox and people](https://docs.stage.systems/analytics/inbox-and-people.md): Every form response and enquiry, with what the person read before writing and how often they had visited.
- [AI activity](https://docs.stage.systems/analytics/ai-crawlers.md): Which AI companies read your site, and when an assistant fetched a page for a real person.
- [Building on Stage](https://docs.stage.systems/developers/index.md): What a Stage site is made of, the contract a site must meet to be editable and measurable, and how these pages are organised.
- [Set up a site](https://docs.stage.systems/developers/setup.md): Start from the client template, give it an org and the shared credentials, and get a green /admin locally.
- [Edit anchors](https://docs.stage.systems/developers/editing/anchors.md): The inert data-e-* attributes a renderer emits so the editor can map a click back to a component id and a field path.
- [Components](https://docs.stage.systems/developers/editing/components.md): Build a renderer for a component type, register it, and it is editable. The reference Hero, the registry, media slots and shared content.
- [The write model](https://docs.stage.systems/developers/editing/write-model.md): Content is addressed by a stable id and a dotted path. Saves are compare-and-swap on a version counter with a three-way merge on conflict.
- [Page schemas](https://docs.stage.systems/developers/structure/schemas.md): Editing needs no schema. Adding does. A per-site schema declares which fields are lists, what a new item looks like, and what the edit notch offers.
- [The edit notch](https://docs.stage.systems/developers/structure/edit-notch.md): Edit mode never changes the page's layout or presentation. Structural actions live in a tab on the section's right edge, and components meet a small contract to support it.
- [Blog setup](https://docs.stage.systems/developers/structure/blog.md): Give a site articles: the renderers, the routes, the listing page, and the one schema that drives the editor's content-type menu.
- [Forms setup](https://docs.stage.systems/developers/structure/forms.md): Give a site forms: the question renderers, the overlay, the preview canvas, and the schema entries. Question types are platform constants; their look is the site's.
- [Media](https://docs.stage.systems/developers/media/pipeline.md): Uploads go through the API to object storage and get WebP variants at four widths. Renderers address them by convention, and a slot can hold an image or a video.
- [Next.js sites](https://docs.stage.systems/developers/next/overview.md): Stage on Next.js: the same packages and the same contract, plus an adapter that supplies the React anchors, the admin mount, and a zero-JS edit canvas.
- [Wiring](https://docs.stage.systems/developers/next/wiring.md): The files a Next.js Stage site has and what each one does: registry, public page, edit canvas, browse canvas, admin, article body, media slot, publish handler, env.
- [Tracking](https://docs.stage.systems/developers/analytics/tracking.md): How a page view becomes a row, what the site includes to make that happen, the consent gate, the engagement beacon, and the hooks a site can call.
- [Campaign landing](https://docs.stage.systems/developers/analytics/campaign-landing.md): A request carrying a campaign code is counted, stamped with a first-party cookie, and redirected to the clean URL. Sites get it by re-exporting the middleware.
- [Custom funnels](https://docs.stage.systems/developers/analytics/custom-funnels.md): What a site can measure today with the hooks that exist, and the shape of the funnel SDK that is being built.
- [API](https://docs.stage.systems/developers/reference/api.md): The shared Stage API. One deployment, every secret, org-scoped on every route.
- [Data model](https://docs.stage.systems/developers/reference/data-model.md): The tables behind Stage, grouped by what they hold. Every row carries an org id.
- [Middleware](https://docs.stage.systems/developers/reference/middleware.md): One edge middleware, shipped by the SDK and re-exported by every site, runs campaign landings, the private-site gate and visit logging in front of every request.
- [Versioning and releases](https://docs.stage.systems/developers/reference/releases.md): Two packages, one version, pinned exactly per site. The shared API and database move for everyone at once, so they only ever change additively.
- [Environment variables](https://docs.stage.systems/developers/reference/env.md): What a site deployment holds, what the shared API holds, and what a site must never hold.