|
4 | 4 | section: extensions |
5 | 5 | # Sidenav secondary level section |
6 | 6 | # should be the same for all markdown files for each extension |
7 | | -id: Quick Starts |
| 7 | +id: Quick starts |
8 | 8 | # Tab |
9 | 9 | source: about |
10 | 10 | --- |
11 | 11 | # About |
12 | | -The **@patternfly/quickstarts** extension is made up of two parts: `Quick starts` and `in-app documentation` product documentation tools. |
| 12 | +The **@patternfly/quickstarts** extension is made up of two product documentation tools: **quick starts** and **in-app documentation**. |
13 | 13 |
|
14 | 14 | ## Full live demo application |
15 | | -A live demo of **quick starts and in-app Documentation** can be found [here](https://quickstarts.netlify.app/), or view the [demo code](https://github.com/patternfly/patternfly-quickstarts/tree/main/packages/dev). |
16 | | - |
17 | | -A few key concepts are outlined below. |
| 15 | +To learn more about quick starts and in-app documentation, you may [view examples in a live demo](https://quickstarts.netlify.app/), explore the [demo code](https://github.com/patternfly/patternfly-quickstarts/tree/main/packages/dev), or continue reading below. |
18 | 16 |
|
19 | 17 | ## Quick starts |
20 | | -A `Quick start` is a set of step-by-step instructions and tasks presented in a side panel embedded in a product’s UI. Quick starts can help users get started with a product, and they often guide installation and setup. |
| 18 | +A quick start is a set of step-by-step instructions and tasks presented in a side panel embedded within a product’s UI. Quick starts can help users get started with a product by providing installation and setup guidance. |
21 | 19 |
|
22 | | -Each task in a quick start has multiple steps, and each quick start has multiple tasks. The outcome of the quick start includes the artifacts or state needed to successfully use the product, specific features, or add-ons. |
| 20 | +A quick start has multiple tasks, each with multiple steps. On completion, a quick start gives users the artifacts or state needed to successfully use a product, specific features, or add-ons. |
23 | 21 |
|
24 | 22 | <img src="./img/side-panel.png" alt="Side panel elements" width="449"/> |
25 | 23 |
|
26 | | -For more detailed design guidelines and visuals see [here.](/extensions/quick-starts/design-guidelines#quickstarts) |
| 24 | +For more quick start details and visuals, [view the design guidelines.](/extensions/quick-starts/design-guidelines) |
27 | 25 |
|
28 | 26 | ### Quick start format |
29 | 27 |
|
30 | 28 | #### For developers |
31 | | -A detailed breakdown of the Quick start format in code can be seen [here](https://github.com/patternfly/patternfly-quickstarts/blob/main/packages/module/src/utils/quick-start-types.ts). |
| 29 | +To learn more about quick starts: |
32 | 30 |
|
33 | | -Quickly preview a [basic example](/extensions/quick-starts/Basic-Quick-Starts), and remember there is a [live demo](https://quickstarts.netlify.app/) with [full demo code](https://github.com/patternfly/patternfly-quickstarts/tree/main/packages/dev). |
| 31 | +- [View a breakdown of the quick start code format](https://github.com/patternfly/patternfly-quickstarts/blob/main/packages/module/src/utils/quick-start-types.ts). |
| 32 | +- [View a basic example](/extensions/quick-starts/Basic-Quick-Starts). |
| 33 | +- [View the live demo](https://quickstarts.netlify.app/) and [view the live demo code](https://github.com/patternfly/patternfly-quickstarts/tree/main/packages/dev). |
34 | 34 |
|
35 | 35 | #### For content authors |
36 | | -Quick starts can be written in `yaml` with markdown support, `asciidoc`, or just `json`. For examples of each of these formats see [here](https://github.com/patternfly/patternfly-quickstarts/tree/main/packages/dev/src/quickstarts-data) |
| 36 | +Quick starts can be written in `yaml` with markdown support, `asciidoc`, or `json`. To learn more about each of these formats, [view example files](https://github.com/patternfly/patternfly-quickstarts/tree/main/packages/dev/src/quickstarts-data). |
37 | 37 |
|
38 | 38 | ### Opening and closing the side panel |
39 | 39 |
|
40 | 40 | #### Custom handler |
41 | | -Open the side panel by calling the `setActiveQuickStart` or `setActiveQuickstartID` methods. These methods are provided by the `QuickStartContext` and can be accessed in your React components: |
| 41 | +To open the side panel of a quick start, call the `setActiveQuickStart` or `setActiveQuickstartID` methods. These methods are provided by `QuickStartContext` and can be accessed in your React components: |
42 | 42 | ```typescript |
43 | 43 | const { setActiveQuickStart } = React.useContext<QuickStartContextValues>( |
44 | 44 | QuickStartContext, |
45 | 45 | ); |
46 | 46 | ``` |
47 | 47 |
|
48 | 48 | #### Quick start catalog |
49 | | -By providing a set of quick starts to the `QuickStartContainer`, a full-page catalog view will be generated. Clicking on a catalog card will open its respective `quick start` in the side panel. |
| 49 | +To generate a full-page catalog view, add a set of quick starts to a `QuickStartContainer`. Clicking on a catalog card will open its respective quick start in a side panel. |
50 | 50 |
|
51 | 51 | <img src="./img/catalog.png" alt="Quick start catalog" width="1680"/> |
52 | 52 |
|
53 | 53 | ## In-app documentation |
54 | | -In-app documentation is used to provide definitions for a set of topics relevant to your product. A single unit of in-app documentation can be called a `HelpTopic`, which is also the name used in code. `HelpTopic`'s essential sections are a **content** section that contains a definition of the term or topic, and an optional list of **links** to provide the user with other relevant information. |
| 54 | +In-app documentation defines topics that are relevant to a product. A `HelpTopic` is a single unit of in-app documentation that contains a **content** section, which defines the term or topic, and an optional list of **links** to provide the user with other relevant information. |
55 | 55 |
|
56 | | -`HelpTopics` are displayed in a side panel just like `quick starts`: |
| 56 | +`HelpTopics` are displayed in a side panel just like quick starts: |
57 | 57 |
|
58 | 58 | <img src="./img/help-topic.png" alt="quick start catalog" width="449"/> |
59 | 59 |
|
60 | | -### Help Topic format |
| 60 | +### HelpTopic format |
61 | 61 |
|
62 | 62 | #### For developers |
63 | | -A detailed breakdown of the `HelpTopic` format in code can be seen [here](https://github.com/patternfly/patternfly-quickstarts/blob/main/packages/module/src/utils/help-topic-types.ts). |
| 63 | +To learn more about `HelpTopic`s: |
64 | 64 |
|
65 | | -Quickly preview a [basic example](/extensions/quick-starts/In-App-Documentation), and remember there is a [live demo](https://quickstarts.netlify.app/in-context-help) with [full demo code](https://github.com/patternfly/patternfly-quickstarts/tree/main/packages/dev). |
| 65 | +- [View a breakdown of the HelpTopic code format](https://github.com/patternfly/patternfly-quickstarts/blob/main/packages/module/src/utils/help-topic-types.ts). |
| 66 | +- [View a basic example](/extensions/quick-starts/In-App-Documentation). |
| 67 | +- [View the live demo](https://quickstarts.netlify.app/in-context-help) and [view the live demo code](https://github.com/patternfly/patternfly-quickstarts/tree/main/packages/dev). |
66 | 68 |
|
67 | 69 | #### For content authors |
68 | | -HelpTopics are written in `yaml` with markdown support. An example can be seen [here](https://github.com/patternfly/patternfly-quickstarts/blob/main/packages/dev/src/quickstarts-data/yaml/in-context-help/example-topics.yaml) |
| 70 | +A `HelpTopic` is written in `yaml` with markdown support. [View an example yaml file](https://github.com/patternfly/patternfly-quickstarts/blob/main/packages/dev/src/quickstarts-data/yaml/in-app-documentation/example-topics.yaml). |
69 | 71 |
|
70 | 72 | ### Opening and closing the side panel |
71 | | -Open the side panel by calling `setActiveHelpTopicByName` (available from `HelpTopicContext`) with a `HelpTopic`'s name value. |
| 73 | +To open a side panel, call the `setActiveHelpTopicByName` method(available from `HelpTopicContext`) and include the name of a `HelpTopic`. |
72 | 74 |
|
73 | 75 | ```typescript |
74 | 76 | const { setActiveHelpTopicByName } = React.useContext<HelpTopicContextValues>(HelpTopicContext); |
75 | 77 | ``` |
76 | 78 |
|
77 | | -Close it by calling `setActiveHelpTopicByName` with an empty string. There is no prebuilt `HelpTopic` catalog. simply attach a handler with `setActiveHelpTopicByName` to the appropriate DOM element. See the [basic example](/extensions/quick-starts/In-App-Documentation) or [live demo code](https://github.com/patternfly/patternfly-quickstarts/tree/main/packages/dev) for more details. |
| 79 | +To close a side panel, call the `setActiveHelpTopicByName` method and pass in an empty string. |
| 80 | + |
| 81 | +There is no prebuilt `HelpTopic` catalog: to build one, attach a handler to the appropriate DOM element using the `setActiveHelpTopicByName` method. For more details, see the [basic example](/extensions/quick-starts/In-App-Documentation) or the [live demo code](https://github.com/patternfly/patternfly-quickstarts/tree/main/packages/dev). |
| 82 | + |
| 83 | + |
0 commit comments