cb1b8ac095
* Update billing reusable * Update articles using billing-settings.png * update codespaces-policy-sidebar.png articles * Update reusable using codespaces-sidebar-tab.png * Update codespaces-option-secrets-org.png * Add octicon for secrets menu tab * Make alt text more accessible * Update GitHub Apps menu item references * Update article using org-oauth-applications-ghe.png * organizations/org-settings-block-users.png * Replace org-settings-installed-github-apps.png with octicon * Update org-settings-interaction-limits.png * Update codespaces-option-secrets.png * Replace org-settings-member-priveleges.png with octicon * Delete org-settings-member-privileges.png * Replace org-settings-moderation-settings.png with octicon * Replace org-settings-repository-roles.png with octicon * Replace org-settings-security-and-analysis.png with octicon * Replace repo-defaults-tab.png with octicon * Delete unused image repo-labels-tab.png * Replace scheduled-reminders-org.png with octicon * replace verified-domains-button.png with octicon * Add step to navigate to Projects settings page * Remove codespaces secrets images and use octicons * Replace codespaces-policy-sidebar.png with octicon * Remove unused communities image * Add versioning and update icon for github apps * Add versioning for disabling project boards * Add versioning for integrating jira * Version reusables * Remove unnecessary moderation image * Apply suggestions from code review
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 %}.
Versioning
Reusables can include Liquid conditionals to conditionally render content depending on the current version being viewed. See contributing/liquid-helpers.md.