|
1 |
| -# Page Template |
2 |
| - |
3 |
| -## Some introductory subtitle |
4 |
| - |
5 |
| -!!! tip "TLDR" |
6 |
| - - **very brief** summary of the main findings |
7 |
| - - any key links i.e. to forms or other things people need fill in |
8 |
| - - try to keep it to just three |
9 |
| - |
10 |
| -??? question "Why should we care?" |
11 |
| - - Brief summary of why this is important |
12 |
| - - any key links of background |
13 |
| - - We can have a bigger section on this below |
14 |
| - |
15 |
| -??? success "Pre-requisites" |
16 |
| - * Some information on what someone might need to be familiar with before they can use this page |
17 |
| - |
18 |
| - |Pre-requisite | Importance | Note | |
19 |
| - |--------------|------------|------| |
20 |
| - |[Some link to some other guide we have](https://nhsdigital.github.io/rap-community-of-practice/)|Necessary/Helpful|Any comment we have on this| |
21 |
| - |some other guide|Helpful|another note| |
22 |
| - |
23 |
| -!!! info inline end |
24 |
| - XKCD comics can also be great at grabbing attention: |
25 |
| - |
26 |
| -  |
27 |
| - |
28 |
| -**Don't forget to update the `mkdocs.yml` file to add this page, so it appears in the nav bar!** |
29 |
| - |
30 |
| -Here we need some bit explaining the background of the thing the page is talking about |
31 |
| - |
32 |
| -- keep it brief |
33 |
| -- make it clear what it is and what the benefit is |
34 |
| -- don't go into details of the methods, but perhaps highlight some of the key approaches described below |
35 |
| - |
36 |
| -## First subtitle of the main content |
37 |
| - |
38 |
| -Talk about the issue break it down into steps. |
39 |
| - |
40 |
| -We might even include a little diagram: |
41 |
| - |
42 |
| -```mermaid |
43 |
| -graph LR |
44 |
| - A[Have an idea] --> B{Make a page}; |
45 |
| - B -->|Pull Request| C[Colleagues Review]; |
46 |
| - C --> D[Feedback]; |
47 |
| - D --> B; |
48 |
| - B ----->|Approved| E[Publish!]; |
49 |
| -``` |
50 |
| - |
51 |
| -Consider linking to other pages and try and extract the general concept from language specific implementations, i.e. we could have a pager about "functions", and then link to specific pages on how to do functions in Python and R. |
52 |
| - |
53 |
| -Also, have a look on the following pages to see if they have guidance we could link to, or adapt |
54 |
| -- [Quality Assurance of Code for Analytics](https://best-practice-and-impact.github.io/qa-of-code-guidance/intro.html) |
55 |
| -- [Turing Way](https://the-turing-way.netlify.app/welcome.html) |
56 |
| -- [Central RAP Guidance from GSS](https://analysisfunction.civilservice.gov.uk/support/reproducible-analytical-pipelines/) |
57 |
| - |
58 |
| -## General subsection template |
59 |
| - |
60 |
| -Write some content here |
61 |
| - |
62 |
| -### General subsubsection template |
63 |
| - |
64 |
| -This might be on some specific aspect of the subsection |
65 |
| - |
66 |
| -#### General subsubsubsection template |
67 |
| - |
68 |
| -We might need to get even more specific, but probably wont use this as much! |
69 |
| - |
70 |
| -## Further subtitles |
71 |
| - |
72 |
| -You can include code snippets `inline` or in blocks: |
73 |
| - |
74 |
| -```Python |
75 |
| - print("hello world") |
76 |
| -``` |
77 |
| - |
78 |
| -You might also want to hide large code snippets: |
79 |
| - |
80 |
| -??? example "Some big code snippet" |
81 |
| - ```Python |
82 |
| - print("HA, I lied, it's only a small code snippet") |
83 |
| - ``` |
84 |
| - |
85 |
| -!!! note |
86 |
| - Admonition blocks can be helpful to bring out key points |
87 |
| - |
88 |
| - See [mkdocs guidance]() |
89 |
| - |
90 |
| -## Further subsections |
91 |
| - |
92 |
| -Continue to work through the subject, but we don't have to make the pages long - a short page can be just as useful! |
93 |
| - |
94 |
| -You can include pictures, however referencing them requires a few steps back in the directory tree (see below): |
95 |
| - |
96 |
| - |
97 |
| - |
98 |
| -You can also have tabs: |
99 |
| - |
100 |
| -=== "Tab 1" |
101 |
| - We can put whatever we want in here |
102 |
| - ```Python |
103 |
| - def somefunc(a): |
104 |
| - return None |
105 |
| - ``` |
106 |
| - |
107 |
| -=== "Tab 2" |
108 |
| - And in here something completely different, such as a diagram |
109 |
| -  |
110 |
| - |
111 |
| -## Further Reading |
112 |
| - |
113 |
| -- Provide any useful links people might need to further their learning |
| 1 | +--- |
| 2 | +title: Add your title here |
| 3 | + |
| 4 | +# Uncomment and add your tags here |
| 5 | +# tags: |
| 6 | +# - |
| 7 | +--- |
| 8 | + |
| 9 | +# |
| 10 | + |
| 11 | +## Some introductory subtitle |
| 12 | + |
| 13 | +!!! tip "TLDR" |
| 14 | + - **very brief** summary of the main findings |
| 15 | + - any key links i.e. to forms or other things people need fill in |
| 16 | + - try to keep it to just three |
| 17 | + |
| 18 | +??? question "Why should we care?" |
| 19 | + - Brief summary of why this is important |
| 20 | + - any key links of background |
| 21 | + - We can have a bigger section on this below |
| 22 | + |
| 23 | +??? success "Pre-requisites" |
| 24 | + * Some information on what someone might need to be familiar with before they can use this page |
| 25 | + |
| 26 | + |Pre-requisite | Importance | Note | |
| 27 | + |--------------|------------|------| |
| 28 | + |[Some link to some other guide we have](https://nhsdigital.github.io/rap-community-of-practice/)|Necessary/Helpful|Any comment we have on this| |
| 29 | + |some other guide|Helpful|another note| |
| 30 | + |
| 31 | +!!! info inline end |
| 32 | + XKCD comics can also be great at grabbing attention: |
| 33 | + |
| 34 | +  |
| 35 | + |
| 36 | +**Don't forget to update the `mkdocs.yml` file to add this page, so it appears in the nav bar!** |
| 37 | + |
| 38 | +Here we need some bit explaining the background of the thing the page is talking about |
| 39 | + |
| 40 | +- keep it brief |
| 41 | +- make it clear what it is and what the benefit is |
| 42 | +- don't go into details of the methods, but perhaps highlight some of the key approaches described below |
| 43 | + |
| 44 | +## First subtitle of the main content |
| 45 | + |
| 46 | +Talk about the issue break it down into steps. |
| 47 | + |
| 48 | +We might even include a little diagram: |
| 49 | + |
| 50 | +```mermaid |
| 51 | +graph LR |
| 52 | + A[Have an idea] --> B{Make a page}; |
| 53 | + B -->|Pull Request| C[Colleagues Review]; |
| 54 | + C --> D[Feedback]; |
| 55 | + D --> B; |
| 56 | + B ----->|Approved| E[Publish!]; |
| 57 | +``` |
| 58 | + |
| 59 | +Consider linking to other pages and try and extract the general concept from language specific implementations, i.e. we could have a pager about "functions", and then link to specific pages on how to do functions in Python and R. |
| 60 | + |
| 61 | +Also, have a look on the following pages to see if they have guidance we could link to, or adapt |
| 62 | +- [Quality Assurance of Code for Analytics](https://best-practice-and-impact.github.io/qa-of-code-guidance/intro.html) |
| 63 | +- [Turing Way](https://the-turing-way.netlify.app/welcome.html) |
| 64 | +- [Central RAP Guidance from GSS](https://analysisfunction.civilservice.gov.uk/support/reproducible-analytical-pipelines/) |
| 65 | + |
| 66 | +## General subsection template |
| 67 | + |
| 68 | +Write some content here |
| 69 | + |
| 70 | +### General subsubsection template |
| 71 | + |
| 72 | +This might be on some specific aspect of the subsection |
| 73 | + |
| 74 | +#### General subsubsubsection template |
| 75 | + |
| 76 | +We might need to get even more specific, but probably wont use this as much! |
| 77 | + |
| 78 | +## Further subtitles |
| 79 | + |
| 80 | +You can include code snippets `inline` or in blocks: |
| 81 | + |
| 82 | +```Python |
| 83 | + print("hello world") |
| 84 | +``` |
| 85 | + |
| 86 | +You might also want to hide large code snippets: |
| 87 | + |
| 88 | +??? example "Some big code snippet" |
| 89 | + ```Python |
| 90 | + print("HA, I lied, it's only a small code snippet") |
| 91 | + ``` |
| 92 | + |
| 93 | +!!! note |
| 94 | + Admonition blocks can be helpful to bring out key points |
| 95 | + |
| 96 | + See [mkdocs guidance]() |
| 97 | + |
| 98 | +## Further subsections |
| 99 | + |
| 100 | +Continue to work through the subject, but we don't have to make the pages long - a short page can be just as useful! |
| 101 | + |
| 102 | +You can include pictures, however referencing them requires a few steps back in the directory tree (see below): |
| 103 | + |
| 104 | + |
| 105 | + |
| 106 | +You can also have tabs: |
| 107 | + |
| 108 | +=== "Tab 1" |
| 109 | + We can put whatever we want in here |
| 110 | + ```Python |
| 111 | + def somefunc(a): |
| 112 | + return None |
| 113 | + ``` |
| 114 | + |
| 115 | +=== "Tab 2" |
| 116 | + And in here something completely different, such as a diagram |
| 117 | +  |
| 118 | + |
| 119 | +## Further Reading |
| 120 | + |
| 121 | +- Provide any useful links people might need to further their learning |
0 commit comments