Cleanup after cloned content method

deploy/README.md

@@ -31,13 +31,11 @@ missing). Everything else runs inside containers.
 
 ## Publish the simplified portal from `main`
 
-1. In a checkout of `ctao/content`, switch to `main`. Copy the missing
-   Example files from `sample-content/pages/` and
-   `sample-content/uploads/hero.jpg` from this code repository into its root
-   `pages/` and `uploads/` directories, then commit the seed files. Preserve
-   any existing editorial versions of these files. Existing
-   news or other page files can remain in the content history; this portal
-   loads only the four Example files.
+1. Check that `ctao/content:main` contains the four Example files in `pages/`
+   (listed in `src/data/examples.json`) and the uploads they reference. They
+   are already committed there (`a3452d7`, "demo lorem ipsum pages"). News and
+   other page files can remain in the content repository; this portal loads
+   only the four Example files.
 2. Push the content branch to Gitea as `ctao/content:main`, and the code
    branch as `ctao/portal:main`. These are separate pushes; Bitbucket is
    not the deployment remote.
@@ -90,9 +88,8 @@ the previous portal may be restored.
    password never lands in a file or shell history:
    `podman exec -it ctao-demo-gitea gitea admin user create --admin --username <you> --email <you@…> --random-password`
 7. **[W]** In the Gitea UI: create org `ctao` with repos `portal` and
-   `content` (both public read). Seed the content `main` branch with
-   `sample-content/pages/` and `sample-content/uploads/` as described above.
-   Then, from your workstation, push both over
+   `content` (both public read). The content `main` branch needs the four
+   Example pages described above. Then, from your workstation, push both over
    the vhost with a repo-scoped token:
    `git push https://<user>:<token>@astro-git.isl-dev.grid.cyfronet.pl/ctao/portal.git main`
    `git push https://<user>:<token>@astro-git.isl-dev.grid.cyfronet.pl/ctao/content.git main`