0f25789de9
* Placeholder edit * Revamp description of tier benefits * Add steps around suggested tiers * cannot is easier to read * spaces are fun * Remove reusable * Add a tip * Add step for editing draft tier * Revise * Apply Lucas' input Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * Consolidate step * Change tip to note * Add this line to first paragraph * Apply Product/engineering input Co-authored-by: evelyn masso <outofambit@github.com> * Last engineering/product input * Apply another round of input Co-authored-by: Felicity Chapman <felicitymay@github.com> Co-authored-by: evelyn masso <outofambit@github.com> * Update navigation reusable Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> Co-authored-by: evelyn masso <outofambit@github.com> Co-authored-by: Felicity Chapman <felicitymay@github.com>
Reusables
Reusables are long strings of reusable text.
Reusables are longer strings like paragraphs or procedural lists that can be referenced in multiple content files. Using Markdown (instead of YAML) makes it possible for our localization pipeline to split the strings into smaller translatable segments, leading to fewer translation errors and less churn when the source English content changes.
Each reusable lives in its own Markdown file.
The path and filename of each Markdown file determines what its path will be in the data object.
For example, a file named /data/reusables/foo/bar.md will be accessible as {% data reusables.foo.bar %} in pages.
Reusable files are divided generally into directories by task. For example, if you're creating a reusable string for articles about GitHub notifications, you'd add it in the directory data/reusables/notifications/ in a file named data/reusables/notifications/your-reusable-name.md. The content reference you'd add to the source would look like {% data reusables.notifications.your-reusable-name %}.