From adcf454c011711c9c0fc35fecf7d4d466c90ba43 Mon Sep 17 00:00:00 2001 From: Alecks Gates Date: Sun, 18 Apr 2021 22:35:20 -0500 Subject: [PATCH] Add highlighting hint to code blocks --- README.md | 22 +++++++++---------- chapters/jsonChapters.md | 8 +++---- docs/1.0.md | 2 +- location/location.md | 12 +++++----- .../recommendations/recommendations.md | 12 +++++----- transcripts/transcripts.md | 4 ++-- value/value.md | 10 ++++----- 7 files changed, 35 insertions(+), 35 deletions(-) diff --git a/README.md b/README.md index 420ed14..a2704c0 100644 --- a/README.md +++ b/README.md @@ -152,7 +152,7 @@ The following tags should be considered purely as work in progress proposals. T -``` +```xml Coming April 1st, 2021 ``` Example with Season Linkage: -``` +```xml Season 4: Race for the Whitehouse (combined with) @@ -200,7 +200,7 @@ Example with Season Linkage: -``` +```xml @@ -220,7 +220,7 @@ should be a reference to a slug defined in the [license slugs](licenseslugs.txt) - `url` (optional) This is a url that points to the full license details for this license. Example: -``` +```xml cc-by-4.0 ``` @@ -232,7 +232,7 @@ Example: -``` +```xml ``` Example: -``` +```xml Some other cool podcasts ``` @@ -271,7 +271,7 @@ Example: -``` +```xml @@ -326,7 +326,7 @@ Example: ``` Example: -``` +```xml diff --git a/chapters/jsonChapters.md b/chapters/jsonChapters.md index 25ddd09..d4903a9 100644 --- a/chapters/jsonChapters.md +++ b/chapters/jsonChapters.md @@ -34,7 +34,7 @@ The chapters object is a simple JSON object with only 2 required properties: The "chapter" object takes this basic form: -``` +```json { "startTime": 94, "title": "Donation Segment" @@ -62,7 +62,7 @@ There is only one required attribute: The "location" object takes this basic form: -``` +```json { "name": "Eiffel Tower, Paris", "geo": "geo:48.858093,2.294694" @@ -87,7 +87,7 @@ There are two required attributes: Here is what a very basic chapters file may look like: -``` +```json { "version": "1.1.0", "chapters": @@ -144,7 +144,7 @@ In this more robust example, we can bring in more meta-data about the podcast ep context for something like an embedded HTML5 player on a website. Also there is an example of a "silent" chapter that has no presence in the visible chapter list, but allows for different artwork to be shown: -``` +```json { "version": "1.1.0", "author": "John Doe", diff --git a/docs/1.0.md b/docs/1.0.md index e9b18ce..656d7b4 100644 --- a/docs/1.0.md +++ b/docs/1.0.md @@ -4,7 +4,7 @@ A wholistic RSS namespace for podcasting that is meant to synthesize the fragmen The namespace for this extension is `https://podcastindex.org/namespace/1.0`. Clients which recognize this namespace must also recognize `https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/1.0.md` as identical. The suggested tag prefix for use in XML is `podcast`, but clients should support alternate prefixes for this namespace. If your application generates RSS feeds and you implement one or more elements below, you will need to link this DTD in your XML: -``` +```xml ``` diff --git a/location/location.md b/location/location.md index 764084f..d44ae5e 100644 --- a/location/location.md +++ b/location/location.md @@ -35,7 +35,7 @@ This, therefore, means that the `` tag is complex and has a nu ### Structure -``` +```xml Hogwarts" +```xml +Hogwarts ``` For a podcast from Tesla upon landing on Mars: -``` +```xml Tesla Base 3 ``` diff --git a/proposal-docs/recommendations/recommendations.md b/proposal-docs/recommendations/recommendations.md index 978261d..a9bbdb9 100644 --- a/proposal-docs/recommendations/recommendations.md +++ b/proposal-docs/recommendations/recommendations.md @@ -55,10 +55,10 @@ The recommendations object is a simple JSON object with 2 required properties: The "recommendation" object takes this basic form: -``` +```json { "type": "page", - "title": "History of podcasting", + "title": "History of podcasting", "image": "https://upload.wikimedia.org/wikipedia/commons/thumb/e/e7/Podcasts_%28iOS%29.svg/440px-Podcasts_%28iOS%29.svg.png", "url": "https://en.wikipedia.org/wiki/History_of_podcasting" } @@ -85,14 +85,14 @@ There are 4 required attributes: Here is what a very basic recommendations file may look like: -``` +```json { "version": "1.0", "recommendations": [ { "type": "page", - "title": "History of podcasting", + "title": "History of podcasting", "image": "https://upload.wikimedia.org/wikipedia/commons/thumb/e/e7/Podcasts_%28iOS%29.svg/440px-Podcasts_%28iOS%29.svg.png", "url": "https://en.wikipedia.org/wiki/History_of_podcasting" }, @@ -127,7 +127,7 @@ Here is what a very basic recommendations file may look like: ## More complex example -``` +```json { "version": "1.0", "title": "Podnews podcasting news", @@ -138,7 +138,7 @@ Here is what a very basic recommendations file may look like: "displayStartTime": 0.0, "displayDuration": 120.0, "type": "page", - "title": "History of podcasting", + "title": "History of podcasting", "image": "https://upload.wikimedia.org/wikipedia/commons/thumb/e/e7/Podcasts_%28iOS%29.svg/440px-Podcasts_%28iOS%29.svg.png", "url": "https://en.wikipedia.org/wiki/History_of_podcasting", "relevance": 0.8 diff --git a/transcripts/transcripts.md b/transcripts/transcripts.md index d05be77..c66a8c6 100644 --- a/transcripts/transcripts.md +++ b/transcripts/transcripts.md @@ -17,7 +17,7 @@ designed to serve as an accessibility aid and provide searchable episode content - `

`: Content of monologue #### Snippet: -``` +```html Kevin:

We have an update planned where we would like to give the ability to upload an artwork file for these videos

@@ -44,7 +44,7 @@ The JSON representation is a flexible format that accomodates various degrees of - ``: Dialogue content #### Snippet: -``` +```json { "version": "1.0.0", "segments": [ diff --git a/value/value.md b/value/value.md index 537b546..ac0229e 100644 --- a/value/value.md +++ b/value/value.md @@ -65,7 +65,7 @@ Currently, there can be only a single copy of this element at each level.
#### Structure: -``` +```xml ` level, it is intended to override the channel level tag f #### Example: -``` +```xml