From d12ed875c8bcfe9f9986bcf21db08d469371b7d5 Mon Sep 17 00:00:00 2001 From: enterfive Date: Fri, 30 Nov 2018 13:51:44 +0100 Subject: [PATCH 01/96] Set theme jekyll-theme-cayman --- _config.yml | 1 + 1 file changed, 1 insertion(+) create mode 100644 _config.yml diff --git a/_config.yml b/_config.yml new file mode 100644 index 0000000..c419263 --- /dev/null +++ b/_config.yml @@ -0,0 +1 @@ +theme: jekyll-theme-cayman \ No newline at end of file From 59cf4635d2e1de5a9bc3c402d9dda17518e8473f Mon Sep 17 00:00:00 2001 From: securetorobert Date: Fri, 30 Nov 2018 14:39:15 +0100 Subject: [PATCH 02/96] getting started --- Clients.md | 261 ++++++++++++++++++++++++++++++++++++++++++++++++ Dashboard.md | 261 ++++++++++++++++++++++++++++++++++++++++++++++++ Email.md | 261 ++++++++++++++++++++++++++++++++++++++++++++++++ Profanity.md | 261 ++++++++++++++++++++++++++++++++++++++++++++++++ Readme.md | 73 +++++++++----- Readme.md.orig | 266 +++++++++++++++++++++++++++++++++++++++++++++++++ clients.html | 52 ++++++++++ dashboard.html | 52 ++++++++++ email.html | 52 ++++++++++ index.html | 16 +-- profanity.html | 52 ++++++++++ 11 files changed, 1576 insertions(+), 31 deletions(-) create mode 100644 Clients.md create mode 100644 Dashboard.md create mode 100644 Email.md create mode 100644 Profanity.md create mode 100644 Readme.md.orig create mode 100644 clients.html create mode 100644 dashboard.html create mode 100644 email.html create mode 100644 profanity.html diff --git a/Clients.md b/Clients.md new file mode 100644 index 0000000..2dd73b4 --- /dev/null +++ b/Clients.md @@ -0,0 +1,261 @@ +Versus API Endpoints +======= + +This documentation lists the API endpoints required for engineers on the Versus team to interface with Versus Backend. The API endpoints are generally grouped into the following. + + * Clients + * Dashboard + * Email Templates + * Profanity Filter + +*Current version: [v0.1.0][dist]* + + +Getting started +--------------- + +Create a file based on the template, which has a bare DOM, link to the +scripts, and a link to a theme. It will look something like this (not exact). +For GitHub projects, simply place this file in your [GitHub pages] branch and +you're all good to go. + +*In short: just download this file and upload it somewhere.* + +The main JS and CSS files are also available in [npm] and [bower]. + +[Default theme template >][template] + +[Blank template >][blank] + +[bower]: http://bower.io/search/?q=flatdoc +[npm]: https://www.npmjs.org/package/flatdoc + +### Via GitHub + +To fetch a Github Repository's readme file, use the `Flatdoc.github` fetcher. +This will fetch the Readme file of the repository's default branch. + +``` javascript +Flatdoc.run({ + fetcher: Flatdoc.github('USER/REPO') +}); +``` + +You may also fetch another file other than the Readme file, just specify it as +the 2nd parameter. + +``` javascript +Flatdoc.run({ + fetcher: Flatdoc.github('USER/REPO', 'Changelog.md') +}); +``` + +After you've done this, you probably want to deploy it via [GitHub Pages]. + +[GitHub Pages guide >][GitHub Pages] + +### Via a file + +You may also fetch a file. In this example, this fetches the file `Readme.md` in +the same folder as the HTML file. + +``` javascript +Flatdoc.run({ + fetcher: Flatdoc.file('Readme.md') +}); +``` + +You may actually supply any URL here. It will be fetched via AJAX. This is +useful for local testing. + +``` javascript +Flatdoc.run({ + fetcher: Flatdoc.file('http://yoursite.com/Readme.md') +}); +``` + +How it works +------------ + +Flatdoc is a hosted `.js` file (along with a theme and its assets) that you can +add into any page hosted anywhere. + +#### All client-side + +There are no build scripts or 3rd-party services involved. Everything is done in +the browser. Worried about performance? Oh, It's pretty fast. + +Flatdoc utilizes the [GitHub API] to fetch your project's Readme files. You may +also configure it to fetch any arbitrary URL via AJAX. + +#### Lightning-fast parsing + +Next, it uses [marked], an extremely fast Markdown parser that has support for +GitHub flavored Markdown. + +Flatdoc then simply renders *menu* and *content* DOM elements to your HTML +document. Flatdoc also comes with a default theme to style your page for you, or +you may opt to create your own styles. + +Markdown extras +--------------- + +Flatdoc offers a few harmless, unobtrusive extras that come in handy in building +documentation sites. + +#### Code highlighting + +You can use Markdown code fences to make syntax-highlighted text. Simply +surround your text with three backticks. This works in GitHub as well. +See [GitHub Syntax Highlighting][fences] for more info. + + ``` html + Hola, mundo + ``` + +#### Blockquotes + +Blockquotes show up as side figures. This is useful for providing side +information or non-code examples. + +> Blockquotes are blocks that begin with `>`. + +#### Smart quotes + +Single quotes, double quotes, and double-hyphens are automatically replaced to +their typographically-accurate equivalent. This, of course, does not apply to +`` and `
` blocks to leave code alone.
+
+> "From a certain point onward there is no longer any turning back. That is the
+> point that must be reached."  
+> --Franz Kafka
+
+#### Buttons
+
+If your link text has a `>` at the end (for instance: `Continue >`), they show
+up as buttons.
+
+> [View in GitHub >][project]
+
+Customizing
+===========
+
+Basic
+-----
+
+### Theme options
+
+For the default theme (*theme-white*), You can set theme options by adding
+classes to the `` element. The available options are:
+
+#### big-h3
+Makes 3rd-level headings bigger.
+
+``` html
+
+```
+
+#### no-literate
+Disables "literate" mode, where code appears on the right and content text
+appear on the left.
+
+``` html
+
+```
+
+#### large-brief
+Makes the opening paragraph large.
+
+``` html
+
+```
+
+### Adding more markup
+
+You have full control over the HTML file, just add markup wherever you see fit.
+As long as you leave `role='flatdoc-content'` and `role='flatdoc-menu'` empty as
+they are, you'll be fine.
+
+Here are some ideas to get you started.
+
+ * Add a CSS file to make your own CSS adjustments.
+ * Add a 'Tweet' button on top.
+ * Add Google Analytics.
+ * Use CSS to style the IDs in menus (`#acknowledgements + p`).
+
+### JavaScript hooks
+
+Flatdoc emits the events `flatdoc:loading` and `flatdoc:ready` to help you make
+custom behavior when the document loads.
+
+``` js
+$(document).on('flatdoc:ready', function() {
+  // I don't like this section to appear
+  $("#acknowledgements").remove();
+});
+```
+
+Full customization
+------------------
+
+You don't have to be restricted to the given theme. Flatdoc is just really one
+`.js` file that expects 2 HTML elements (for *menu* and *content*). Start with
+the blank template and customize as you see fit.
+
+[Get blank template >][template]
+
+Misc
+====
+
+Inspirations
+------------
+
+The following projects have inspired Flatdoc.
+
+ * [Backbone.js] - Jeremy's projects have always adopted this "one page
+ documentation" approach which I really love.
+
+ * [Docco] - Jeremy's Docco introduced me to the world of literate programming,
+ and side-by-side documentation in general.
+
+ * [Stripe] - Flatdoc took inspiration on the look of their API documentation.
+
+ * [DocumentUp] - This service has the same idea but does a hosted readme 
+ parsing approach.
+
+Attributions
+------------
+
+[Photo](http://www.flickr.com/photos/doug88888/2953428679/) taken from Flickr,
+licensed under Creative Commons.
+
+Acknowledgements
+----------------
+
+© 2013, 2014, Rico Sta. Cruz. Released under the [MIT 
+License](http://www.opensource.org/licenses/mit-license.php).
+
+**Flatdoc** is authored and maintained by [Rico Sta. Cruz][rsc] with help from its 
+[contributors][c].
+
+ * [My website](http://ricostacruz.com) (ricostacruz.com)
+ * [Github](http://github.com/rstacruz) (@rstacruz)
+ * [Twitter](http://twitter.com/rstacruz) (@rstacruz)
+
+[rsc]: http://ricostacruz.com
+[c]:   http://github.com/rstacruz/flatdoc/contributors
+
+[GitHub API]: http://github.com/api
+[marked]: https://github.com/chjj/marked
+[Backbone.js]: http://backbonejs.org
+[dox]: https://github.com/visionmedia/dox
+[Stripe]: https://stripe.com/docs/api
+[Docco]: http://jashkenas.github.com/docco
+[GitHub pages]: https://pages.github.com
+[fences]:https://help.github.com/articles/github-flavored-markdown#syntax-highlighting
+[DocumentUp]: http://documentup.com
+
+[project]: https://github.com/rstacruz/flatdoc
+[template]: https://github.com/rstacruz/flatdoc/raw/gh-pages/templates/template.html
+[blank]: https://github.com/rstacruz/flatdoc/raw/gh-pages/templates/blank.html
+[dist]: https://github.com/rstacruz/flatdoc/tree/gh-pages/v/0.9.0
diff --git a/Dashboard.md b/Dashboard.md
new file mode 100644
index 0000000..2dd73b4
--- /dev/null
+++ b/Dashboard.md
@@ -0,0 +1,261 @@
+Versus API Endpoints
+=======
+
+This documentation lists the API endpoints required for engineers on the Versus team to interface with Versus Backend. The API endpoints are generally grouped into the following.
+
+ * Clients
+ * Dashboard
+ * Email Templates
+ * Profanity Filter
+
+*Current version: [v0.1.0][dist]*
+
+
+Getting started
+---------------
+
+Create a file based on the template, which has a bare DOM, link to the
+scripts, and a link to a theme. It will look something like this (not exact).
+For GitHub projects, simply place this file in your [GitHub pages] branch and
+you're all good to go.
+
+*In short: just download this file and upload it somewhere.*
+
+The main JS and CSS files are also available in [npm] and [bower].
+
+[Default theme template >][template]
+
+[Blank template >][blank]
+
+[bower]: http://bower.io/search/?q=flatdoc
+[npm]: https://www.npmjs.org/package/flatdoc
+
+### Via GitHub
+
+To fetch a Github Repository's readme file, use the `Flatdoc.github` fetcher.
+This will fetch the Readme file of the repository's default branch.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.github('USER/REPO')
+});
+```
+
+You may also fetch another file other than the Readme file, just specify it as
+the 2nd parameter.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.github('USER/REPO', 'Changelog.md')
+});
+```
+
+After you've done this, you probably want to deploy it via [GitHub Pages].
+
+[GitHub Pages guide >][GitHub Pages]
+
+### Via a file
+
+You may also fetch a file. In this example, this fetches the file `Readme.md` in
+the same folder as the HTML file.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.file('Readme.md')
+});
+```
+
+You may actually supply any URL here. It will be fetched via AJAX. This is
+useful for local testing.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.file('http://yoursite.com/Readme.md')
+});
+```
+
+How it works
+------------
+
+Flatdoc is a hosted `.js` file (along with a theme and its assets) that you can
+add into any page hosted anywhere.
+
+#### All client-side
+
+There are no build scripts or 3rd-party services involved. Everything is done in
+the browser. Worried about performance? Oh, It's pretty fast.
+
+Flatdoc utilizes the [GitHub API] to fetch your project's Readme files. You may
+also configure it to fetch any arbitrary URL via AJAX.
+
+#### Lightning-fast parsing
+
+Next, it uses [marked], an extremely fast Markdown parser that has support for
+GitHub flavored Markdown.
+
+Flatdoc then simply renders *menu* and *content* DOM elements to your HTML
+document. Flatdoc also comes with a default theme to style your page for you, or
+you may opt to create your own styles.
+
+Markdown extras
+---------------
+
+Flatdoc offers a few harmless, unobtrusive extras that come in handy in building
+documentation sites.
+
+#### Code highlighting
+
+You can use Markdown code fences to make syntax-highlighted text. Simply
+surround your text with three backticks. This works in GitHub as well.
+See [GitHub Syntax Highlighting][fences] for more info.
+
+    ``` html
+    Hola, mundo
+    ```
+
+#### Blockquotes
+
+Blockquotes show up as side figures. This is useful for providing side
+information or non-code examples.
+
+> Blockquotes are blocks that begin with `>`.
+
+#### Smart quotes
+
+Single quotes, double quotes, and double-hyphens are automatically replaced to
+their typographically-accurate equivalent. This, of course, does not apply to
+`` and `
` blocks to leave code alone.
+
+> "From a certain point onward there is no longer any turning back. That is the
+> point that must be reached."  
+> --Franz Kafka
+
+#### Buttons
+
+If your link text has a `>` at the end (for instance: `Continue >`), they show
+up as buttons.
+
+> [View in GitHub >][project]
+
+Customizing
+===========
+
+Basic
+-----
+
+### Theme options
+
+For the default theme (*theme-white*), You can set theme options by adding
+classes to the `` element. The available options are:
+
+#### big-h3
+Makes 3rd-level headings bigger.
+
+``` html
+
+```
+
+#### no-literate
+Disables "literate" mode, where code appears on the right and content text
+appear on the left.
+
+``` html
+
+```
+
+#### large-brief
+Makes the opening paragraph large.
+
+``` html
+
+```
+
+### Adding more markup
+
+You have full control over the HTML file, just add markup wherever you see fit.
+As long as you leave `role='flatdoc-content'` and `role='flatdoc-menu'` empty as
+they are, you'll be fine.
+
+Here are some ideas to get you started.
+
+ * Add a CSS file to make your own CSS adjustments.
+ * Add a 'Tweet' button on top.
+ * Add Google Analytics.
+ * Use CSS to style the IDs in menus (`#acknowledgements + p`).
+
+### JavaScript hooks
+
+Flatdoc emits the events `flatdoc:loading` and `flatdoc:ready` to help you make
+custom behavior when the document loads.
+
+``` js
+$(document).on('flatdoc:ready', function() {
+  // I don't like this section to appear
+  $("#acknowledgements").remove();
+});
+```
+
+Full customization
+------------------
+
+You don't have to be restricted to the given theme. Flatdoc is just really one
+`.js` file that expects 2 HTML elements (for *menu* and *content*). Start with
+the blank template and customize as you see fit.
+
+[Get blank template >][template]
+
+Misc
+====
+
+Inspirations
+------------
+
+The following projects have inspired Flatdoc.
+
+ * [Backbone.js] - Jeremy's projects have always adopted this "one page
+ documentation" approach which I really love.
+
+ * [Docco] - Jeremy's Docco introduced me to the world of literate programming,
+ and side-by-side documentation in general.
+
+ * [Stripe] - Flatdoc took inspiration on the look of their API documentation.
+
+ * [DocumentUp] - This service has the same idea but does a hosted readme 
+ parsing approach.
+
+Attributions
+------------
+
+[Photo](http://www.flickr.com/photos/doug88888/2953428679/) taken from Flickr,
+licensed under Creative Commons.
+
+Acknowledgements
+----------------
+
+© 2013, 2014, Rico Sta. Cruz. Released under the [MIT 
+License](http://www.opensource.org/licenses/mit-license.php).
+
+**Flatdoc** is authored and maintained by [Rico Sta. Cruz][rsc] with help from its 
+[contributors][c].
+
+ * [My website](http://ricostacruz.com) (ricostacruz.com)
+ * [Github](http://github.com/rstacruz) (@rstacruz)
+ * [Twitter](http://twitter.com/rstacruz) (@rstacruz)
+
+[rsc]: http://ricostacruz.com
+[c]:   http://github.com/rstacruz/flatdoc/contributors
+
+[GitHub API]: http://github.com/api
+[marked]: https://github.com/chjj/marked
+[Backbone.js]: http://backbonejs.org
+[dox]: https://github.com/visionmedia/dox
+[Stripe]: https://stripe.com/docs/api
+[Docco]: http://jashkenas.github.com/docco
+[GitHub pages]: https://pages.github.com
+[fences]:https://help.github.com/articles/github-flavored-markdown#syntax-highlighting
+[DocumentUp]: http://documentup.com
+
+[project]: https://github.com/rstacruz/flatdoc
+[template]: https://github.com/rstacruz/flatdoc/raw/gh-pages/templates/template.html
+[blank]: https://github.com/rstacruz/flatdoc/raw/gh-pages/templates/blank.html
+[dist]: https://github.com/rstacruz/flatdoc/tree/gh-pages/v/0.9.0
diff --git a/Email.md b/Email.md
new file mode 100644
index 0000000..2dd73b4
--- /dev/null
+++ b/Email.md
@@ -0,0 +1,261 @@
+Versus API Endpoints
+=======
+
+This documentation lists the API endpoints required for engineers on the Versus team to interface with Versus Backend. The API endpoints are generally grouped into the following.
+
+ * Clients
+ * Dashboard
+ * Email Templates
+ * Profanity Filter
+
+*Current version: [v0.1.0][dist]*
+
+
+Getting started
+---------------
+
+Create a file based on the template, which has a bare DOM, link to the
+scripts, and a link to a theme. It will look something like this (not exact).
+For GitHub projects, simply place this file in your [GitHub pages] branch and
+you're all good to go.
+
+*In short: just download this file and upload it somewhere.*
+
+The main JS and CSS files are also available in [npm] and [bower].
+
+[Default theme template >][template]
+
+[Blank template >][blank]
+
+[bower]: http://bower.io/search/?q=flatdoc
+[npm]: https://www.npmjs.org/package/flatdoc
+
+### Via GitHub
+
+To fetch a Github Repository's readme file, use the `Flatdoc.github` fetcher.
+This will fetch the Readme file of the repository's default branch.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.github('USER/REPO')
+});
+```
+
+You may also fetch another file other than the Readme file, just specify it as
+the 2nd parameter.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.github('USER/REPO', 'Changelog.md')
+});
+```
+
+After you've done this, you probably want to deploy it via [GitHub Pages].
+
+[GitHub Pages guide >][GitHub Pages]
+
+### Via a file
+
+You may also fetch a file. In this example, this fetches the file `Readme.md` in
+the same folder as the HTML file.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.file('Readme.md')
+});
+```
+
+You may actually supply any URL here. It will be fetched via AJAX. This is
+useful for local testing.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.file('http://yoursite.com/Readme.md')
+});
+```
+
+How it works
+------------
+
+Flatdoc is a hosted `.js` file (along with a theme and its assets) that you can
+add into any page hosted anywhere.
+
+#### All client-side
+
+There are no build scripts or 3rd-party services involved. Everything is done in
+the browser. Worried about performance? Oh, It's pretty fast.
+
+Flatdoc utilizes the [GitHub API] to fetch your project's Readme files. You may
+also configure it to fetch any arbitrary URL via AJAX.
+
+#### Lightning-fast parsing
+
+Next, it uses [marked], an extremely fast Markdown parser that has support for
+GitHub flavored Markdown.
+
+Flatdoc then simply renders *menu* and *content* DOM elements to your HTML
+document. Flatdoc also comes with a default theme to style your page for you, or
+you may opt to create your own styles.
+
+Markdown extras
+---------------
+
+Flatdoc offers a few harmless, unobtrusive extras that come in handy in building
+documentation sites.
+
+#### Code highlighting
+
+You can use Markdown code fences to make syntax-highlighted text. Simply
+surround your text with three backticks. This works in GitHub as well.
+See [GitHub Syntax Highlighting][fences] for more info.
+
+    ``` html
+    Hola, mundo
+    ```
+
+#### Blockquotes
+
+Blockquotes show up as side figures. This is useful for providing side
+information or non-code examples.
+
+> Blockquotes are blocks that begin with `>`.
+
+#### Smart quotes
+
+Single quotes, double quotes, and double-hyphens are automatically replaced to
+their typographically-accurate equivalent. This, of course, does not apply to
+`` and `
` blocks to leave code alone.
+
+> "From a certain point onward there is no longer any turning back. That is the
+> point that must be reached."  
+> --Franz Kafka
+
+#### Buttons
+
+If your link text has a `>` at the end (for instance: `Continue >`), they show
+up as buttons.
+
+> [View in GitHub >][project]
+
+Customizing
+===========
+
+Basic
+-----
+
+### Theme options
+
+For the default theme (*theme-white*), You can set theme options by adding
+classes to the `` element. The available options are:
+
+#### big-h3
+Makes 3rd-level headings bigger.
+
+``` html
+
+```
+
+#### no-literate
+Disables "literate" mode, where code appears on the right and content text
+appear on the left.
+
+``` html
+
+```
+
+#### large-brief
+Makes the opening paragraph large.
+
+``` html
+
+```
+
+### Adding more markup
+
+You have full control over the HTML file, just add markup wherever you see fit.
+As long as you leave `role='flatdoc-content'` and `role='flatdoc-menu'` empty as
+they are, you'll be fine.
+
+Here are some ideas to get you started.
+
+ * Add a CSS file to make your own CSS adjustments.
+ * Add a 'Tweet' button on top.
+ * Add Google Analytics.
+ * Use CSS to style the IDs in menus (`#acknowledgements + p`).
+
+### JavaScript hooks
+
+Flatdoc emits the events `flatdoc:loading` and `flatdoc:ready` to help you make
+custom behavior when the document loads.
+
+``` js
+$(document).on('flatdoc:ready', function() {
+  // I don't like this section to appear
+  $("#acknowledgements").remove();
+});
+```
+
+Full customization
+------------------
+
+You don't have to be restricted to the given theme. Flatdoc is just really one
+`.js` file that expects 2 HTML elements (for *menu* and *content*). Start with
+the blank template and customize as you see fit.
+
+[Get blank template >][template]
+
+Misc
+====
+
+Inspirations
+------------
+
+The following projects have inspired Flatdoc.
+
+ * [Backbone.js] - Jeremy's projects have always adopted this "one page
+ documentation" approach which I really love.
+
+ * [Docco] - Jeremy's Docco introduced me to the world of literate programming,
+ and side-by-side documentation in general.
+
+ * [Stripe] - Flatdoc took inspiration on the look of their API documentation.
+
+ * [DocumentUp] - This service has the same idea but does a hosted readme 
+ parsing approach.
+
+Attributions
+------------
+
+[Photo](http://www.flickr.com/photos/doug88888/2953428679/) taken from Flickr,
+licensed under Creative Commons.
+
+Acknowledgements
+----------------
+
+© 2013, 2014, Rico Sta. Cruz. Released under the [MIT 
+License](http://www.opensource.org/licenses/mit-license.php).
+
+**Flatdoc** is authored and maintained by [Rico Sta. Cruz][rsc] with help from its 
+[contributors][c].
+
+ * [My website](http://ricostacruz.com) (ricostacruz.com)
+ * [Github](http://github.com/rstacruz) (@rstacruz)
+ * [Twitter](http://twitter.com/rstacruz) (@rstacruz)
+
+[rsc]: http://ricostacruz.com
+[c]:   http://github.com/rstacruz/flatdoc/contributors
+
+[GitHub API]: http://github.com/api
+[marked]: https://github.com/chjj/marked
+[Backbone.js]: http://backbonejs.org
+[dox]: https://github.com/visionmedia/dox
+[Stripe]: https://stripe.com/docs/api
+[Docco]: http://jashkenas.github.com/docco
+[GitHub pages]: https://pages.github.com
+[fences]:https://help.github.com/articles/github-flavored-markdown#syntax-highlighting
+[DocumentUp]: http://documentup.com
+
+[project]: https://github.com/rstacruz/flatdoc
+[template]: https://github.com/rstacruz/flatdoc/raw/gh-pages/templates/template.html
+[blank]: https://github.com/rstacruz/flatdoc/raw/gh-pages/templates/blank.html
+[dist]: https://github.com/rstacruz/flatdoc/tree/gh-pages/v/0.9.0
diff --git a/Profanity.md b/Profanity.md
new file mode 100644
index 0000000..2dd73b4
--- /dev/null
+++ b/Profanity.md
@@ -0,0 +1,261 @@
+Versus API Endpoints
+=======
+
+This documentation lists the API endpoints required for engineers on the Versus team to interface with Versus Backend. The API endpoints are generally grouped into the following.
+
+ * Clients
+ * Dashboard
+ * Email Templates
+ * Profanity Filter
+
+*Current version: [v0.1.0][dist]*
+
+
+Getting started
+---------------
+
+Create a file based on the template, which has a bare DOM, link to the
+scripts, and a link to a theme. It will look something like this (not exact).
+For GitHub projects, simply place this file in your [GitHub pages] branch and
+you're all good to go.
+
+*In short: just download this file and upload it somewhere.*
+
+The main JS and CSS files are also available in [npm] and [bower].
+
+[Default theme template >][template]
+
+[Blank template >][blank]
+
+[bower]: http://bower.io/search/?q=flatdoc
+[npm]: https://www.npmjs.org/package/flatdoc
+
+### Via GitHub
+
+To fetch a Github Repository's readme file, use the `Flatdoc.github` fetcher.
+This will fetch the Readme file of the repository's default branch.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.github('USER/REPO')
+});
+```
+
+You may also fetch another file other than the Readme file, just specify it as
+the 2nd parameter.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.github('USER/REPO', 'Changelog.md')
+});
+```
+
+After you've done this, you probably want to deploy it via [GitHub Pages].
+
+[GitHub Pages guide >][GitHub Pages]
+
+### Via a file
+
+You may also fetch a file. In this example, this fetches the file `Readme.md` in
+the same folder as the HTML file.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.file('Readme.md')
+});
+```
+
+You may actually supply any URL here. It will be fetched via AJAX. This is
+useful for local testing.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.file('http://yoursite.com/Readme.md')
+});
+```
+
+How it works
+------------
+
+Flatdoc is a hosted `.js` file (along with a theme and its assets) that you can
+add into any page hosted anywhere.
+
+#### All client-side
+
+There are no build scripts or 3rd-party services involved. Everything is done in
+the browser. Worried about performance? Oh, It's pretty fast.
+
+Flatdoc utilizes the [GitHub API] to fetch your project's Readme files. You may
+also configure it to fetch any arbitrary URL via AJAX.
+
+#### Lightning-fast parsing
+
+Next, it uses [marked], an extremely fast Markdown parser that has support for
+GitHub flavored Markdown.
+
+Flatdoc then simply renders *menu* and *content* DOM elements to your HTML
+document. Flatdoc also comes with a default theme to style your page for you, or
+you may opt to create your own styles.
+
+Markdown extras
+---------------
+
+Flatdoc offers a few harmless, unobtrusive extras that come in handy in building
+documentation sites.
+
+#### Code highlighting
+
+You can use Markdown code fences to make syntax-highlighted text. Simply
+surround your text with three backticks. This works in GitHub as well.
+See [GitHub Syntax Highlighting][fences] for more info.
+
+    ``` html
+    Hola, mundo
+    ```
+
+#### Blockquotes
+
+Blockquotes show up as side figures. This is useful for providing side
+information or non-code examples.
+
+> Blockquotes are blocks that begin with `>`.
+
+#### Smart quotes
+
+Single quotes, double quotes, and double-hyphens are automatically replaced to
+their typographically-accurate equivalent. This, of course, does not apply to
+`` and `
` blocks to leave code alone.
+
+> "From a certain point onward there is no longer any turning back. That is the
+> point that must be reached."  
+> --Franz Kafka
+
+#### Buttons
+
+If your link text has a `>` at the end (for instance: `Continue >`), they show
+up as buttons.
+
+> [View in GitHub >][project]
+
+Customizing
+===========
+
+Basic
+-----
+
+### Theme options
+
+For the default theme (*theme-white*), You can set theme options by adding
+classes to the `` element. The available options are:
+
+#### big-h3
+Makes 3rd-level headings bigger.
+
+``` html
+
+```
+
+#### no-literate
+Disables "literate" mode, where code appears on the right and content text
+appear on the left.
+
+``` html
+
+```
+
+#### large-brief
+Makes the opening paragraph large.
+
+``` html
+
+```
+
+### Adding more markup
+
+You have full control over the HTML file, just add markup wherever you see fit.
+As long as you leave `role='flatdoc-content'` and `role='flatdoc-menu'` empty as
+they are, you'll be fine.
+
+Here are some ideas to get you started.
+
+ * Add a CSS file to make your own CSS adjustments.
+ * Add a 'Tweet' button on top.
+ * Add Google Analytics.
+ * Use CSS to style the IDs in menus (`#acknowledgements + p`).
+
+### JavaScript hooks
+
+Flatdoc emits the events `flatdoc:loading` and `flatdoc:ready` to help you make
+custom behavior when the document loads.
+
+``` js
+$(document).on('flatdoc:ready', function() {
+  // I don't like this section to appear
+  $("#acknowledgements").remove();
+});
+```
+
+Full customization
+------------------
+
+You don't have to be restricted to the given theme. Flatdoc is just really one
+`.js` file that expects 2 HTML elements (for *menu* and *content*). Start with
+the blank template and customize as you see fit.
+
+[Get blank template >][template]
+
+Misc
+====
+
+Inspirations
+------------
+
+The following projects have inspired Flatdoc.
+
+ * [Backbone.js] - Jeremy's projects have always adopted this "one page
+ documentation" approach which I really love.
+
+ * [Docco] - Jeremy's Docco introduced me to the world of literate programming,
+ and side-by-side documentation in general.
+
+ * [Stripe] - Flatdoc took inspiration on the look of their API documentation.
+
+ * [DocumentUp] - This service has the same idea but does a hosted readme 
+ parsing approach.
+
+Attributions
+------------
+
+[Photo](http://www.flickr.com/photos/doug88888/2953428679/) taken from Flickr,
+licensed under Creative Commons.
+
+Acknowledgements
+----------------
+
+© 2013, 2014, Rico Sta. Cruz. Released under the [MIT 
+License](http://www.opensource.org/licenses/mit-license.php).
+
+**Flatdoc** is authored and maintained by [Rico Sta. Cruz][rsc] with help from its 
+[contributors][c].
+
+ * [My website](http://ricostacruz.com) (ricostacruz.com)
+ * [Github](http://github.com/rstacruz) (@rstacruz)
+ * [Twitter](http://twitter.com/rstacruz) (@rstacruz)
+
+[rsc]: http://ricostacruz.com
+[c]:   http://github.com/rstacruz/flatdoc/contributors
+
+[GitHub API]: http://github.com/api
+[marked]: https://github.com/chjj/marked
+[Backbone.js]: http://backbonejs.org
+[dox]: https://github.com/visionmedia/dox
+[Stripe]: https://stripe.com/docs/api
+[Docco]: http://jashkenas.github.com/docco
+[GitHub pages]: https://pages.github.com
+[fences]:https://help.github.com/articles/github-flavored-markdown#syntax-highlighting
+[DocumentUp]: http://documentup.com
+
+[project]: https://github.com/rstacruz/flatdoc
+[template]: https://github.com/rstacruz/flatdoc/raw/gh-pages/templates/template.html
+[blank]: https://github.com/rstacruz/flatdoc/raw/gh-pages/templates/blank.html
+[dist]: https://github.com/rstacruz/flatdoc/tree/gh-pages/v/0.9.0
diff --git a/Readme.md b/Readme.md
index 0967599..79ad31b 100644
--- a/Readme.md
+++ b/Readme.md
@@ -1,39 +1,64 @@
-Flatdoc
+# Versus API Endpoints
 =======
 
-Flatdoc is a small JavaScript file that fetches Markdown files and renders them
-as full pages. Essentially, it's the easiest
-way to make open source documentation from *Readme* files.
+This documentation lists the API endpoints required for engineers on the Versus team to interface with Versus Backend. The API endpoints are generally grouped into the following.
 
- * No server-side components
- * No build process needed
- * Deployable via GitHub Pages
- * Can fetch GitHub Readme files
- * Gorgeous default theme (and it's responsive)
- * Just create an HTML file and deploy!
+ * Clients
+ * Dashboard
+ * Email Templates
+ * Profanity Filter
 
-*Current version: [v0.9.0][dist]*
+*Current version: [v0.1.0][dist]*
 
-[![Build Status](https://travis-ci.org/rstacruz/flatdoc.svg?branch=gh-pages)](https://travis-ci.org/rstacruz/flatdoc)
 
-Getting started
----------------
+# Clients
+----------------
+
+This has functions for managing clients
+1. Create Client: create a new Versus Sentiment Client
+2. Get Client: get details about a Versus Sentiment Client
+3. Update Client: onboard a Versus Sentiment Client
+4. Create Member: register someone who was added to the list of team members
 
-Create a file based on the template, which has a bare DOM, link to the
-scripts, and a link to a theme. It will look something like this (not exact).
-For GitHub projects, simply place this file in your [GitHub pages] branch and
-you're all good to go.
+# Dasboard
+----------------
+
+This has functions for retrieving mentions
+1. Today Summary: Today's mentions on social media, news, and other sources
+2. Week Summary: This week's mentions on social media, news, and other sources
+3. Month Summary: This month's mentions on social media, news, and other sources
+4. All Time Summary: Total aggregate on our systems of mentions on social media, news, and other sources
+5. Today Details: Mentions from social media, news, and other sources grouped by source for today
+6. Week Details: Mentions from social media, news, and other sources grouped by source for the past week
+7. Today Details: Mentions from social media, news, and other sources grouped by source for the past month
+8. All Time Details: Mentions from social media, news, and other sources grouped by source for all content on our systems
+
+# Email Templates
+----------------
 
-*In short: just download this file and upload it somewhere.*
+This has functions for sending out emails
+1. Custom Alerts: Notify an admin that custom alerts have been set for their account
+2. Dashboard Ready: Notify an admin that the Versus Sentiment dashboard has data for viewing
+3. Designated Primary Email: Notify an admin that they have been designated as a primary contact
+4. Designated Team Member: Notify someone that they have been added as a team member to Versus Sentiment
+5. Respond to Article: Notify a recipient to respond to a social media post
+6. Welcome to Versus: Notify the recipient that their Versus Sentiment account has been created
+7. Your Report: Dispatch a periodic report
 
-The main JS and CSS files are also available in [npm] and [bower].
+# Profanity Filter
+----------------
+
+This function will take a string and return a HTML formattted string with tags that decorate profane words.
+
+
+# Getting started
+---------------
 
-[Default theme template >][template]
+All endpoints are REST. The default method is POST unless otherwise specified. There is a base URL to which you will need to append the endpoint.
 
-[Blank template >][blank]
+> Method: POST
+> Base_URL: 
 
-[bower]: http://bower.io/search/?q=flatdoc
-[npm]: https://www.npmjs.org/package/flatdoc
 
 ### Via GitHub
 
diff --git a/Readme.md.orig b/Readme.md.orig
new file mode 100644
index 0000000..0967599
--- /dev/null
+++ b/Readme.md.orig
@@ -0,0 +1,266 @@
+Flatdoc
+=======
+
+Flatdoc is a small JavaScript file that fetches Markdown files and renders them
+as full pages. Essentially, it's the easiest
+way to make open source documentation from *Readme* files.
+
+ * No server-side components
+ * No build process needed
+ * Deployable via GitHub Pages
+ * Can fetch GitHub Readme files
+ * Gorgeous default theme (and it's responsive)
+ * Just create an HTML file and deploy!
+
+*Current version: [v0.9.0][dist]*
+
+[![Build Status](https://travis-ci.org/rstacruz/flatdoc.svg?branch=gh-pages)](https://travis-ci.org/rstacruz/flatdoc)
+
+Getting started
+---------------
+
+Create a file based on the template, which has a bare DOM, link to the
+scripts, and a link to a theme. It will look something like this (not exact).
+For GitHub projects, simply place this file in your [GitHub pages] branch and
+you're all good to go.
+
+*In short: just download this file and upload it somewhere.*
+
+The main JS and CSS files are also available in [npm] and [bower].
+
+[Default theme template >][template]
+
+[Blank template >][blank]
+
+[bower]: http://bower.io/search/?q=flatdoc
+[npm]: https://www.npmjs.org/package/flatdoc
+
+### Via GitHub
+
+To fetch a Github Repository's readme file, use the `Flatdoc.github` fetcher.
+This will fetch the Readme file of the repository's default branch.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.github('USER/REPO')
+});
+```
+
+You may also fetch another file other than the Readme file, just specify it as
+the 2nd parameter.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.github('USER/REPO', 'Changelog.md')
+});
+```
+
+After you've done this, you probably want to deploy it via [GitHub Pages].
+
+[GitHub Pages guide >][GitHub Pages]
+
+### Via a file
+
+You may also fetch a file. In this example, this fetches the file `Readme.md` in
+the same folder as the HTML file.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.file('Readme.md')
+});
+```
+
+You may actually supply any URL here. It will be fetched via AJAX. This is
+useful for local testing.
+
+``` javascript
+Flatdoc.run({
+  fetcher: Flatdoc.file('http://yoursite.com/Readme.md')
+});
+```
+
+How it works
+------------
+
+Flatdoc is a hosted `.js` file (along with a theme and its assets) that you can
+add into any page hosted anywhere.
+
+#### All client-side
+
+There are no build scripts or 3rd-party services involved. Everything is done in
+the browser. Worried about performance? Oh, It's pretty fast.
+
+Flatdoc utilizes the [GitHub API] to fetch your project's Readme files. You may
+also configure it to fetch any arbitrary URL via AJAX.
+
+#### Lightning-fast parsing
+
+Next, it uses [marked], an extremely fast Markdown parser that has support for
+GitHub flavored Markdown.
+
+Flatdoc then simply renders *menu* and *content* DOM elements to your HTML
+document. Flatdoc also comes with a default theme to style your page for you, or
+you may opt to create your own styles.
+
+Markdown extras
+---------------
+
+Flatdoc offers a few harmless, unobtrusive extras that come in handy in building
+documentation sites.
+
+#### Code highlighting
+
+You can use Markdown code fences to make syntax-highlighted text. Simply
+surround your text with three backticks. This works in GitHub as well.
+See [GitHub Syntax Highlighting][fences] for more info.
+
+    ``` html
+    Hola, mundo
+    ```
+
+#### Blockquotes
+
+Blockquotes show up as side figures. This is useful for providing side
+information or non-code examples.
+
+> Blockquotes are blocks that begin with `>`.
+
+#### Smart quotes
+
+Single quotes, double quotes, and double-hyphens are automatically replaced to
+their typographically-accurate equivalent. This, of course, does not apply to
+`` and `
` blocks to leave code alone.
+
+> "From a certain point onward there is no longer any turning back. That is the
+> point that must be reached."  
+> --Franz Kafka
+
+#### Buttons
+
+If your link text has a `>` at the end (for instance: `Continue >`), they show
+up as buttons.
+
+> [View in GitHub >][project]
+
+Customizing
+===========
+
+Basic
+-----
+
+### Theme options
+
+For the default theme (*theme-white*), You can set theme options by adding
+classes to the `` element. The available options are:
+
+#### big-h3
+Makes 3rd-level headings bigger.
+
+``` html
+
+```
+
+#### no-literate
+Disables "literate" mode, where code appears on the right and content text
+appear on the left.
+
+``` html
+
+```
+
+#### large-brief
+Makes the opening paragraph large.
+
+``` html
+
+```
+
+### Adding more markup
+
+You have full control over the HTML file, just add markup wherever you see fit.
+As long as you leave `role='flatdoc-content'` and `role='flatdoc-menu'` empty as
+they are, you'll be fine.
+
+Here are some ideas to get you started.
+
+ * Add a CSS file to make your own CSS adjustments.
+ * Add a 'Tweet' button on top.
+ * Add Google Analytics.
+ * Use CSS to style the IDs in menus (`#acknowledgements + p`).
+
+### JavaScript hooks
+
+Flatdoc emits the events `flatdoc:loading` and `flatdoc:ready` to help you make
+custom behavior when the document loads.
+
+``` js
+$(document).on('flatdoc:ready', function() {
+  // I don't like this section to appear
+  $("#acknowledgements").remove();
+});
+```
+
+Full customization
+------------------
+
+You don't have to be restricted to the given theme. Flatdoc is just really one
+`.js` file that expects 2 HTML elements (for *menu* and *content*). Start with
+the blank template and customize as you see fit.
+
+[Get blank template >][template]
+
+Misc
+====
+
+Inspirations
+------------
+
+The following projects have inspired Flatdoc.
+
+ * [Backbone.js] - Jeremy's projects have always adopted this "one page
+ documentation" approach which I really love.
+
+ * [Docco] - Jeremy's Docco introduced me to the world of literate programming,
+ and side-by-side documentation in general.
+
+ * [Stripe] - Flatdoc took inspiration on the look of their API documentation.
+
+ * [DocumentUp] - This service has the same idea but does a hosted readme 
+ parsing approach.
+
+Attributions
+------------
+
+[Photo](http://www.flickr.com/photos/doug88888/2953428679/) taken from Flickr,
+licensed under Creative Commons.
+
+Acknowledgements
+----------------
+
+© 2013, 2014, Rico Sta. Cruz. Released under the [MIT 
+License](http://www.opensource.org/licenses/mit-license.php).
+
+**Flatdoc** is authored and maintained by [Rico Sta. Cruz][rsc] with help from its 
+[contributors][c].
+
+ * [My website](http://ricostacruz.com) (ricostacruz.com)
+ * [Github](http://github.com/rstacruz) (@rstacruz)
+ * [Twitter](http://twitter.com/rstacruz) (@rstacruz)
+
+[rsc]: http://ricostacruz.com
+[c]:   http://github.com/rstacruz/flatdoc/contributors
+
+[GitHub API]: http://github.com/api
+[marked]: https://github.com/chjj/marked
+[Backbone.js]: http://backbonejs.org
+[dox]: https://github.com/visionmedia/dox
+[Stripe]: https://stripe.com/docs/api
+[Docco]: http://jashkenas.github.com/docco
+[GitHub pages]: https://pages.github.com
+[fences]:https://help.github.com/articles/github-flavored-markdown#syntax-highlighting
+[DocumentUp]: http://documentup.com
+
+[project]: https://github.com/rstacruz/flatdoc
+[template]: https://github.com/rstacruz/flatdoc/raw/gh-pages/templates/template.html
+[blank]: https://github.com/rstacruz/flatdoc/raw/gh-pages/templates/blank.html
+[dist]: https://github.com/rstacruz/flatdoc/tree/gh-pages/v/0.9.0
diff --git a/clients.html b/clients.html
new file mode 100644
index 0000000..a9b8523
--- /dev/null
+++ b/clients.html
@@ -0,0 +1,52 @@
+
+
+
+  
+  
+  
+
+  Flatdoc
+
+  
+  
+  
+  
+
+  
+  
+  
+  
+
+  
+  
+
+
+
+  
+ +
+ + +
+
+ +
+ +
+
+ + + diff --git a/dashboard.html b/dashboard.html new file mode 100644 index 0000000..a9b8523 --- /dev/null +++ b/dashboard.html @@ -0,0 +1,52 @@ + + + + + + + + Flatdoc + + + + + + + + + + + + + + + + +
+ +
+ + +
+
+ +
+ +
+
+ + + diff --git a/email.html b/email.html new file mode 100644 index 0000000..a9b8523 --- /dev/null +++ b/email.html @@ -0,0 +1,52 @@ + + + + + + + + Flatdoc + + + + + + + + + + + + + + + + +
+ +
+ + +
+
+ +
+ +
+
+ + + diff --git a/index.html b/index.html index 45a95e6..3a047c4 100644 --- a/index.html +++ b/index.html @@ -5,7 +5,7 @@ - Flatdoc + Versus Flatdoc @@ -29,8 +29,8 @@ - - + + @@ -41,8 +41,8 @@
-

Documentation is easy.

-

Flatdoc is the fastest way to create a site for your open source project.

+

Versus API Documentation.

+

.

Flatdoc
@@ -52,8 +52,10 @@
Flatdoc
diff --git a/profanity.html b/profanity.html new file mode 100644 index 0000000..a9b8523 --- /dev/null +++ b/profanity.html @@ -0,0 +1,52 @@ + + + + + + + + Flatdoc + + + + + + + + + + + + + + + + +
+ +
+ + +
+
+ +
+ +
+
+ + + From d2b2179e3a23c7906b297ef10022534d33c3e95f Mon Sep 17 00:00:00 2001 From: securetorobert Date: Fri, 30 Nov 2018 14:47:26 +0100 Subject: [PATCH 03/96] changed the runner --- index.html | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/index.html b/index.html index 3a047c4..6609de1 100644 --- a/index.html +++ b/index.html @@ -21,7 +21,7 @@ @@ -33,8 +33,7 @@ - - + From 33af3629ff4d412c99635174f32387f49f82d106 Mon Sep 17 00:00:00 2001 From: securetorobert Date: Fri, 30 Nov 2018 15:20:01 +0100 Subject: [PATCH 04/96] fixed profanity page --- Profanity.md | 45 ++++++++++----------------------------------- Readme.md | 9 ++------- index.html | 2 +- profanity.html | 32 +++++++++++++++++--------------- 4 files changed, 30 insertions(+), 58 deletions(-) diff --git a/Profanity.md b/Profanity.md index 2dd73b4..df5a32f 100644 --- a/Profanity.md +++ b/Profanity.md @@ -1,44 +1,19 @@ -Versus API Endpoints -======= +# Profanity Filter -This documentation lists the API endpoints required for engineers on the Versus team to interface with Versus Backend. The API endpoints are generally grouped into the following. +This function will take a string and return a HTML formattted string with tags that decorate profane words. - * Clients - * Dashboard - * Email Templates - * Profanity Filter -*Current version: [v0.1.0][dist]* +> Endpoint: versus_profanity_filter - -Getting started ---------------- - -Create a file based on the template, which has a bare DOM, link to the -scripts, and a link to a theme. It will look something like this (not exact). -For GitHub projects, simply place this file in your [GitHub pages] branch and -you're all good to go. - -*In short: just download this file and upload it somewhere.* - -The main JS and CSS files are also available in [npm] and [bower]. - -[Default theme template >][template] - -[Blank template >][blank] - -[bower]: http://bower.io/search/?q=flatdoc -[npm]: https://www.npmjs.org/package/flatdoc - -### Via GitHub - -To fetch a Github Repository's readme file, use the `Flatdoc.github` fetcher. -This will fetch the Readme file of the repository's default branch. +> Payload ``` javascript -Flatdoc.run({ - fetcher: Flatdoc.github('USER/REPO') -}); +{"text": "What the hell"} +``` + +> Result +``` html +what the hell ``` You may also fetch another file other than the Readme file, just specify it as diff --git a/Readme.md b/Readme.md index 79ad31b..ee37dd9 100644 --- a/Readme.md +++ b/Readme.md @@ -1,5 +1,4 @@ # Versus API Endpoints -======= This documentation lists the API endpoints required for engineers on the Versus team to interface with Versus Backend. The API endpoints are generally grouped into the following. @@ -12,7 +11,6 @@ This documentation lists the API endpoints required for engineers on the Versus # Clients ----------------- This has functions for managing clients 1. Create Client: create a new Versus Sentiment Client @@ -21,7 +19,6 @@ This has functions for managing clients 4. Create Member: register someone who was added to the list of team members # Dasboard ----------------- This has functions for retrieving mentions 1. Today Summary: Today's mentions on social media, news, and other sources @@ -34,7 +31,6 @@ This has functions for retrieving mentions 8. All Time Details: Mentions from social media, news, and other sources grouped by source for all content on our systems # Email Templates ----------------- This has functions for sending out emails 1. Custom Alerts: Notify an admin that custom alerts have been set for their account @@ -46,18 +42,17 @@ This has functions for sending out emails 7. Your Report: Dispatch a periodic report # Profanity Filter ----------------- This function will take a string and return a HTML formattted string with tags that decorate profane words. # Getting started ---------------- All endpoints are REST. The default method is POST unless otherwise specified. There is a base URL to which you will need to append the endpoint. > Method: POST -> Base_URL: + +> Base_URL: https://us-central1-versus-dev-212614.cloudfunctions.net/ ### Via GitHub diff --git a/index.html b/index.html index 6609de1..bac2272 100644 --- a/index.html +++ b/index.html @@ -21,7 +21,7 @@ diff --git a/profanity.html b/profanity.html index a9b8523..2b45827 100644 --- a/profanity.html +++ b/profanity.html @@ -20,26 +20,28 @@ -
- -
- - -
-
+