docs: unify CLMS filenaming doc names and title pattern - #72
Conversation
Rename both docs to the shared clms-filenaming_<topic>_v1.qmd pattern, align both titles to 'CLMS Product Filenaming - <Topic>', and replace em dashes with plain hyphens throughout.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4c4dc15947
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| date: '2026-07-24' | ||
| subtitle: Copernicus Land Monitoring Service - Technical Library | ||
| title: CLMS Filename Tree | ||
| title: CLMS Product Filenaming - Filename Tree |
There was a problem hiding this comment.
These documents were already merged to main, and generate_url_paths() in .github/scripts/build/update_url_mappings.py derives the published HTML/PDF slugs directly from each source filename. Renaming both files therefore removes the existing guidelines/clms-filename-tree_v1.* and guidelines/clms-filenaming-design-principles_v1.* endpoints; the URL mapper treats the destinations as new keys and later deletes the old mappings rather than creating redirects. Keep the original filenames (titles can still change), or provide explicit compatibility redirects for both HTML and PDF URLs.
AGENTS.md reference: AGENTS.md:L130-L131
Useful? React with 👍 / 👎.
2 participants
Rename both docs to the shared clms-filenaming__v1.qmd pattern, align both titles to 'CLMS Product Filenaming - ', and replace em dashes with plain hyphens throughout.