> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/public-website/src/content/news/initial-public-website.md).

# Initial public website foundation

The FactionOS public website foundation is now in place.

This update establishes the product site package, shared shell, metadata helpers, sitemap posture, RSS endpoint, and typed publishing routes for blog and news entries. The site remains separate from the guided demo and public docs.

### What changed

* Astro output remains the deployment model.
* Blog and news content can be validated at build time.
* RSS and sitemap output can discover non-draft publishing routes.
* The site shell continues to avoid analytics, hosted forms, auth, and CMS behavior.

Later work owns final brand media, deeper page content, deployment evidence, and launch handoff checks.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://faction-os.gitbook.io/faction-os-docs/public-website/src/content/news/initial-public-website.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.