2. Page Source Options - csandker/Playbooks GitHub Wiki

Currently you have the following options to create a new page:

• HTTP
• File Upload
• From Server
• Text Input

HTTP

Fetch a Markdown Page from a different place via HTTP. Note the remote source should return the page as Markdown, not HTML. Raw Github pages are a good place to include as HTTP resource, e.g. https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1208/T1208.md.

Pages added via HTTP can be updated from source. If the server detects a mismatch between your local and the origin's remote version (aka. you changed the page or it got updated on the remote side), you will see a notification and can fetch the updated version from the remote source.

Example:

File Upload

Pretty straightforward. Upload a Markdown file from your local system. Note this source type can not be updated (as the server can't access your local files).

From Server

This is likely the best option for you if you already have an existing knowledgebase that you want to include. Within the admin area you can include server side directory for read access, all directories added and enabled within the admin area are displayed to application users and the directories are crawled for markdown or text files. Application users can add any markdown or text files from these directories to their playbooks.

As with the HTTP source, these type pages can be updates (as the server can access them). So once an updated version is detected the application offers the users to update their pages. If you have an existing knowledge base this is the best option, as it enables all PlayBooks users to use uptodate versions and keep in sync with the uplink.

Example:

Text Input

This can be used to write your own pages from scratch in markdown. By typing your text the application will convert the result to HTML and display it to you in a preview.

Example: