|
1 | | -# TED Developer Documentation |
| 1 | +# docs-playground |
2 | 2 |
|
3 | | -This is the main repository responsible for the aggregation of all TED Developer documentation into https://docs.ted.europa.eu. |
| 3 | +This repository is a copy of [`OP-TED/OP-TED.github.io`](https://github.com/OP-TED/OP-TED.github.io) |
| 4 | +(*canonical repository*) maintained by the Release Wizard of the eForms |
| 5 | +Metadata Manager application (MDM) for testing the SDK release process |
| 6 | +automation. It is not the production site and it is not consumed by any |
| 7 | +downstream system. |
| 8 | + |
| 9 | +If you are looking for the real TED Developer Docs source, please use |
| 10 | +[`OP-TED/OP-TED.github.io`](https://github.com/OP-TED/OP-TED.github.io) |
| 11 | +instead. |
| 12 | + |
| 13 | +## How this repository differs from the canonical repository |
| 14 | + |
| 15 | +Three files are replaced by the wizard each time it refreshes this |
| 16 | +repository: |
| 17 | + |
| 18 | +- **This README.** The canonical repository's README describes the real |
| 19 | + TED Developer Docs site and would mislead anyone landing here by |
| 20 | + accident. It is replaced by the text you are now reading so that |
| 21 | + visitors are warned immediately. |
| 22 | +- **`.github/workflows/publish_site.yml`.** The canonical workflow runs |
| 23 | + a full Antora build of the documentation site, which requires |
| 24 | + `node_modules`, a `yarn.lock`, and several minutes of checkout and |
| 25 | + rendering. None of that is useful in a wizard test, where what |
| 26 | + matters is only that a workflow run progresses from *queued* to |
| 27 | + *running* to *completed* so the wizard's polling code can observe |
| 28 | + the transition. The replacement workflow is a sixty-second no-op |
| 29 | + that always succeeds. |
| 30 | +- **`antora-playbook.yml`.** The canonical playbook reads documentation |
| 31 | + content from `OP-TED/eforms-docs`. In the playground it is rewired |
| 32 | + to [`OP-TED/eforms-docs-playground`](https://github.com/OP-TED/eforms-docs-playground) |
| 33 | + so that the test cycle stays self-contained: the branches and |
| 34 | + content the wizard pushes during testing live in the docs-playground |
| 35 | + mirror of the docs repository, and this playbook reads from there. |
| 36 | + |
| 37 | +GitHub Pages is also not enabled on this repository, so even the stub |
| 38 | +workflow does not publish anything that would be visible on the public |
| 39 | +web. |
| 40 | + |
| 41 | +## How this repository is refreshed |
| 42 | + |
| 43 | +The MDM Release Wizard exposes a refresh button on the *Start a new |
| 44 | +release* card. The operator may press it at any time before starting |
| 45 | +a release test. The button opens a dialogue in which one or more |
| 46 | +playground repositories may be selected for refresh. When this |
| 47 | +repository is selected, the wizard force-pushes the canonical |
| 48 | +repository's current state onto it, deletes any branches and tags |
| 49 | +that do not exist on the canonical, and then re-applies the three |
| 50 | +overlay files listed above (this README included). |
| 51 | + |
| 52 | +The refresh button is shown only when the MDM instance is configured |
| 53 | +to use playground repositories — that is, in development and other |
| 54 | +non-production deployments. In production, where MDM is configured |
| 55 | +against the canonical repositories, the button is not shown and the |
| 56 | +underlying endpoints are disabled. |
| 57 | + |
| 58 | +Because every refresh erases local state on this repository, please |
| 59 | +do not open pull requests against it, do not push commits to it, and |
| 60 | +do not rely on its branches, tags, or GitHub Releases as a source of |
| 61 | +truth. The authoritative artefacts live on the canonical repository |
| 62 | +linked above. |
| 63 | + |
| 64 | +## Other playground repositories used for testing the SDK release process |
| 65 | + |
| 66 | +The MDM Release Wizard maintains a small family of playground |
| 67 | +repositories under the same `OP-TED` organisation, each mirroring the |
| 68 | +corresponding canonical repository for testing: |
| 69 | + |
| 70 | +- [`OP-TED/eforms-sdk-playground`](https://github.com/OP-TED/eforms-sdk-playground) |
| 71 | + — mirror of [`OP-TED/eforms-sdk`](https://github.com/OP-TED/eforms-sdk), |
| 72 | + used to test the SDK release flow itself. |
| 73 | +- [`OP-TED/eforms-docs-playground`](https://github.com/OP-TED/eforms-docs-playground) |
| 74 | + — mirror of [`OP-TED/eforms-docs`](https://github.com/OP-TED/eforms-docs), |
| 75 | + used as the target of the wizard's documentation export step. |
| 76 | +- [`OP-TED/eforms-sdk-analyzer-playground`](https://github.com/OP-TED/eforms-sdk-analyzer-playground) |
| 77 | + — mirror of [`OP-TED/eforms-sdk-analyzer`](https://github.com/OP-TED/eforms-sdk-analyzer), |
| 78 | + used to test the analyser release flow that runs in parallel with |
| 79 | + the SDK release. |
| 80 | + |
| 81 | +Each of these repositories carries a similar README and is refreshed |
| 82 | +by the wizard in the same way. |
0 commit comments