Skip to content

Commit d1a65b0

Browse files
authored
Merge pull request #505 from layer5io/chore/brokenlinks
contrib guide: broken links and release versioning
2 parents 15cabe0 + b770ca9 commit d1a65b0

File tree

1 file changed

+15
-22
lines changed

1 file changed

+15
-22
lines changed

content/en/contributing/contributing-to-docs.md

Lines changed: 15 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -153,17 +153,16 @@ The theme holds its styles in the [`assets/scss` directory](https://github.com/l
153153

154154
You can override the default styles and add new ones:
155155

156-
* To override templates or layouts, place your files in the main project directory (e.g., `layouts/partials/`) instead of editing the theme files under `themes/docsy/`.
157-
* Use the same file name and relative path as the theme. Hugo will look for files in the project first and fall back to the theme if no override is found.
156+
* In general, put your files in the project directory structure under `website` rather than in the theme directory.
157+
Use the same file name as the theme does, and put the file in the same relative position.
158+
Hugo looks first at the file in the main project directories, if present, then at the files under the theme directory.
158159

159-
For example, to override the theme’s navigation bar template:
160+
For example, the Layer5 website's [`layouts/partials/navbar.html`](https://github.com/layer5io/docs/blob/master/layouts/partials/navbar.html) overrides the theme's `layouts/partials/navbar.html`
160161

161-
```
162-
Project override: layouts/partials/navbar.html
163-
Theme default: themes/docsy/layouts/partials/navbar.html
164-
```
162+
* You can update the Layer5 website's project variables in the [`_variables_project.scss` file](https://github.com/layer5io/docs/blob/master/assets/scss/_variables_project.scss).
163+
Values in that file override the [Docsy variables](https://github.com/google/docsy/blob/main/assets/scss/_variables.scss).
164+
You can also use `_variables_project.scss` to specify your own values for any of the default [Bootstrap 4 variables](https://getbootstrap.com/docs/4.0/getting-started/theming/).
165165
166-
* To customize SCSS variables, update the `_variables_project.scss` file in the `assets/scss/` directory. This file overrides the theme’s SCSS variables and can also be used to redefine Bootstrap variables.
167166
* For adding custom CSS rules, use the `_styles_project.scss` file in the same `assets/scss/` directory.
168167
169168
### Image styling
@@ -261,20 +260,6 @@ Useful Hugo docs:
261260
* [Shortcode templates](https://gohugo.io/templates/shortcode-templates/)
262261
* [Shortcodes](https://gohugo.io/content-management/shortcodes/)
263262
264-
## Versioning of the docs
265-
266-
For each stable release, we create a new branch for the relevant documentation.
267-
For example, the documentation for the v0.2 stable release is maintained in the `v0.2-branch`.
268-
Each branch has a corresponding Netlify website that automatically syncs each merged PR.
269-
270-
The versioned sites follow this convention:
271-
272-
* `docs.layer5.io` always points to the current _master branch_
273-
* `master.docs.layer5.io` always points to GitHub head
274-
* `vXXX-YYY.docs.layer5.io` points to the release at vXXX.YYY-branch
275-
276-
We also hook up each version to the dropdown on the website menu bar.
277-
278263
Whenever any documents reference any source code, you should use the version shortcode in the links, like so:
279264
280265
```
@@ -283,6 +268,14 @@ https://github.com/layer5io/docs/blob/master/scripts/gke/deploy.sh
283268
284269
This ensures that all the links in a versioned webpage point to the correct branch.
285270
271+
<!-- ## Versioning of the docs
272+
For each stable release, we create a new branch for the relevant documentation.
273+
For example, the documentation for the v0.2 stable release is maintained in the [v0.2-branch](https://github.com/layer5io/docs/tree/v0.2-branch).
274+
@@ -257,7 +257,7 @@ The versioned sites follow this convention:
275+
* `vXXX-YYY.docs.layer5.io` points to the release at vXXX.YYY-branch
276+
We also hook up each version to the dropdown on the website menu bar.
277+
For information on how to update the website to a new version, see the [Layer5 release guide](https://github.com/layer5io/docs/blob/master/docs_dev/releasing.md#releasing-a-new-version-of-the-website). -->
278+
286279
## Markdown
287280
288281
Text can be **bold**, _italic_, or ~~strikethrough~~. [Links](https://gohugo.io) should be blue with no underlines (unless hovered over).

0 commit comments

Comments
 (0)