@@ -7,8 +7,8 @@ comments, issues and chat.
7
7
8
8
.. glossary ::
9
9
10
- content repository
11
- content repositories
10
+ content repository
11
+ content repositories
12
12
Location containing material to be included as a subset of the completed
13
13
site. Often, the material within will be written in a friendlier
14
14
human-editable markup format such as reStructuredText or Markdown.
@@ -31,8 +31,8 @@ comments, issues and chat.
31
31
* Plain-text documents that associate subsets of :term: `presented URLs `
32
32
with specific layouts.
33
33
34
- content ID
35
- content IDs
34
+ content ID
35
+ content IDs
36
36
Unique identifier assigned to a single page of content generated from a
37
37
:term: `content repository `. It's important to note that a content ID is
38
38
assigned to each *output * page, not each source document. Depending on the
@@ -58,26 +58,26 @@ comments, issues and chat.
58
58
``https://github.com/rackerlabs/developer-blog/_posts/mongodb-3.0-getting-started.md ``:
59
59
``https://github.com/rackerlabs/developer-blog/blog/mongodb-3.0-getting-started ``.
60
60
61
- revision ID
62
- revision IDs
61
+ metadata envelope
62
+ metadata envelopes
63
+ JSON document that contains a single page's worth of content as a rendered
64
+ HTML fragment, along with any additional information necessary for the
65
+ presentation of that page. See :ref: `the schema section <envelope-schema >`
66
+ for a description of the expected structure.
67
+
68
+ revision ID
69
+ revision IDs
63
70
Identifier used to isolate different staging environments from one another.
64
71
65
- presented URL
66
- presented URLs
72
+ presented URL
73
+ presented URLs
67
74
URL of a page within the final presented content of a deconst site. This
68
75
should be the full URL, including the scheme and domain.
69
76
70
77
Example:
71
78
``https://developer.rackspace.com/sdks/cloud-servers/getting-started/ ``.
72
79
73
- template
80
+ template
74
81
Common markup that surrounds each presented page with navigation, brand
75
82
identity, copyright information and anything else that's shared among some
76
83
subset of each site.
77
-
78
- metadata envelope
79
- metadata envelopes
80
- JSON document that contains a single page's worth of content as a rendered
81
- HTML fragment, along with any additional information necessary for the
82
- presentation of that page. See :ref: `the schema section <envelope-schema >`
83
- for a description of the expected structure.
0 commit comments