ghost.org valid

Ghost Developer Docs

For agents: Developer docs for Ghost, an open source Node.js publishing platform: install, self-host, hosting, update guides for independent publications.

ghost-cmspublishing-platformself-hostingnodejsopen-source-blogging

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:29:57.029Z. Cached copy · Source on ghost.org

# Ghost Developer Docs

- [Getting Started With Ghost](https://docs.ghost.org/index.md): Learn how to build and develop beautiful, independent publications
- [Introduction](https://docs.ghost.org/introduction.md): Ghost is an open source, professional publishing platform built on a modern Node.js technology stack — designed for teams who need power, flexibility and performance.
- [How To Install Ghost](https://docs.ghost.org/install.md): The fastest way to get started is to set up a site on **Ghost(Pro)**. If you're running a self-hosted instance, we strongly recommend an Ubuntu server with at least 1GB of memory to run Ghost.
- [Hosting Ghost](https://docs.ghost.org/hosting.md): A short guide to running Ghost in a production environment and setting up an independent publication to serve traffic at scale.
- [How To Update Ghost](https://docs.ghost.org/update.md): Learn how to update your self-hosted Ghost install to the latest version
- [Product Principles & Roadmap](https://docs.ghost.org/product.md): Developing Ghost as a product is a complex process undertaken by a small number of people with a great deal of care.
- [Architecture](https://docs.ghost.org/architecture.md): Ghost is structured as a modern, decoupled web application with a sensible service-based architecture.
- [Configuration](https://docs.ghost.org/config.md): For self-hosted Ghost users, a custom configuration file can be used to override Ghost’s default behaviour. This provides you with a range of options to configure your publication to suit your needs.
- [Staff Users](https://docs.ghost.org/staff.md): Staff users within Ghost have access to the admin area with varying levels of permissions for what they can do.
- [Publishing](https://docs.ghost.org/publishing.md): Posts are the primary entry-type within Ghost, and generally represent the majority of stored data.
- [Memberships](https://docs.ghost.org/members.md): The native Members feature in Ghost makes it possible to launch a membership business from any Ghost publication, with member signup, paid subscriptions and email newsletters built-in.
- [Recommendations](https://docs.ghost.org/recommendations.md)
- [Email Newsletters](https://docs.ghost.org/newsletters.md): Sites using the Members feature benefit from built-in email newsletters, where all posts can be delivered directly to segments of your audience in just a few clicks.
- [Ghost Security](https://docs.ghost.org/security.md): Ghost is committed to developing secure, reliable products utilising all modern security best practices and processes.
- [Ghost Handlebars Themes](https://docs.ghost.org/themes.md): The Ghost theme layer has been engineered to give developers and designers the flexibility to build custom publications that are powered by the Ghost platform.
- [Structure](https://docs.ghost.org/themes/structure.md): A Ghost theme contains static HTML templates that make use of helpers to output data from your site, and custom CSS for styling.
- [Contexts](https://
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=ghost.org · GET /v1/domain/ghost.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for ghost.org:
1. POST https://agentwebmap.com/v1/sites/ghost.org/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://ghost.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/ghost.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/ghost.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.