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

Add page titles #105

Merged
merged 1 commit into from
May 13, 2017
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _includes/header.html
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@
</label>

<div class="trigger">
<a class="page-link" href="{{ "/documentation.html" | relative_url }}">Docs</a>
<a class="page-link" href="{{ "/documentation.html" | relative_url }}">Specification</a>
<a class="page-link" href="{{ "/examples.html" | relative_url }}">Examples</a>
<a class="page-link" href="{{ "/implementations.html" | relative_url }}">Software</a>
{% for path in page_paths %}
Expand Down
4 changes: 1 addition & 3 deletions documentation.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,8 @@
---
layout: page
title: Specification
---

Specification
-------------

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:

|--------------------------------------------------------------|-------------------------------------------------|
Expand Down
4 changes: 1 addition & 3 deletions example1.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,8 @@
---
layout: page
title: Building a product schema
---

Example data
------------

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*.

### Example JSON data for a product API
Expand Down
4 changes: 1 addition & 3 deletions example2.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,8 @@
---
layout: page
title: Building a mount point schema
---

Purpose
-------

This example shows a possible JSON representation of a hypothetical machine's mount points as represented in an `/etc/fstab` file.

An entry in the fstab file can have many different forms. Here is a possible representation of a full fstab:
Expand Down
4 changes: 1 addition & 3 deletions examples.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,8 @@
---
layout: page
title: Examples
---

Basic example
-------------

Here is a basic example of a JSON Schema:

```json
Expand Down