# Landing Page Editor > Use when editing, updating, or iterating on a workspace's landing page HTML (the magazine-style /w/:slug page). Supports incremental edits — fetch the current HTML, make targeted changes, then write it back. NOT for initial generation — that comes from the `brief` field which runs the server-side LANDING_PAGE_PROMPT against Gemini. - Skill: `astriaai/landing-page-editor` (Agent Skill) - Install (CLI): `npx skillmds@latest add astriaai/landing-page-editor` - Raw SKILL.md: https://api.skillmd.com/api/skills/astriaai/landing-page-editor/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend - Author: astriaai (https://skillmd.com/u/astriaai) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/astriaai/landing-page-editor --- # Workspace Landing Page Editor The workspace landing page (rendered at `/w/:slug`) is a single self-contained HTML blob stored on `workspace.landing_page_html`. It is generated from scratch by the server-side `LANDING_PAGE_PROMPT` whenever a `brief` is submitted — that path overwrites the HTML wholesale. For ANY change that should not regenerate the whole page (typography tweaks, layout edits, adding a section, changing copy, swapping an image, fixing a tagline), edit the HTML directly and write it back. Do NOT send a `brief` unless the user wants a full regeneration. All commands use the `astria` CLI (see the `astria-api` skill). Pass `-w ` to target the workspace. ## Constraints carried over from `LANDING_PAGE_PROMPT` When editing, preserve these invariants (the live `/w/:slug` page depends on them): - The output is **inner body HTML** — no ``, ``, ``, or `` tags - Styling uses **Tailwind utility classes** (already loaded on the page). Use `