e5c6dca9c5
* Add new articles * Rename article * Add secrets content * Remove permissions statements * Fix image name * Fix article name * Mention GPG verification for Codespaces in "About commit signature verification" * Add GPG verification content * Add access and security procedure * Add 💅 * Rename articles * Rename the other article * Rename again * Okay, rename this one again, too * Update link * Start access and security content * Add 💅 * Mention new functionalities in "Personalizing..." * Mention new features in "About Codespaces" * Add 💅 * Fix typos * Add audit log events * Fix so many links * Add 💅 * Add permissions * Spell access correctly, for once * Add 💅 * FIX THESE LINKS I SWEAR * Addd missing ) * Start adding procedure * update with procedural * Update content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> * Update content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> * Apply suggestions from code review Committing all reviews ✨ Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: Meg Bird <megbird@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 %}.