Skip to content

Commit a2ba614

Browse files
author
bravegrape
authored
Merge pull request #151 from alphagov/add-signposting
Add signposting after moving `docs` folder content
2 parents 9ac03a2 + 2441420 commit a2ba614

11 files changed

+8
-465
lines changed

CONTRIBUTING.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,10 @@
33
Everybody who uses this project is encouraged to contribute to this project. If you're part of the [alphagov GitHub organisation](https://www.github.com/alphagov) you probably have write access to this repo. If you don't, ask a GitHub admin or #tech-docs-format on Slack.
44

55
- Before adding your feature, [check the backlog to see if someone is already talking about it](https://github.com/alphagov/tech-docs-template/issues)
6-
- If you add a new option to `config/tech-docs.yml`, make sure you [document the option in docs/configuration.md](docs/configuration.md)
7-
- If you add a new option to the page frontmatter, make sure you [document the option in docs/frontmatter.md](docs/frontmatter.md)
6+
- If you add a new option to `config/tech-docs.yml`, make sure you [document the new configuration option][configuration]
7+
- If you add a new option to the page frontmatter, make sure you [document the new frontmatter configuration](docs/frontmatter.md)
88
- You can test your contribution using [unit tests](spec/govuk_tech_docs), [javascript tests](spec/javascripts) or [integration tests](spec/features)
99
- If your change is relevant to the users of the gem, add something to [CHANGELOG](CHANGELOG.md). You don't have to do this if it's just refactoring. Make sure that you include any upgrade instructions.
10+
11+
[configuration]: https://github.com/alphagov/tdt-documentation/blob/master/source/amend_project/configuration/index.html.md.erb
12+
[frontmatter]: https://github.com/alphagov/tdt-documentation/blob/master/source/frontmatter.html.md.erb

docs/configuration.md

Lines changed: 1 addition & 226 deletions
Original file line numberDiff line numberDiff line change
@@ -1,228 +1,3 @@
11
# Configuration
22

3-
You can configure the site using `config/tech-docs.yml`. [See the PaaS tech docs for an example](https://github.com/alphagov/paas-tech-docs/blob/master/config/tech-docs.yml).
4-
5-
These are all the available options:
6-
7-
## `ga_tracking_id`
8-
9-
Tracking ID from Google Analytics
10-
11-
```yaml
12-
ga_tracking_id: UA-XXXX-Y
13-
```
14-
15-
## `github_repo`
16-
17-
Your repository. Required if [show_contribution_banner](#show-contribution-banner) is true.
18-
19-
```yaml
20-
github_repo: alphagov/example-repo
21-
```
22-
23-
## `github_branch`
24-
25-
Your github branch name. Useful if your default branch is not named master.
26-
27-
```yaml
28-
github_branch: source
29-
```
30-
31-
## `google_site_verification`
32-
33-
Adds a [Google Site Verification code](https://support.google.com/webmasters/answer/35179?hl=en) to the meta tags.
34-
35-
```yaml
36-
google_site_verification: TvDTuyvdstyusadrCSDrctyd
37-
```
38-
39-
## `enable_search`
40-
41-
Enables search functionality. This indexes pages only and is not recommended for single-page sites.
42-
43-
```yaml
44-
enable_search: true
45-
```
46-
47-
## `header_links`
48-
49-
Right hand side navigation.
50-
51-
Example:
52-
53-
```yaml
54-
header_links:
55-
Documentation: /
56-
```
57-
58-
## `footer_links`
59-
60-
Links to show in footer.
61-
62-
Example:
63-
64-
```yaml
65-
footer_links:
66-
Accessibility: /accessibility
67-
```
68-
69-
## `host`
70-
71-
Host to use for canonical URL generation (without trailing slash).
72-
73-
Example:
74-
75-
```yaml
76-
host: https://docs.cloud.service.gov.uk
77-
```
78-
79-
## `collapsible_nav`
80-
81-
Enable collapsible navigation in the sidebar. Defaults to false;
82-
83-
```yaml
84-
collapsible_nav: true
85-
```
86-
87-
## `multipage_nav`
88-
89-
Enable multipage navigation in the sidebar. Defaults to false;
90-
91-
```yaml
92-
multipage_nav: true
93-
```
94-
95-
## `max_toc_heading_level`
96-
97-
Table of contents depth – how many levels to include in the table of contents. If your ToC is too long, reduce this number and we'll only show higher-level headings.
98-
99-
```yaml
100-
max_toc_heading_level: 6
101-
```
102-
103-
## `phase`
104-
105-
```yaml
106-
phase: "Beta"
107-
```
108-
109-
## `prevent_indexing`
110-
111-
Prevent robots from indexing (e.g. whilst in development)
112-
113-
```yaml
114-
prevent_indexing: false
115-
```
116-
117-
## `redirects`
118-
119-
A list of redirects, from old to new location. Use this to set up external
120-
redirects or if [setting `old_paths` in the frontmatter](docs/frontmatter.md#old_paths) doesn't work.
121-
122-
```yaml
123-
redirects:
124-
/old-page.html: https://example.org/something-else.html
125-
/another/old-page.html: /another/new-page.html
126-
```
127-
128-
## `service_name`
129-
130-
The service name in the header.
131-
132-
Example:
133-
134-
```yaml
135-
service_name: "Platform as a Service"
136-
```
137-
138-
## `full_service_name`
139-
140-
The full service name (maybe with GOV.UK)
141-
142-
Example:
143-
144-
```yaml
145-
full_service_name: "GOV.UK Pay"
146-
```
147-
148-
## `service_link`
149-
150-
What the service name in the header links to.
151-
152-
default: '/'
153-
154-
```yaml
155-
service_link: "/"
156-
```
157-
158-
## `show_contribution_banner`
159-
160-
Show a block at the bottom of the page that links to the page source, so readers
161-
can easily contribute back to the documentation. If turned on [github_repo](#github-repo) is
162-
required.
163-
164-
Off by default.
165-
166-
```yaml
167-
show_contribution_banner: true
168-
github_repo: alphagov/example-repo
169-
```
170-
171-
## `source_urls`
172-
173-
Customise the URLs that the contribution banner links to. Only useful if
174-
[show_contribution_banner](#show_contribution_banner) is turned on. By default, "Report issue" links
175-
to raising a GitHub issue but by modifying the `report_issue_url` it can link to an email address
176-
or another page.
177-
178-
```yaml
179-
source_urls:
180-
report_issue_url: mailto:support@example.com
181-
```
182-
183-
## `show_govuk_logo`
184-
185-
Whether to show the GOV.UK crown logo.
186-
187-
default: `true`
188-
189-
```yaml
190-
show_govuk_logo: true
191-
```
192-
193-
## `api_path`
194-
195-
Define a path to an Open API V3 spec file. This can be a relative file path or a URI to a raw file.
196-
197-
```yaml
198-
api_path: ./source/pets.yml
199-
```
200-
201-
## `owner_slack_workspace` and `default_owner_slack`
202-
203-
These attributes are used to specify the owner of a page. See the separate
204-
[documentation for page expiry][expiry] for more details.
205-
206-
## `show_expiry`
207-
208-
Decides whether or not to show a red banner when the page needs to be reviewed.
209-
210-
If not present or set to `true`, the red banner will appear when the page needs to be reviewed. This is the default behaviour.
211-
212-
If set to `false`, the red banner will not appear when the page needs to be reviewed.
213-
214-
See the separate [documentation for page expiry][expiry] for more details.
215-
216-
[expiry]: https://tdt-documentation.london.cloudapps.digital/page-expiry.html#page-expiry-and-review
217-
218-
## `show_review_banner`
219-
220-
Decides whether or not to display the page review banner, regardless of whether the page needs to be reviewed or not.
221-
222-
If not present or set to `true`, the banner will be displayed on the page. This is the default behaviour.
223-
224-
If set to `false`, the banner will not be displayed.
225-
226-
See the separate [documentation for page expiry][expiry] for more details.
227-
228-
[expiry]: https://tdt-documentation.london.cloudapps.digital/page-expiry.html#page-expiry-and-review
3+
This content has been moved to <https://tdt-documentation.london.cloudapps.digital/amend_project/configuration/#configuration-options>.

docs/core-layout-without-sidebar.png

-174 KB
Binary file not shown.

docs/core-layout.png

-228 KB
Binary file not shown.

docs/expired-page.png

-74 KB
Binary file not shown.

0 commit comments

Comments
 (0)