Stack scanning
Discover technologies and server information from the live website to understand how a static site is built.
Static site management
Manage static sites and GitHub content together.
Scan static website stacks, edit GitHub content, and monitor client sites alongside your WordPress portfolio.
STATIC SITE MANAGEMENT
GitHub content workspace
Field Notes · fieldnotes.co
Repositoryfield-notes/site
ContentMarkdown and frontmatter
PublishingCommit to selected branch
THE ORBIT DESK
Give static websites a complete maintenance record.
Connect the live URL and GitHub repository to keep the technical stack, content, uptime, audits, and client work together. Edit supported Markdown content without switching to a separate content management system.
GitHub content editor
Edit Markdown and frontmatter, prepare drafts, and manage supported media in a content workflow connected to the repository.
Monitoring and client care
Follow uptime, SSL, Lighthouse audits, tasks, contracts, and reports from the same agency portfolio.
The example uses illustrative data. Content editing depends on the connected repository structure and supported content types. Git commits use your existing deployment pipeline.
Care continues after launch
The site is static. The client relationship keeps moving.
A brochure site or campaign page still has an owner, a production URL, a source repository, and a client who expects it to work. A new request or availability issue needs the same clear follow-through as any other site in your portfolio.
Orbit combines stack scanning, Git-connected content editing, and monitoring around the live site. Your deployment pipeline keeps its role, while the agency has a shared place to review the technology, update supported content, and manage client work.
A closer look
Git content and live website care.
Manage supported repository content while keeping the production website visible in the agency portfolio.- GitHub connection
- Connect an authorized repository and branch to the static website record.
- Markdown and frontmatter
- Use the editor for supported Markdown content and its frontmatter fields, based on the repository structure.
- Drafts and media
- Prepare content drafts and supported media before committing a change to the repository.
- Stack scans and audits
- Review detected technologies, SSL information, availability, and Lighthouse findings for the live website.
How it works
From repository connection to content commit.
Keep editorial changes connected to the source your team already maintains.
- Source
Connect GitHub
Authorize access and associate the repository and branch with the site.
- Inventory
Discover the content
Inspect supported content collections and the Markdown files and frontmatter fields they contain.
- Editing
Prepare a draft
Edit content and supported media, saving a draft while the change is being reviewed.
- Git
Commit the change
Write approved content to the selected repository branch; your existing build and hosting workflow handles deployment.
Repository content and website maintenance, together.
Examples describe the available workflow; the interface previews use illustrative data.
| Git content and live website care. | Content workflow | Live website care |
|---|---|---|
| Source | GitHub repository and branch | Website URL and site profile |
| Review | Markdown, frontmatter, and draft changes | Stack scan and Lighthouse findings |
| Publish | Commit supported changes to the selected branch | Existing pipeline builds and deploys |
| Agency work | Content tasks and site context | Monitoring, contracts, and reports |
Why it matters
One agency workspace for a mixed website portfolio.
The tools differ by site type, while the maintenance record stays consistent.
IN PRACTICE
Content teams
Make supported Markdown and frontmatter changes through a structured editor.
Developers
Keep content in GitHub and retain the deployment pipeline already used by the site.
Agency managers
Review WordPress and static sites together with their client, monitoring, and maintenance context.
Keep exploring
The rest of the site story.
Connect the services that support your static site content, analytics, and maintenance workflow.