* Add documentation for 2FA with GitHub Mobile * Fix unordered list for GitHub Mobile features * Prefer "logging in to" over "logging into" Co-authored-by: Brian Lovin <brianlovin@github.com> * Indicate that GitHub Mobile is secondary * Further indicate that GitHub Mobile is most like security keys * Prefer "sign in" over "log in" Co-authored-by: Zachary Sierakowski <zacharysierakowski@github.com> * Fix unintended edit Co-authored-by: Zachary Sierakowski <zacharysierakowski@github.com> * Prefer active voice Co-authored-by: hubwriter <hubwriter@github.com> * Add missing punctuation Co-authored-by: hubwriter <hubwriter@github.com> * Fix phrasing of mobile 2FA CTA Co-authored-by: hubwriter <hubwriter@github.com> * Apply suggestions from code review Co-authored-by: hubwriter <hubwriter@github.com> * Prefer active voice Co-authored-by: hubwriter <hubwriter@github.com> * Update "secondary" phrasing for mobile 2FA Co-authored-by: hubwriter <hubwriter@github.com> * Add info about skipping security key Co-authored-by: Joshua Walker <3141202+joshuawalker@users.noreply.github.com> Co-authored-by: Brian Lovin <brianlovin@github.com> Co-authored-by: Zachary Sierakowski <zacharysierakowski@github.com> Co-authored-by: hubwriter <hubwriter@github.com> Co-authored-by: Joshua Walker <3141202+joshuawalker@users.noreply.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 %}.
Versioning
Reusables can include Liquid conditionals to conditionally render content depending on the current version being viewed. See contributing/liquid-helpers.md.