Use main branch to simpyfy config
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# CTAO Science Portal — simple proof of concept
|
||||
|
||||
The `simple` branch uses the sibling `mockup` project's layout, assets, CSS,
|
||||
The `main` branch uses the sibling `mockup` project's layout, assets, CSS,
|
||||
and header interactions. Astro generates a static site. Sveltia CMS edits
|
||||
exactly four Markdown pages in the separate `ctao/content` repository.
|
||||
|
||||
@@ -80,10 +80,10 @@ needed to display the button. A Markdown blockquote receives the mockup's
|
||||
highlight styling. Images without alternative text are treated as decorative.
|
||||
Menu labels, ordering, URLs, and the shared site layout remain code-controlled.
|
||||
|
||||
Remote editing uses Gitea OAuth and saves to **`ctao/content`, branch `simple`**.
|
||||
Remote editing uses Gitea OAuth and saves to **`ctao/content`, branch `main`**.
|
||||
That branch must contain the four files from `sample-content/pages/` and the
|
||||
sample upload before publishing this version. The code mirror is
|
||||
**`ctao/portal`, branch `simple`**. Deployment independently selects
|
||||
**`ctao/portal`, branch `main`**. Deployment independently selects
|
||||
`CODE_BRANCH` and `CONTENT_BRANCH`, overlays content, runs checks, and publishes
|
||||
atomically. `CONTENT_BRANCH` must match `backend.branch` in the CMS config.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user