1
0
mirror of synced 2025-12-31 06:02:42 -05:00
Files
docs/data/reusables
jmarlena 45398e709c Password authentication and OAuth Authorizations API deprecation (#16375)
* Version password examples for GHES only

* Remove unnecessary note

* Versioned deprecation reusable for GHES only?

* Update troubleshooting article

* Version OAuthorizations REST API page for enterprise-only

* Remove deprecations reusable

* Add tentative note

* Rework two-factor authentication sections

* Fix double redirect reference

* versioning tweak

* Versioning tweaks

* adding back the endifs

* random link reformatting

* OAuth Authorization API versioned for 2.22

* /

* Fix internal docs links

* remove static redirect for dotcom

* Try deleting redirect

* Apply @martin389's suggested changes

Co-authored-by: Martin Lopes <54248166+martin389@users.noreply.github.com>

* Remove best practice assumptions

* Apply suggestions from code review

Co-authored-by: Martin Lopes <54248166+martin389@users.noreply.github.com>

* Add note

* restore redirects in content file and remove free-pro-team expected path from test fixture

* change note position

* handle path that was available on dotcom in developer site but is now GHES only

Co-authored-by: Martin Lopes <54248166+martin389@users.noreply.github.com>
Co-authored-by: Sarah Schneider <sarahs@github.com>
2020-11-13 11:01:17 -08:00
..
2020-11-02 15:12:44 -06:00
2020-11-02 15:12:44 -06:00
2020-11-02 15:12:44 -06:00
2020-11-05 07:17:59 -06:00
2020-11-02 15:12:44 -06:00
2020-11-02 15:12:44 -06:00
2020-11-02 15:12:44 -06:00
2020-11-02 15:12:44 -06:00
2020-09-27 14:10:11 +02:00
2020-11-02 15:12:44 -06:00
2020-11-02 15:12:44 -06:00
2020-11-02 15:12:44 -06:00
2020-11-02 15:12:44 -06:00
2020-11-02 15:12:44 -06:00
2020-11-02 15:12:44 -06:00
2020-11-05 18:22:34 -08:00
2020-09-27 14:10:11 +02:00
2020-11-02 15:12:44 -06:00
2020-11-04 14:38:39 -05:00
2020-09-27 14:10:11 +02:00

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 %}.