|
|
@ -65,15 +65,15 @@ place after an MSC has been accepted, not as part of a proposal itself.
|
|
|
|
Alternatively, use the Docker image at
|
|
|
|
Alternatively, use the Docker image at
|
|
|
|
https://hub.docker.com/r/klakegg/hugo/. (The "extended edition" is required
|
|
|
|
https://hub.docker.com/r/klakegg/hugo/. (The "extended edition" is required
|
|
|
|
to process the SCSS.)
|
|
|
|
to process the SCSS.)
|
|
|
|
2. Run `git submodule update --init --recursive` for good measure.
|
|
|
|
2. Run `npm i` to install the dependencies and fetch the docsy git submodule.
|
|
|
|
3. Run `npm i` to install the dependencies. Note that this will require NodeJS to be installed.
|
|
|
|
Note that this will require NodeJS to be installed.
|
|
|
|
4. Run `npm run get-proposals` to seed proposal data. This is merely for populating the content of the "Spec Change Proposals"
|
|
|
|
3. Run `npm run get-proposals` to seed proposal data. This is merely for populating the content of the "Spec Change Proposals"
|
|
|
|
page and is not required.
|
|
|
|
page and is not required.
|
|
|
|
5. Run `hugo serve` (or `docker run --rm -it -v $(pwd):/src -p 1313:1313
|
|
|
|
4. Run `hugo serve` (or `docker run --rm -it -v $(pwd):/src -p 1313:1313
|
|
|
|
klakegg/hugo:ext serve`) to run a local webserver which builds whenever a file
|
|
|
|
klakegg/hugo:ext serve`) to run a local webserver which builds whenever a file
|
|
|
|
change is detected. If watching doesn't appear to be working for you, try
|
|
|
|
change is detected. If watching doesn't appear to be working for you, try
|
|
|
|
adding `--disableFastRender` to the commandline.
|
|
|
|
adding `--disableFastRender` to the commandline.
|
|
|
|
6. Edit the specification 🙂
|
|
|
|
5. Edit the specification 🙂
|
|
|
|
|
|
|
|
|
|
|
|
We use a highly customized [Docsy](https://www.docsy.dev/) theme for our generated site, which uses Bootstrap and Font
|
|
|
|
We use a highly customized [Docsy](https://www.docsy.dev/) theme for our generated site, which uses Bootstrap and Font
|
|
|
|
Awesome. If you're looking at making design-related changes to the spec site, please coordinate with us in
|
|
|
|
Awesome. If you're looking at making design-related changes to the spec site, please coordinate with us in
|
|
|
|