Run
Operate the generator, reader delivery and optional writing process as separate responsibilities. Begin with the checked local installation in Start, then select the configuration and hosting pattern you actually need. A static reader does not need a MarkStack server or database on its public host.
Choose an operating task
| Need | Guide |
|---|---|
| Branding, prefixes and assets | Configuration |
| Build, Publish and release gates | Build and publish |
| Static host or private writer process | Hosting and team setup |
| Roles, requests and privacy | Security and privacy |
| Backups, upgrades and diagnosis | Operations and maintenance |
Configuration explains installed file settings and selected runtime overrides. Build and publish explains how each process selects inputs and replaces output. Hosting covers public/private readers and the optional private editor. Security describes enforced boundaries without converting them into certification. Operations covers retained state and return paths.
Decide the deployment shape
| Shape | What you operate |
|---|---|
| Files/Git, public reader | Build pipeline and static host |
| Files/Git, private reader | Build plus host/network reader gate |
| Local browser writing | Loopback editor and private data |
| Remote team writing | Private editor, TLS/proxy and supervision |
| Separate audiences | Separate reviewed inputs and artifacts |
Reader access and writer access are different. Editor accounts do not protect published HTML or search. Hidden folders remain generated and can be discoverable. Upload only the intended reader artifact, not source/private runtime or the checkout root.
The editor is optional and separate. It is not deployed with this public showcase. If no browser writer is needed, do not add a writing service merely because the repository includes one. Remote editor use needs a deliberate private perimeter, trusted proxy settings, secure cookie behavior and tested roles.
Follow one controlled release
Confirm the engine/runtime and selected source/configuration/data first. Build to expendable output, inspect the artifact, exercise the reader and review its audience. Keep the previous accepted artifact, deploy through your actual host process, then check home, deep routes, search, assets, missing routes and cache on the live host.
Administrator Publish changes local output only. Git review, commit/push and provider deployment stay separate. A generated count or provider success message is not the whole acceptance result. Review and release names the gates and evidence to retain.
Keep recoverable state
| State | Recovery |
|---|---|
| Markdown and site media | Source history and backups |
| Config and customizations | Reviewed compatible copies |
| Private accounts and runtime | Restricted consistent backup |
| Generated reader | Known accepted prior artifact |
| Service, proxy and domain | Actual setup and rehearsal |
| Browser unsaved buffer | Preserve before reload/access changes |
HTML is rebuildable only when its inputs remain available. An old output copy is not an account backup, and restoring old HTML does not undo newer account changes. Coordinate writers and rehearse recovery on disposable copies before relying on it.
The service, DNS, TLS and hosting snippets are templates for your installation. Local syntax/tests do not certify production deployment, capacity, accessibility or compliance. Use Validation limits to distinguish retained local evidence from checks still required on your actual system.