|
15 | 15 | - [Previewing the website using MkDocs](#previewing-the-website-using-mkdocs) |
16 | 16 | - [Building the website using the included Dockerfile](#building-the-website-using-the-included-dockerfile) |
17 | 17 | - [Hosting the website on OpenShift](#hosting-the-website-on-openshift) |
| 18 | + - [Finding pages that might be outdated](#finding-pages-that-might-be-outdated) |
18 | 19 |
|
19 | 20 | ## Starting as a writer |
20 | 21 |
|
@@ -256,3 +257,39 @@ delete your project or clean it with `oc delete`: |
256 | 257 | ```bash |
257 | 258 | oc delete all -l app=csc-user-guide-feature-a |
258 | 259 | ``` |
| 260 | + |
| 261 | +## Finding pages that might be outdated |
| 262 | + |
| 263 | +Each page in Docs CSC shows a "Last update" timestamp. To ensure that content |
| 264 | +stays up to date and valid, it is good practice to search for and check pages |
| 265 | +that have not been updated in a long time. A script `scripts/last_update.sh` |
| 266 | +is provided for this purpose that goes through the git log and prints for each |
| 267 | +`.md` file its last update timestamp and who made the most recent commit. |
| 268 | +Consider using the script from time to time to check pages that have not been |
| 269 | +touched in a while, say, 1-2 years. |
| 270 | + |
| 271 | +Run the script in the root of the repository as |
| 272 | + |
| 273 | +```bash |
| 274 | +bash scripts/last_update.sh |
| 275 | +``` |
| 276 | + |
| 277 | +You can also filter out pages that no one has touched after you using the `-u` |
| 278 | +option. The search pattern used here corresponds to your git username as |
| 279 | +defined in your git config (see `git config user.name`). |
| 280 | + |
| 281 | +```bash |
| 282 | +bash scripts/last_update.sh -u |
| 283 | +``` |
| 284 | + |
| 285 | +Note that if you've changed your git username recently, the results may be |
| 286 | +incomplete and you might need to manually grep for your commits. |
| 287 | + |
| 288 | +If you find something worth updating, please do so and create a PR to help us |
| 289 | +maintain Docs. If nothing needs to be modified, one way to update the timestamp |
| 290 | +without actually making any visible changes is to add a comment in the file |
| 291 | +using HTML tags, e.g. |
| 292 | + |
| 293 | +``` |
| 294 | +<!-- Page OK, add comment to update timestamp --> |
| 295 | +``` |
0 commit comments