Skip to content
This repository was archived by the owner on Nov 2, 2023. It is now read-only.

Commit 3391184

Browse files
adamvosshandrews
authored andcommitted
Add page titles
This also renames the 'Docs' entry to 'Specification' better matching the page content.
1 parent 05da1d9 commit 3391184

File tree

5 files changed

+5
-13
lines changed

5 files changed

+5
-13
lines changed

_includes/header.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@
1919
</label>
2020

2121
<div class="trigger">
22-
<a class="page-link" href="{{ "/documentation.html" | relative_url }}">Docs</a>
22+
<a class="page-link" href="{{ "/documentation.html" | relative_url }}">Specification</a>
2323
<a class="page-link" href="{{ "/examples.html" | relative_url }}">Examples</a>
2424
<a class="page-link" href="{{ "/implementations.html" | relative_url }}">Software</a>
2525
{% for path in page_paths %}

documentation.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,8 @@
11
---
22
layout: page
3+
title: Specification
34
---
45

5-
Specification
6-
-------------
7-
86
The latest Internet-Drafts at the IETF are the draft-wright-json-schema\*-01 documents, which correspond to the draft-06 meta-schemas. These were published on 2017-04-15. (Due to a change in authorship the I-D numbering was reset with the previous draft). The specification is split into three parts, Core, Validation, and Hyper-Schema:
97

108
|--------------------------------------------------------------|-------------------------------------------------|

example1.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,8 @@
11
---
22
layout: page
3+
title: Building a product schema
34
---
45

5-
Example data
6-
------------
7-
86
Let's pretend we're interacting with a JSON based product catalog. This catalog has a product which has an *id*, a *name*, a *price*, and an optional set of *tags*.
97

108
### Example JSON data for a product API

example2.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,8 @@
11
---
22
layout: page
3+
title: Building a mount point schema
34
---
45

5-
Purpose
6-
-------
7-
86
This example shows a possible JSON representation of a hypothetical machine's mount points as represented in an `/etc/fstab` file.
97

108
An entry in the fstab file can have many different forms. Here is a possible representation of a full fstab:

examples.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,8 @@
11
---
22
layout: page
3+
title: Examples
34
---
45

5-
Basic example
6-
-------------
7-
86
Here is a basic example of a JSON Schema:
97

108
```json

0 commit comments

Comments
 (0)