|
1 | 1 | --- |
2 | | -draft: true # Set to false when ready to publish |
| 2 | +draft: true # Set to false when ready to publish |
3 | 3 | title: 'Insert title here' |
4 | 4 | publishDate: YYYY-MM-DD |
5 | 5 | params: |
6 | | - # Add and remove authors as needed. Please reserve authorship for significant contributions, not edits and feedback. |
7 | | - authors: [ |
8 | | - {name: "INSERT_NAME_1", handle: "INSERT_HANDLE_1"}, |
9 | | - {name: "INSERT_NAME_2", handle: "INSERT_HANDLE_2"}, |
10 | | - ] |
| 6 | + |
| 7 | +# Add and remove authors as needed. Please reserve authorship for significant contributions, not edits and feedback. |
| 8 | + |
| 9 | +authors: [ |
| 10 | +{name: "INSERT_NAME_1", handle: "INSERT_HANDLE_1"}, |
| 11 | +{name: "INSERT_NAME_2", handle: "INSERT_HANDLE_2"}, |
| 12 | +] |
11 | 13 |
|
12 | 14 | # Classifications of the framework to drive key concepts, design principles, and architectural best practices |
| 15 | + |
13 | 16 | pillars: |
14 | | - - placeholder |
15 | | - - placeholder |
| 17 | + |
| 18 | +- placeholder |
| 19 | +- placeholder |
16 | 20 |
|
17 | 21 | # The areas of the GitHub adoption journey. Inspiration taken from docs.github.com |
| 22 | + |
18 | 23 | areas: |
19 | | - - placeholder |
20 | | - - placeholder |
| 24 | + |
| 25 | +- placeholder |
| 26 | +- placeholder |
21 | 27 |
|
22 | 28 | # Classifications of industries who may be at different stages of the customer journey. |
| 29 | + |
23 | 30 | verticals: |
24 | | - - placeholder |
25 | | - - placeholder |
| 31 | + |
| 32 | +- placeholder |
| 33 | +- placeholder |
26 | 34 |
|
27 | 35 | # Individuals in key roles on the customer journey, typically consisting of one or more administrators and the end-user community. |
| 36 | + |
28 | 37 | personas: |
29 | | - - placeholder |
30 | | - - placeholder |
| 38 | + |
| 39 | +- placeholder |
| 40 | +- placeholder |
31 | 41 |
|
32 | 42 | # Deployment options for GitHub Enterprise, including Cloud (GHEC), Server (GHES), and Hybrid. |
| 43 | + |
33 | 44 | platform: |
34 | | - - placeholder |
35 | | - - placeholder |
| 45 | + |
| 46 | +- placeholder |
| 47 | +- placeholder |
36 | 48 |
|
37 | 49 | # GitHub product functions designed to support every stage of development. |
| 50 | + |
38 | 51 | features: |
39 | | - - placeholder |
40 | | - - placeholder |
| 52 | + |
| 53 | +- placeholder |
| 54 | +- placeholder |
41 | 55 |
|
42 | 56 | # Deeper-level topics of the GitHub Platform and its features. They are most often interacted with by end-users. |
| 57 | + |
43 | 58 | components: |
44 | | - - placeholder |
45 | | - - placeholder |
| 59 | + |
| 60 | +- placeholder |
| 61 | +- placeholder |
46 | 62 |
|
47 | 63 | # Associated teams and other GitHub and Partner resources that can provide additional support. |
| 64 | + |
48 | 65 | github: |
49 | | - - placeholder |
50 | | - - placeholder |
| 66 | + |
| 67 | +- placeholder |
| 68 | +- placeholder |
| 69 | + |
51 | 70 | --- |
52 | 71 |
|
53 | 72 | <!-- This disables the linting rule for multiple top-level headers --> |
54 | 73 | <!-- markdownlint-disable MD025 --> |
55 | 74 |
|
56 | 75 | <!-- |
57 | | -See our CONTRIBUTING doc for submission details and additional writing style guidelines: https://github.com/github/github-well-architected-internal/blob/main/CONTRIBUTING.md |
| 76 | +See our CONTRIBUTING doc for submission details and additional writing style guidelines: https://github.com/github/github-well-architected/blob/main/CONTRIBUTING.md |
58 | 77 | --> |
59 | 78 |
|
60 | 79 | ## Scenario overview |
| 80 | + |
61 | 81 | <!-- Provide a brief overview of the scenario that your article will cover. Be as generic, yet opinionated, as possible. --> |
62 | 82 |
|
63 | 83 | ## Key design strategies and checklist |
| 84 | + |
64 | 85 | <!-- This section should discuss the key design strategies that your proposed solution employs. This could include architectural patterns, coding practices, |
65 | | -and other strategic decisions that were made during the design of the solution. |
| 86 | +and other strategic decisions that were made during the design of the solution. |
66 | 87 |
|
67 | 88 | The checklist should provide a list of key steps or considerations that should be followed when implementing the solution. This could include things like |
68 | 89 | "Ensure all code is properly commented", "Write tests for all new functionality", "Verify the associated teams and resources", etc. --> |
69 | 90 |
|
70 | 91 | ## Assumptions and preconditions |
| 92 | + |
71 | 93 | <!-- List any assumptions or preconditions that your article is based on. Be as generic, yet opinionated, as possible. --> |
72 | 94 |
|
73 | 95 | ## Recommended deployment |
| 96 | + |
74 | 97 | <!-- Describe the recommended GitHub Platform deployment that your article will propose. This will typically zoom in on GitHub Platform products, features, and technologies you would prescribe. --> |
75 | 98 |
|
76 | 99 | ## Additional solution detail and trade-offs to consider |
| 100 | + |
77 | 101 | <!-- Write more detail about the solution and articulate opinionated prescriptions, trade-offs, or consequences of either the deployment, the assumptions, or the desired goals. Be as generic, yet opinionated, as possible. --> |
78 | 102 |
|
79 | 103 | ## Seeking further assistance |
| 104 | + |
80 | 105 | <!-- The Hugo shortcode below will fully populate this section --> |
81 | 106 |
|
82 | 107 | {{% seeking-further-assistance-details %}} |
|
0 commit comments