FSFE/fsfe-website
27
33
Fork 93
Code Issues 64 Pull Requests 17 Wiki Activity

docs: fix some small issues
All checks were successful
continuous-integration/drone/pr Build is passing
Details

Browse Source
This commit is contained in:
Darragh Elliott
2025-08-26 16:25:30 +01:00
parent 99bfb8784f
commit b609967a13
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -45,7 +45,7 @@ Notable top level directories are:
And of course the different website folders.
And here are dome notable directories inside the folder for the main webpage, fsfe.org.
And here are some notable directories inside the folder for the main webpage, fsfe.org.
- `about`: Information about the FSFE itself, its team members etc
- `activities`: All specific FSFE activities
@@ -78,7 +78,7 @@ You can see the current status of translation progress of fsfe.org at [status.fs
[See the docs for more comprehesive and beginner-friendly documentation](https://docs.fsfe.org/en/techdocs/mainpage/buildlocally).
There are two ways to build and develop the directory locally. Initial builds of the webpages may take ~12 minutes, but subsequent builds should be much faster. Using the `--languages` flag to avoid building all supported languages can make this much faster. The `--sites` flag allows for building only some of the sites in this repo, which can also provide a speed boost to the developer experience. Run `./build.py --help` for more information.
There are two ways to build and develop the directory locally. Initial builds of the webpages may take ~6 minutes, but subsequent builds should be much faster. Using the `--languages` flag to avoid building all supported languages can make this much faster. The `--sites` flag allows for building only some of the sites in this repo, which can also provide a speed boost to the developer experience. Run `uv run build.py --help` for more information.
Alterations to build scripts or the files used site-wide will result in near full rebuilds.

2
docs/phase2.md
View File

@@ -11,7 +11,7 @@ It will
5. Processes the file, and puts the result into the output dir with name `<name>.<lang>.<html>`.
6. If the file name matches its parent directory name, IE it is in `<name>/<name>.<lang>.xhtml`, then generate an index symlink in the output dir.
7. Generate symlinks from `<name>.<lang>.html` to `<name>.html.<lang>`, for [Apache Multiviews](https://httpd.apache.org/docs/current/content-negotiation.html) (how we handle choosing pages based on user browser language)
8. Using some somewhat advanced XSL wizardry, Phase 2 is also able to build RSS and ICS files from XML data. The process of selecting stylesheets etc is the same as for XHTML>
8. Using some somewhat advanced XSL wizardry, Phase 2 is also able to build RSS and ICS files from XML data. The process of selecting stylesheets etc is the same as for XHTML.
9. Copies over any static files that are needed, like images, PDFs etc.
After phase 2 is over we have a copy of all sites built. If the site was not staged then it is in the target directory if it was staged, then it is in the staging directory.