diff --git a/docs/.gitignore b/docs/.gitignore
deleted file mode 100644
index c46da9a7b..000000000
--- a/docs/.gitignore
+++ /dev/null
@@ -1,8 +0,0 @@
-_site/
-.sass-cache/
-.jekyll-metadata
-_pdf
-.DS_Store
-.idea
-vendor/
-.bundle/
diff --git a/docs/.gitlab-ci.yml b/docs/.gitlab-ci.yml
deleted file mode 100644
index 7167efd52..000000000
--- a/docs/.gitlab-ci.yml
+++ /dev/null
@@ -1,26 +0,0 @@
-image: ruby:2.3
-
-variables:
- JEKYLL_ENV: production
-
-test:
- stage: test
- script:
- - sh ./var/build.sh
- - bundle exec jekyll build -d test
- artifacts:
- paths:
- - test
- except:
- - master
-
-pages:
- stage: deploy
- script:
- - sh ./var/build.sh
- - bundle exec jekyll build -d public
- artifacts:
- paths:
- - public
- only:
- - master
diff --git a/docs/.vscode/settings.json b/docs/.vscode/settings.json
deleted file mode 100644
index 5af001d55..000000000
--- a/docs/.vscode/settings.json
+++ /dev/null
@@ -1,6 +0,0 @@
-// Place your settings in this file to overwrite default and user settings.
-{
- "files.associations": {
- "*.html": "liquid"
- }
-}
diff --git a/docs/404.md b/docs/404.md
deleted file mode 100644
index a7b58c002..000000000
--- a/docs/404.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Page Not Found"
-search: exclude
----
-
-Sorry, but the page you were trying to view does not exist. Try searching for it or looking at the URL to see if it looks correct.
diff --git a/docs/Dockerfile b/docs/Dockerfile
deleted file mode 100644
index 7eed201a6..000000000
--- a/docs/Dockerfile
+++ /dev/null
@@ -1,14 +0,0 @@
-FROM jekyll/builder
-
-WORKDIR /tmp
-ADD Gemfile /tmp/
-ADD Gemfile.lock /tmp/
-RUN bundle install
-
-FROM jekyll/jekyll
-
-VOLUME /src
-EXPOSE 4000
-
-WORKDIR /src
-ENTRYPOINT ["jekyll", "serve", "--livereload", "-H", "0.0.0.0"]
diff --git a/docs/Gemfile b/docs/Gemfile
deleted file mode 100644
index 515633aa3..000000000
--- a/docs/Gemfile
+++ /dev/null
@@ -1,7 +0,0 @@
-source "https://rubygems.org"
-
-# to publish on github page
-gem 'github-pages', group: :jekyll_plugins
-
-# to publich without github page
-#gem "jekyll"
diff --git a/docs/Gemfile.lock b/docs/Gemfile.lock
deleted file mode 100644
index dd64253d1..000000000
--- a/docs/Gemfile.lock
+++ /dev/null
@@ -1,253 +0,0 @@
-GEM
- remote: https://rubygems.org/
- specs:
- activesupport (6.0.2.1)
- concurrent-ruby (~> 1.0, >= 1.0.2)
- i18n (>= 0.7, < 2)
- minitest (~> 5.1)
- tzinfo (~> 1.1)
- zeitwerk (~> 2.2)
- addressable (2.7.0)
- public_suffix (>= 2.0.2, < 5.0)
- coffee-script (2.4.1)
- coffee-script-source
- execjs
- coffee-script-source (1.11.1)
- colorator (1.1.0)
- commonmarker (0.17.13)
- ruby-enum (~> 0.5)
- concurrent-ruby (1.1.5)
- dnsruby (1.61.3)
- addressable (~> 2.5)
- em-websocket (0.5.1)
- eventmachine (>= 0.12.9)
- http_parser.rb (~> 0.6.0)
- ethon (0.12.0)
- ffi (>= 1.3.0)
- eventmachine (1.2.7)
- eventmachine (1.2.7-x64-mingw32)
- execjs (2.7.0)
- faraday (1.0.0)
- multipart-post (>= 1.2, < 3)
- ffi (1.12.1)
- ffi (1.12.1-x64-mingw32)
- forwardable-extended (2.6.0)
- gemoji (3.0.1)
- github-pages (203)
- github-pages-health-check (= 1.16.1)
- jekyll (= 3.8.5)
- jekyll-avatar (= 0.7.0)
- jekyll-coffeescript (= 1.1.1)
- jekyll-commonmark-ghpages (= 0.1.6)
- jekyll-default-layout (= 0.1.4)
- jekyll-feed (= 0.13.0)
- jekyll-gist (= 1.5.0)
- jekyll-github-metadata (= 2.12.1)
- jekyll-mentions (= 1.5.1)
- jekyll-optional-front-matter (= 0.3.2)
- jekyll-paginate (= 1.1.0)
- jekyll-readme-index (= 0.3.0)
- jekyll-redirect-from (= 0.15.0)
- jekyll-relative-links (= 0.6.1)
- jekyll-remote-theme (= 0.4.1)
- jekyll-sass-converter (= 1.5.2)
- jekyll-seo-tag (= 2.6.1)
- jekyll-sitemap (= 1.4.0)
- jekyll-swiss (= 1.0.0)
- jekyll-theme-architect (= 0.1.1)
- jekyll-theme-cayman (= 0.1.1)
- jekyll-theme-dinky (= 0.1.1)
- jekyll-theme-hacker (= 0.1.1)
- jekyll-theme-leap-day (= 0.1.1)
- jekyll-theme-merlot (= 0.1.1)
- jekyll-theme-midnight (= 0.1.1)
- jekyll-theme-minimal (= 0.1.1)
- jekyll-theme-modernist (= 0.1.1)
- jekyll-theme-primer (= 0.5.4)
- jekyll-theme-slate (= 0.1.1)
- jekyll-theme-tactile (= 0.1.1)
- jekyll-theme-time-machine (= 0.1.1)
- jekyll-titles-from-headings (= 0.5.3)
- jemoji (= 0.11.1)
- kramdown (= 1.17.0)
- liquid (= 4.0.3)
- mercenary (~> 0.3)
- minima (= 2.5.1)
- nokogiri (>= 1.10.4, < 2.0)
- rouge (= 3.13.0)
- terminal-table (~> 1.4)
- github-pages-health-check (1.16.1)
- addressable (~> 2.3)
- dnsruby (~> 1.60)
- octokit (~> 4.0)
- public_suffix (~> 3.0)
- typhoeus (~> 1.3)
- html-pipeline (2.12.3)
- activesupport (>= 2)
- nokogiri (>= 1.4)
- http_parser.rb (0.6.0)
- i18n (0.9.5)
- concurrent-ruby (~> 1.0)
- jekyll (3.8.5)
- addressable (~> 2.4)
- colorator (~> 1.0)
- em-websocket (~> 0.5)
- i18n (~> 0.7)
- jekyll-sass-converter (~> 1.0)
- jekyll-watch (~> 2.0)
- kramdown (~> 1.14)
- liquid (~> 4.0)
- mercenary (~> 0.3.3)
- pathutil (~> 0.9)
- rouge (>= 1.7, < 4)
- safe_yaml (~> 1.0)
- jekyll-avatar (0.7.0)
- jekyll (>= 3.0, < 5.0)
- jekyll-coffeescript (1.1.1)
- coffee-script (~> 2.2)
- coffee-script-source (~> 1.11.1)
- jekyll-commonmark (1.3.1)
- commonmarker (~> 0.14)
- jekyll (>= 3.7, < 5.0)
- jekyll-commonmark-ghpages (0.1.6)
- commonmarker (~> 0.17.6)
- jekyll-commonmark (~> 1.2)
- rouge (>= 2.0, < 4.0)
- jekyll-default-layout (0.1.4)
- jekyll (~> 3.0)
- jekyll-feed (0.13.0)
- jekyll (>= 3.7, < 5.0)
- jekyll-gist (1.5.0)
- octokit (~> 4.2)
- jekyll-github-metadata (2.12.1)
- jekyll (~> 3.4)
- octokit (~> 4.0, != 4.4.0)
- jekyll-mentions (1.5.1)
- html-pipeline (~> 2.3)
- jekyll (>= 3.7, < 5.0)
- jekyll-optional-front-matter (0.3.2)
- jekyll (>= 3.0, < 5.0)
- jekyll-paginate (1.1.0)
- jekyll-readme-index (0.3.0)
- jekyll (>= 3.0, < 5.0)
- jekyll-redirect-from (0.15.0)
- jekyll (>= 3.3, < 5.0)
- jekyll-relative-links (0.6.1)
- jekyll (>= 3.3, < 5.0)
- jekyll-remote-theme (0.4.1)
- addressable (~> 2.0)
- jekyll (>= 3.5, < 5.0)
- rubyzip (>= 1.3.0)
- jekyll-sass-converter (1.5.2)
- sass (~> 3.4)
- jekyll-seo-tag (2.6.1)
- jekyll (>= 3.3, < 5.0)
- jekyll-sitemap (1.4.0)
- jekyll (>= 3.7, < 5.0)
- jekyll-swiss (1.0.0)
- jekyll-theme-architect (0.1.1)
- jekyll (~> 3.5)
- jekyll-seo-tag (~> 2.0)
- jekyll-theme-cayman (0.1.1)
- jekyll (~> 3.5)
- jekyll-seo-tag (~> 2.0)
- jekyll-theme-dinky (0.1.1)
- jekyll (~> 3.5)
- jekyll-seo-tag (~> 2.0)
- jekyll-theme-hacker (0.1.1)
- jekyll (~> 3.5)
- jekyll-seo-tag (~> 2.0)
- jekyll-theme-leap-day (0.1.1)
- jekyll (~> 3.5)
- jekyll-seo-tag (~> 2.0)
- jekyll-theme-merlot (0.1.1)
- jekyll (~> 3.5)
- jekyll-seo-tag (~> 2.0)
- jekyll-theme-midnight (0.1.1)
- jekyll (~> 3.5)
- jekyll-seo-tag (~> 2.0)
- jekyll-theme-minimal (0.1.1)
- jekyll (~> 3.5)
- jekyll-seo-tag (~> 2.0)
- jekyll-theme-modernist (0.1.1)
- jekyll (~> 3.5)
- jekyll-seo-tag (~> 2.0)
- jekyll-theme-primer (0.5.4)
- jekyll (> 3.5, < 5.0)
- jekyll-github-metadata (~> 2.9)
- jekyll-seo-tag (~> 2.0)
- jekyll-theme-slate (0.1.1)
- jekyll (~> 3.5)
- jekyll-seo-tag (~> 2.0)
- jekyll-theme-tactile (0.1.1)
- jekyll (~> 3.5)
- jekyll-seo-tag (~> 2.0)
- jekyll-theme-time-machine (0.1.1)
- jekyll (~> 3.5)
- jekyll-seo-tag (~> 2.0)
- jekyll-titles-from-headings (0.5.3)
- jekyll (>= 3.3, < 5.0)
- jekyll-watch (2.2.1)
- listen (~> 3.0)
- jemoji (0.11.1)
- gemoji (~> 3.0)
- html-pipeline (~> 2.2)
- jekyll (>= 3.0, < 5.0)
- kramdown (1.17.0)
- liquid (4.0.3)
- listen (3.2.1)
- rb-fsevent (~> 0.10, >= 0.10.3)
- rb-inotify (~> 0.9, >= 0.9.10)
- mercenary (0.3.6)
- mini_portile2 (2.4.0)
- minima (2.5.1)
- jekyll (>= 3.5, < 5.0)
- jekyll-feed (~> 0.9)
- jekyll-seo-tag (~> 2.1)
- minitest (5.14.0)
- multipart-post (2.1.1)
- nokogiri (1.10.7)
- mini_portile2 (~> 2.4.0)
- nokogiri (1.10.7-x64-mingw32)
- mini_portile2 (~> 2.4.0)
- octokit (4.15.0)
- faraday (>= 0.9)
- sawyer (~> 0.8.0, >= 0.5.3)
- pathutil (0.16.2)
- forwardable-extended (~> 2.6)
- public_suffix (3.1.1)
- rb-fsevent (0.10.3)
- rb-inotify (0.10.1)
- ffi (~> 1.0)
- rouge (3.13.0)
- ruby-enum (0.7.2)
- i18n
- rubyzip (2.0.0)
- safe_yaml (1.0.5)
- sass (3.7.4)
- sass-listen (~> 4.0.0)
- sass-listen (4.0.0)
- rb-fsevent (~> 0.9, >= 0.9.4)
- rb-inotify (~> 0.9, >= 0.9.7)
- sawyer (0.8.2)
- addressable (>= 2.3.5)
- faraday (> 0.8, < 2.0)
- terminal-table (1.8.0)
- unicode-display_width (~> 1.1, >= 1.1.1)
- thread_safe (0.3.6)
- typhoeus (1.3.1)
- ethon (>= 0.9.0)
- tzinfo (1.2.6)
- thread_safe (~> 0.1)
- unicode-display_width (1.6.1)
- zeitwerk (2.2.2)
-
-PLATFORMS
- ruby
- x64-mingw32
-
-DEPENDENCIES
- github-pages
-
-BUNDLED WITH
- 2.1.4
diff --git a/docs/_config.yml b/docs/_config.yml
deleted file mode 100644
index 5f5844fdb..000000000
--- a/docs/_config.yml
+++ /dev/null
@@ -1,122 +0,0 @@
-repository: tomjoht/documentation-theme-jekyll
-
-output: web
-# this property is useful for conditional filtering of content that is separate from the PDF.
-
-topnav_title: Superalgos Documentation
-# this appears on the top navigation bar next to the home button
-
-site_title: Superalgos Crypto Intelligence Suite Documentation
-# this appears in the html browser tab for the site title (seen mostly by search engines, not users)
-
-company_name: Superalgos.org
-# this appears in the footer
-
-github_editme_path:
-# if you're using Github, provide the basepath to the branch you've created for reviews, following the sample here. if not, leave this value blank.
-
-# gitlab_editme_path: tomjoht/documentation-theme-jekyll/blob/gh-pages/
-# if you're using GitLab, provide the basepath to the branch you've created for reviews, following the sample here. if not, leave this value blank.
-
-google_analytics: UA-121623442-1
-# if you have google-analytics ID, put it in. if not, edit this value to blank.
-
-host: 127.0.0.1
-# the preview server used. Leave as is.
-
-port: 4000
-# the port where the preview is rendered. You can leave this as is unless you have other Jekyll builds using this same port that might cause conflicts. in that case, use another port such as 4006.
-
-exclude:
- - .idea/
- - .gitignore
- - vendor
-# these are the files and directories that jekyll will exclude from the build
-
-feedback_subject_line:
-
-feedback_email:
-# used as a contact email for the Feedback link in the top navigation bar
-
-# feedback_disable: true
-# if you uncomment the previous line, the Feedback link gets removed
-
-feedback_text: "Need help?"
-# if you uncomment the previous line, it changes the Feedback text
-
-feedback_link: "https://t.me/superalgoscommunity"
-# if you uncomment the previous line, it changes where the feedback link points to
-
-highlighter: rouge
-# library used for syntax highlighting
-
-markdown: kramdown
-kramdown:
- input: GFM
- auto_ids: true
- hard_wrap: false
- syntax_highlighter: rouge
- parse_block_html: true
-
-# filter used to process markdown. note that kramdown differs from github-flavored markdown in some subtle ways
-
-collections:
- tooltips:
- output: false
-# collections are declared here. this renders the content in _tooltips and processes it, but doesn't output it as actual files in the output unless you change output to true
-
-defaults:
- -
- scope:
- path: ""
- type: "pages"
- values:
- layout: "page"
- comments: false
- # if you don't want to use Commento.io and just hide comments, change true to false wherever you see the comments property
- search: true
- sidebar: home_sidebar
- topnav: topnav
- -
- scope:
- path: ""
- type: "tooltips"
- values:
- layout: "page"
- search: true
- tooltip: true
-
- -
- scope:
- path: ""
- type: "posts"
- values:
- layout: "post"
- comments: false
- # if you don't want to use Commento.io and just hide comments, change true to false wherever you see the comments property
- search: true
- sidebar: home_sidebar
- topnav: topnav
-
-# these are defaults used for the frontmatter for these file types
-
-sidebars:
-- mydoc_sidebar
-- suite_sidebar
-- syst_sidebar
-- algo_sidebar
-- disc_sidebar
-- smart_sidebar
-- coach_sidebar
-- market_sidebar
-- mine_sidebar
-
-description: "The Superalgos Suite Documentation covers general workings of Superalgos and of each of the products in the suite."
-# the description is used in the feed.xml file
-
-# needed for sitemap.xml file only
-# url: http://idratherbewriting.com
-# baseurl: /documentation-theme-jekyll
-
-
-github: [metadata]
diff --git a/docs/_data/A PENDING LIST.md b/docs/_data/A PENDING LIST.md
deleted file mode 100644
index 3b9e5f7ef..000000000
--- a/docs/_data/A PENDING LIST.md
+++ /dev/null
@@ -1,11 +0,0 @@
-ATOMIZE:
-
-Hierarchies tables, by segment.
-
-How to pages, create template.
-
-* Find each hierarchy. Create hierarchies map.
-* Set up and exchange account.
-* Set up an exchange account key.
-* Set up an exchange account key instance.
-* Expand and collapse data structures.
\ No newline at end of file
diff --git a/docs/_data/alerts.yml b/docs/_data/alerts.yml
deleted file mode 100644
index 157e1622b..000000000
--- a/docs/_data/alerts.yml
+++ /dev/null
@@ -1,15 +0,0 @@
-tip: '
Tip: '
-note: '
Note: '
-important: '
Important: '
-warning: '
Warning: '
-end: '
'
-
-callout_danger: '
'
-callout_default: '
'
-callout_primary: '
'
-callout_success: '
'
-callout_info: '
'
-callout_warning: '
'
-
-hr_faded: ''
-hr_shaded: ''
\ No newline at end of file
diff --git a/docs/_data/charting_space.md b/docs/_data/charting_space.md
deleted file mode 100644
index f211db8e8..000000000
--- a/docs/_data/charting_space.md
+++ /dev/null
@@ -1,19 +0,0 @@
-charting_space: "The charting space is the hierarchy that governs the configuration of the charts, and the bidimensional space on which charts are drawn."
-
-viewport: "The viewport is a window through which you may look into the charting space."
-
-dashboard: "A dashboard is a collection of time machines, each containing any number of charts."
-
-time_machine: "A time machine synchronizes multiple timeline charts over the same timeline. Timeline charts within a time machine may have different rate scales or time frame scales, but their time scale will always match."
-
-time_scale: "The time scale controls the scale of the horizontal axis, that is, the timeline of the corresponding time machine, and of all of the timeline charts within it."
-
-rate_scale: "The rate scale controls the scale of the vertical axis, that is, the scale of the quoted asset, either of the time machine or of the timeline chart, depending on where the node is located."
-
-time_frame_scale: "The time frame scale controls the time frame setting, that is, the period represented by each candle, either of the time machine or of the timeline chart, depending on where the node is located."
-
-timeline_chart: "The timeline chart represents a chart within a time machine, which may have independent rate and time frame scales, as well as particular layers."
-
-layers_manager: "The layer manager determines which layers will be visible on the corresponding timeline chart."
-
-layer: "A layer represents a reference to a data product in the data storage node of the network hierarchy. Conceptually, it means that a certain data product, which exists in a certain location on the network, holds the data to be rendered on the charts."
\ No newline at end of file
diff --git a/docs/_data/charting_space.yml b/docs/_data/charting_space.yml
deleted file mode 100644
index f211db8e8..000000000
--- a/docs/_data/charting_space.yml
+++ /dev/null
@@ -1,19 +0,0 @@
-charting_space: "The charting space is the hierarchy that governs the configuration of the charts, and the bidimensional space on which charts are drawn."
-
-viewport: "The viewport is a window through which you may look into the charting space."
-
-dashboard: "A dashboard is a collection of time machines, each containing any number of charts."
-
-time_machine: "A time machine synchronizes multiple timeline charts over the same timeline. Timeline charts within a time machine may have different rate scales or time frame scales, but their time scale will always match."
-
-time_scale: "The time scale controls the scale of the horizontal axis, that is, the timeline of the corresponding time machine, and of all of the timeline charts within it."
-
-rate_scale: "The rate scale controls the scale of the vertical axis, that is, the scale of the quoted asset, either of the time machine or of the timeline chart, depending on where the node is located."
-
-time_frame_scale: "The time frame scale controls the time frame setting, that is, the period represented by each candle, either of the time machine or of the timeline chart, depending on where the node is located."
-
-timeline_chart: "The timeline chart represents a chart within a time machine, which may have independent rate and time frame scales, as well as particular layers."
-
-layers_manager: "The layer manager determines which layers will be visible on the corresponding timeline chart."
-
-layer: "A layer represents a reference to a data product in the data storage node of the network hierarchy. Conceptually, it means that a certain data product, which exists in a certain location on the network, holds the data to be rendered on the charts."
\ No newline at end of file
diff --git a/docs/_data/concepts.md b/docs/_data/concepts.md
deleted file mode 100644
index 0df3d5553..000000000
--- a/docs/_data/concepts.md
+++ /dev/null
@@ -1,42 +0,0 @@
-design_space: "The design space is the visual environment that features all the information available to the system and the user, and that enables users to exert control over the whole system. You may think of the design space as your desktop."
-
-workspace: "The workspace refers to the body of information managed by the system. Every data structure in the form of strategies, the configuration of different parts of the system, operational settings, and the relationships among them live within the workspace."
-
-node: "A node is a small data structure containing information which may be related to market information, trading intelligence, the operation of the system or other concepts. They are visually represented by icons on the workspace."
-
-structure_of_nodes: "Nodes may be chained together forming structures of nodes. In every structure of nodes there is a parent node with offsprings. That is, a structure of nodes is a data structure composed of any node and its offspring."
-
-parent-offspring_relationships: "Nodes in structures of nodes are chained to each other by so-called parent-offspring relationships. These relationships are visually represented by orange dotted lines, which may turn yellow or blue depending on certain visualization properties that the user may control. When nodes are chained together they form structures of nodes."
-
-chain: "Nodes in the workspace may be unchained or detached from its parent, carrying all offspring with it. When a node is left unchained, it is no longer taken into account in the logic of the hierarchy, as it no longer belongs to it. When a node is chained back or reattached to the hierarchy, it goes back to being functional."
-
-hierarchy: "A hierarchy is the representation of an overarching, top-level concept resulting in a long chain of nodes, usually with many ramifications. Currently, the system manages five different types of hierarchies: the crypto ecosystem, the charting space, trading systems, the network, and data mines."
-
-reference: "A reference is a mechanism by which information in a node is related to, or accessed by, other nodes. The ability of a node to establish a reference with another node enables the first to access the information or features entailed in the second one."
-
-session: "A session refers to a backtesting, paper trading, forward testing or live trading session. When the term is used without specifying the type of session, then it refers to the overall concept by which a trading bot instance—based on datasets exposed as products by other bots—applies the trading logic defined on a trading system in any of the aforementioned modes."
-
-sensor_bot: "A sensor bot is an algorithm that extracts raw data from external sources (i.e.: exchanges, Twitter, etc.) and stores it in a dataset that other bots may consume."
-
-indicator_bot: "An indicator bot is an algorithm that processes information that other bots have generated, and produces elaborate datasets for others to consume."
-
-bot: "A bot is an algorithm defined in a data mine. Superalgos manages three types of bots: sensors, indicators, and the trading bot."
-
-trading_bot: "Based on datasets exposed as products by other bots (counting sensors, indicators and even other trading bots), a trading bot applies the trading logic defined on a trading system to, on one side, generate a complete trading simulation (outputting datasets that include trades, the action of strategies, validation of conditions, etc.), and on the other side, manage the execution of orders when on a forward testing or live trading session."
-
-superalgos_protocol: "In conceptual terms, the Superalgos Protocol determines the structure in which the information describing a trading system is stored and guides how traders shall create and automate strategies. In practical terms, the protocol results in a file with a specific format capable of holding all the information concerning any number and variety of strategies. In its current early version, the protocol is the description of a JSON object which defines the desired automation."
-
-hierarchies_directory: "The hierarchies directory is the part of the documentation that features a description of the complete catalog of nodes of each hierachy"
-
-data_product: "A data product is a collection of datasets that bots output for others to consume."
-
-dataset: "A dataset is a collection of plain-text files storing information in the form of arrays of records in the standard JSON format, although not as objects with named properties, but as arrays."
-
-process: "A process is an algorithm defined in the process definition structure of nodes of the corresponding bot and data mine."
-
-masters_data_mine: "Masters is a data mine shipping with the system. It features the main trading bot and sensor bot, along with indicators offering the following data products: Candles, Volumes, Candle Stairs Patterns, Volume Stairs Patterns, Bollinger Bands, Percentage Bandwidth, Bollinger Channels, and Bollinger Sub-Channels."
-
-sparta_data_mine: "Sparta is a data mine shipping with the system. It features indicators offering the following data products: Relative Strength Index (RSI 14), Simple Moving Average (SMA), Exponential Moving Average (EMA), and Moving Average Convergence/Divergence (MACD)."
-
-pending: "balanceAssetA, balanceAssetB, overfitting, supported assets, supported exchanges, supported markets"
-
diff --git a/docs/_data/concepts.yml b/docs/_data/concepts.yml
deleted file mode 100644
index 0df3d5553..000000000
--- a/docs/_data/concepts.yml
+++ /dev/null
@@ -1,42 +0,0 @@
-design_space: "The design space is the visual environment that features all the information available to the system and the user, and that enables users to exert control over the whole system. You may think of the design space as your desktop."
-
-workspace: "The workspace refers to the body of information managed by the system. Every data structure in the form of strategies, the configuration of different parts of the system, operational settings, and the relationships among them live within the workspace."
-
-node: "A node is a small data structure containing information which may be related to market information, trading intelligence, the operation of the system or other concepts. They are visually represented by icons on the workspace."
-
-structure_of_nodes: "Nodes may be chained together forming structures of nodes. In every structure of nodes there is a parent node with offsprings. That is, a structure of nodes is a data structure composed of any node and its offspring."
-
-parent-offspring_relationships: "Nodes in structures of nodes are chained to each other by so-called parent-offspring relationships. These relationships are visually represented by orange dotted lines, which may turn yellow or blue depending on certain visualization properties that the user may control. When nodes are chained together they form structures of nodes."
-
-chain: "Nodes in the workspace may be unchained or detached from its parent, carrying all offspring with it. When a node is left unchained, it is no longer taken into account in the logic of the hierarchy, as it no longer belongs to it. When a node is chained back or reattached to the hierarchy, it goes back to being functional."
-
-hierarchy: "A hierarchy is the representation of an overarching, top-level concept resulting in a long chain of nodes, usually with many ramifications. Currently, the system manages five different types of hierarchies: the crypto ecosystem, the charting space, trading systems, the network, and data mines."
-
-reference: "A reference is a mechanism by which information in a node is related to, or accessed by, other nodes. The ability of a node to establish a reference with another node enables the first to access the information or features entailed in the second one."
-
-session: "A session refers to a backtesting, paper trading, forward testing or live trading session. When the term is used without specifying the type of session, then it refers to the overall concept by which a trading bot instance—based on datasets exposed as products by other bots—applies the trading logic defined on a trading system in any of the aforementioned modes."
-
-sensor_bot: "A sensor bot is an algorithm that extracts raw data from external sources (i.e.: exchanges, Twitter, etc.) and stores it in a dataset that other bots may consume."
-
-indicator_bot: "An indicator bot is an algorithm that processes information that other bots have generated, and produces elaborate datasets for others to consume."
-
-bot: "A bot is an algorithm defined in a data mine. Superalgos manages three types of bots: sensors, indicators, and the trading bot."
-
-trading_bot: "Based on datasets exposed as products by other bots (counting sensors, indicators and even other trading bots), a trading bot applies the trading logic defined on a trading system to, on one side, generate a complete trading simulation (outputting datasets that include trades, the action of strategies, validation of conditions, etc.), and on the other side, manage the execution of orders when on a forward testing or live trading session."
-
-superalgos_protocol: "In conceptual terms, the Superalgos Protocol determines the structure in which the information describing a trading system is stored and guides how traders shall create and automate strategies. In practical terms, the protocol results in a file with a specific format capable of holding all the information concerning any number and variety of strategies. In its current early version, the protocol is the description of a JSON object which defines the desired automation."
-
-hierarchies_directory: "The hierarchies directory is the part of the documentation that features a description of the complete catalog of nodes of each hierachy"
-
-data_product: "A data product is a collection of datasets that bots output for others to consume."
-
-dataset: "A dataset is a collection of plain-text files storing information in the form of arrays of records in the standard JSON format, although not as objects with named properties, but as arrays."
-
-process: "A process is an algorithm defined in the process definition structure of nodes of the corresponding bot and data mine."
-
-masters_data_mine: "Masters is a data mine shipping with the system. It features the main trading bot and sensor bot, along with indicators offering the following data products: Candles, Volumes, Candle Stairs Patterns, Volume Stairs Patterns, Bollinger Bands, Percentage Bandwidth, Bollinger Channels, and Bollinger Sub-Channels."
-
-sparta_data_mine: "Sparta is a data mine shipping with the system. It features indicators offering the following data products: Relative Strength Index (RSI 14), Simple Moving Average (SMA), Exponential Moving Average (EMA), and Moving Average Convergence/Divergence (MACD)."
-
-pending: "balanceAssetA, balanceAssetB, overfitting, supported assets, supported exchanges, supported markets"
-
diff --git a/docs/_data/crypto_ecosystem.md b/docs/_data/crypto_ecosystem.md
deleted file mode 100644
index 70dd9a429..000000000
--- a/docs/_data/crypto_ecosystem.md
+++ /dev/null
@@ -1,29 +0,0 @@
-crypto_ecosystem: "The crypto ecosystem is a hierarchy that contains definitions about third-parties, including exchanges and their markets, as well as accounts of users with those third parties."
-
-crypto_exchanges: "The crypto exchanges node groups definitions of the different exchanges the user may interact with."
-
-crypto_exchange: "A crypto exchange node holds the definitions of assets and markets in a specific exchange."
-
-exchange_assets: "The exchange assets node groups the definitions of assets."
-
-asset: "An asset node is the definition of an asset listed at the corresponding exchange."
-
-exchange_markets: "The exchange markets node groups the definitions of markets."
-
-market: "A market is the definition of a pair of assets (i.e.: BTC-USDT) listed as a market in the corresponding exchange."
-
-market_base_asset: "The market base asset is a reference to one of the assets listed at the exchange as defined under the exchange assets node. It is the asset in the pair used to provide a quote—a price—for the quoted asset."
-
-market_quoted_asset: "The market quoted asset is a reference to one of the assets listed at the exchange as defined under the exchange assets node. It is the asset in the pair for which a quote is given, denominated in the base asset."
-
-exchange_accounts: "The exchange accounts node groups the different accounts the user may have with the corresponding exchange."
-
-user_account: "A user account represents a single account with the corresponding exchange, holding the definitions of user assets, including keys and balances."
-
-user_keys: "The user keys node groups the various exchange account keys the user may have under the corresponding account with the exchange."
-
-exchange_account_key: "The exchange account key holds the definition of the key name and secret provided by the corresponding exchange to access the user account via the exchange API."
-
-user_assets: "The user assets node groups the assets the user has at the exchange."
-
-exchange_account_asset: "The exchange account asset represents a single asset the user has at the exchange."
diff --git a/docs/_data/crypto_ecosystem.yml b/docs/_data/crypto_ecosystem.yml
deleted file mode 100644
index 70dd9a429..000000000
--- a/docs/_data/crypto_ecosystem.yml
+++ /dev/null
@@ -1,29 +0,0 @@
-crypto_ecosystem: "The crypto ecosystem is a hierarchy that contains definitions about third-parties, including exchanges and their markets, as well as accounts of users with those third parties."
-
-crypto_exchanges: "The crypto exchanges node groups definitions of the different exchanges the user may interact with."
-
-crypto_exchange: "A crypto exchange node holds the definitions of assets and markets in a specific exchange."
-
-exchange_assets: "The exchange assets node groups the definitions of assets."
-
-asset: "An asset node is the definition of an asset listed at the corresponding exchange."
-
-exchange_markets: "The exchange markets node groups the definitions of markets."
-
-market: "A market is the definition of a pair of assets (i.e.: BTC-USDT) listed as a market in the corresponding exchange."
-
-market_base_asset: "The market base asset is a reference to one of the assets listed at the exchange as defined under the exchange assets node. It is the asset in the pair used to provide a quote—a price—for the quoted asset."
-
-market_quoted_asset: "The market quoted asset is a reference to one of the assets listed at the exchange as defined under the exchange assets node. It is the asset in the pair for which a quote is given, denominated in the base asset."
-
-exchange_accounts: "The exchange accounts node groups the different accounts the user may have with the corresponding exchange."
-
-user_account: "A user account represents a single account with the corresponding exchange, holding the definitions of user assets, including keys and balances."
-
-user_keys: "The user keys node groups the various exchange account keys the user may have under the corresponding account with the exchange."
-
-exchange_account_key: "The exchange account key holds the definition of the key name and secret provided by the corresponding exchange to access the user account via the exchange API."
-
-user_assets: "The user assets node groups the assets the user has at the exchange."
-
-exchange_account_asset: "The exchange account asset represents a single asset the user has at the exchange."
diff --git a/docs/_data/data_mine.md b/docs/_data/data_mine.md
deleted file mode 100644
index db0c65757..000000000
--- a/docs/_data/data_mine.md
+++ /dev/null
@@ -1,77 +0,0 @@
-data_mine: "A data mine is a hierarchy that contains definitions of bots, including the trading bot, sensors, indicators, and even plotters. These definitions make up the actual programs of such bots—the source code."
-
-sensor_bot: "A sensor bot is an algorithm that extracts raw data from external sources (i.e.: exchanges, Twitter, etc.) and stores it in a dataset that other bots may consume."
-
-indicator_bot: "An indicator bot is an algorithm that processes information that other bots have generated, and produces elaborate datasets for others to consume."
-
-trading_bot: "Based on datasets exposed as products by other bots (counting sensors, indicators and even other trading bots), a trading bot applies the trading logic defined on a trading system to, on one side, generate a complete trading simulation (outputting datasets that include trades, the action of strategies, validation of conditions, etc.), and on the other side, manage the execution of orders when on a forward testing or live trading session."
-
-process_definition: "The process definition node groups all definitions required for a process to function. The Multi-Period-Market Process deals with time frames of one hour and above. The Multi-Period-Daily Process deals with time frames of 45 minutes and below."
-
-process_output: "The process output groups the definitions of which datasets are impacted by the process, that is, which datasets the process builds or takes a part in building."
-
-output_dataset: "The output dataset is a reference to a dataset definition. By establishing such reference, the process acquires the definitions as of how the dataset is to be constructed."
-
-process_dependencies: "Process dependencies are references to various data structures on which the process depends to function."
-
-status_dependency: "Status dependencies are references to a status report that define which process the process establishing the reference depends on."
-
-data_dependency: "Data dependencies are references established with dataset definitions of other bots, determining which datasets the process establishing the reference uses as input."
-
-status_report: "Status reports serve as temporal annotations that bots read every time they run to know what was done in the previous cycle and what the state of affairs is at present. Status reports are dynamic, and they change constantly, with updates after every cycle of the associated process."
-
-execution_started_event: "The execution started event is the event that triggers the execution of a process. It usually references the execution finished event of another process on which the process depends on."
-
-execution_finished_event: "The execution finished event is the event that processes trigger once they have finished an execution cycle. The event is broadcasted to whoever wants to listen, so that other bots may know when the process has finished its execution cycle."
-
-product_definition: "The product definition node holds all definitions that make up a product, including how the product is calculated and the datasets the product is comprised of."
-
-dataset_definition: "A dataset definition contains a configuration file that defines all aspects of the dataset. There are two types of dataset definitions: Multi-Period-Market and Multi-Period-Daily."
-
-record_definition: "The record definition is where indicators define how many fields, what fields and in which order those fields will be stored in each record."
-
-record_property: "A record is the compendium of information stored for each period of time, including the start and end datetime of the period along with the properties that provide the information the indicator is meant to generate."
-
-formula: "In the context of a record definition, formulas are used to assign a value to the property, usually in the form of a variable declared in the calculation or data building procedure."
-
-calculations_procedure: "The calculations procedure processes information to be fed to calculated properties. Calculated properties are not stored in the data set; instead, they are calculated in real-time as the data is consumed by others."
-
-procedure_loop: "The procedure loop holds the JavaScript code that reads an input, processes the information, and generates an output recursively."
-
-javascript_code: "The JavaScript code node may hold any snippet of valid JavaScript."
-
-procedure_initialization: "The procedure initialization is used to initialize variables used by the procedure loop."
-
-data_building_procedure: "The data building procedure processes information to be fed to properties that are stored in the output dataset."
-
-plotter: "A plotter is a device used to produce a graphic representation of datasets generated by bots."
-
-plotter_module: "A plotter module is a device within a plotter that contains the definitions to create the visualization for a product definition."
-
-plotter_panel: "A plotter panel usually shows numerical representations of data over the charts on a small window or panel. The plotter panel node features definitions to make that possible."
-
-panel_data: "A panel data node represents a data field to be plotted on the plotter panel."
-
-data_formula: "A data formula is a device used to assign a value to the panel data, usually in the form of the name of the corresponding record property."
-
-shapes: "The shapes node contains definitions of polygons and styles to be rendered on a per-period basis over the charts."
-
-chart_points: "A chart points groups definitions of coordinate points used to define polygons."
-
-point: "A point is a definition of an [x,y] coordinate. The value [x] usually represents a datetime. The value [y] may refer to a price or some other concept."
-
-point_formula: "A point formula is a node used to input the [x,y] coordinates of a point."
-
-polygon: "A polygon features definitions that makeup shapes and their styles."
-
-polygon_vertex: "A polygon vertex is a reference to a point defined in the chart points, constituting a specific coordinate to be used as a vertex of a shape."
-
-polygon_border: "A polygon border is a shape defined by at least two vertices used to draw lines or to apply a style to the stroke of a closed shape."
-
-style: "A style is a definition of color and opacity in case of a polygon body, and color, opacity and line thickness in case of polygon borders."
-
-style_condition: "A style condition is a rule that allows applying an alternative style in cases where the rule validates true."
-
-polygon_body: "A polygon body is the fill of a shape made out of at least three vertices."
-
-pending: "daily files, market files and so on, Multi-Period-Daily, Multi-Period-Market"
\ No newline at end of file
diff --git a/docs/_data/data_mine.yml b/docs/_data/data_mine.yml
deleted file mode 100644
index db0c65757..000000000
--- a/docs/_data/data_mine.yml
+++ /dev/null
@@ -1,77 +0,0 @@
-data_mine: "A data mine is a hierarchy that contains definitions of bots, including the trading bot, sensors, indicators, and even plotters. These definitions make up the actual programs of such bots—the source code."
-
-sensor_bot: "A sensor bot is an algorithm that extracts raw data from external sources (i.e.: exchanges, Twitter, etc.) and stores it in a dataset that other bots may consume."
-
-indicator_bot: "An indicator bot is an algorithm that processes information that other bots have generated, and produces elaborate datasets for others to consume."
-
-trading_bot: "Based on datasets exposed as products by other bots (counting sensors, indicators and even other trading bots), a trading bot applies the trading logic defined on a trading system to, on one side, generate a complete trading simulation (outputting datasets that include trades, the action of strategies, validation of conditions, etc.), and on the other side, manage the execution of orders when on a forward testing or live trading session."
-
-process_definition: "The process definition node groups all definitions required for a process to function. The Multi-Period-Market Process deals with time frames of one hour and above. The Multi-Period-Daily Process deals with time frames of 45 minutes and below."
-
-process_output: "The process output groups the definitions of which datasets are impacted by the process, that is, which datasets the process builds or takes a part in building."
-
-output_dataset: "The output dataset is a reference to a dataset definition. By establishing such reference, the process acquires the definitions as of how the dataset is to be constructed."
-
-process_dependencies: "Process dependencies are references to various data structures on which the process depends to function."
-
-status_dependency: "Status dependencies are references to a status report that define which process the process establishing the reference depends on."
-
-data_dependency: "Data dependencies are references established with dataset definitions of other bots, determining which datasets the process establishing the reference uses as input."
-
-status_report: "Status reports serve as temporal annotations that bots read every time they run to know what was done in the previous cycle and what the state of affairs is at present. Status reports are dynamic, and they change constantly, with updates after every cycle of the associated process."
-
-execution_started_event: "The execution started event is the event that triggers the execution of a process. It usually references the execution finished event of another process on which the process depends on."
-
-execution_finished_event: "The execution finished event is the event that processes trigger once they have finished an execution cycle. The event is broadcasted to whoever wants to listen, so that other bots may know when the process has finished its execution cycle."
-
-product_definition: "The product definition node holds all definitions that make up a product, including how the product is calculated and the datasets the product is comprised of."
-
-dataset_definition: "A dataset definition contains a configuration file that defines all aspects of the dataset. There are two types of dataset definitions: Multi-Period-Market and Multi-Period-Daily."
-
-record_definition: "The record definition is where indicators define how many fields, what fields and in which order those fields will be stored in each record."
-
-record_property: "A record is the compendium of information stored for each period of time, including the start and end datetime of the period along with the properties that provide the information the indicator is meant to generate."
-
-formula: "In the context of a record definition, formulas are used to assign a value to the property, usually in the form of a variable declared in the calculation or data building procedure."
-
-calculations_procedure: "The calculations procedure processes information to be fed to calculated properties. Calculated properties are not stored in the data set; instead, they are calculated in real-time as the data is consumed by others."
-
-procedure_loop: "The procedure loop holds the JavaScript code that reads an input, processes the information, and generates an output recursively."
-
-javascript_code: "The JavaScript code node may hold any snippet of valid JavaScript."
-
-procedure_initialization: "The procedure initialization is used to initialize variables used by the procedure loop."
-
-data_building_procedure: "The data building procedure processes information to be fed to properties that are stored in the output dataset."
-
-plotter: "A plotter is a device used to produce a graphic representation of datasets generated by bots."
-
-plotter_module: "A plotter module is a device within a plotter that contains the definitions to create the visualization for a product definition."
-
-plotter_panel: "A plotter panel usually shows numerical representations of data over the charts on a small window or panel. The plotter panel node features definitions to make that possible."
-
-panel_data: "A panel data node represents a data field to be plotted on the plotter panel."
-
-data_formula: "A data formula is a device used to assign a value to the panel data, usually in the form of the name of the corresponding record property."
-
-shapes: "The shapes node contains definitions of polygons and styles to be rendered on a per-period basis over the charts."
-
-chart_points: "A chart points groups definitions of coordinate points used to define polygons."
-
-point: "A point is a definition of an [x,y] coordinate. The value [x] usually represents a datetime. The value [y] may refer to a price or some other concept."
-
-point_formula: "A point formula is a node used to input the [x,y] coordinates of a point."
-
-polygon: "A polygon features definitions that makeup shapes and their styles."
-
-polygon_vertex: "A polygon vertex is a reference to a point defined in the chart points, constituting a specific coordinate to be used as a vertex of a shape."
-
-polygon_border: "A polygon border is a shape defined by at least two vertices used to draw lines or to apply a style to the stroke of a closed shape."
-
-style: "A style is a definition of color and opacity in case of a polygon body, and color, opacity and line thickness in case of polygon borders."
-
-style_condition: "A style condition is a rule that allows applying an alternative style in cases where the rule validates true."
-
-polygon_body: "A polygon body is the fill of a shape made out of at least three vertices."
-
-pending: "daily files, market files and so on, Multi-Period-Daily, Multi-Period-Market"
\ No newline at end of file
diff --git a/docs/_data/definitions.yml b/docs/_data/definitions.yml
deleted file mode 100644
index f29f39277..000000000
--- a/docs/_data/definitions.yml
+++ /dev/null
@@ -1,12 +0,0 @@
-elephant: "This is a sample definition."
-
-baseball: "Baseball is considered America's pasttime sport, though that may be more of a historical term than a current one. There's a lot more excitement about football than baseball. A baseball game is somewhat of a snooze to watch, for the most part."
-
-basketball: "Basketball is a sport involving two teams of five players each competing to put a ball through a small circular rim 10 feet above the ground. Basketball requires players to be in top physical condition, since they spend most of the game running back and forth along a 94-foot-long floor."
-
-football: "No doubt the most fun sport to watch, football also manages to accrue the most injuries with the players. From concussions to blown knees, football players have short sport lives."
-
-soccer: "If there's one sport that dominates the world landscape, it's soccer. However, US soccer fans are few and far between. Apart from the popularity of soccer during the World Cup, most people don't even know the name of the professional soccer organization in their area."
-
-workspace: "The workspace is a concept that refers to the visual environment that contains all hierarchies with all of their nodes, nodes that may be floating around detached from hierarchies, and the information regarding the physical position and status of all nodes within the design space, even those detached from the hierarchies. You may think of the workspace as your desktop. It is not part of any of the hierarchies; instead, it contains them."
-
diff --git a/docs/_data/glossary.yml b/docs/_data/glossary.yml
deleted file mode 100644
index e953fe73b..000000000
--- a/docs/_data/glossary.yml
+++ /dev/null
@@ -1,11 +0,0 @@
-jekyll_platform: "Jekyll is a static site generator that builds sites using most modern web technologies."
-
-fractious: "Like a little mischevious child, full of annoying and constant trouble."
-
-gratuitous: "Something that is unwarranted and uncouth, like the social equivalent of a flagrant foul."
-
-haughty: "Proud and flaunting it. Holding your head high up like a snooty, too-good-for-everything rich person."
-
-impertinent: "Someone acting rude and insensitive to others."
-
-intrepid: "Brave and courageous especially in a difficult, dangerous situation."
\ No newline at end of file
diff --git a/docs/_data/how_to.md b/docs/_data/how_to.md
deleted file mode 100644
index 42bb00ce9..000000000
--- a/docs/_data/how_to.md
+++ /dev/null
@@ -1,3 +0,0 @@
-find_a_hierarchy: "To find a hierarchy, locate the workspace node and pan the design space in the appropriate cardinal direction: N for the Sparta Data Mine, NE for the WHB Trading System, E for the BRR Trading System, SE for Super Scripts, S for Network, SW for Crypto Ecosystem, W for Charting System, and NE for Masters Data Mine."
-
-go_to_the_workspace_node: "To go the workspace node, use the browser's zoom feature. This coincidentally takes you to the center of the design space, exactly where the workspace node is located by default."
\ No newline at end of file
diff --git a/docs/_data/how_to.yml b/docs/_data/how_to.yml
deleted file mode 100644
index 42bb00ce9..000000000
--- a/docs/_data/how_to.yml
+++ /dev/null
@@ -1,3 +0,0 @@
-find_a_hierarchy: "To find a hierarchy, locate the workspace node and pan the design space in the appropriate cardinal direction: N for the Sparta Data Mine, NE for the WHB Trading System, E for the BRR Trading System, SE for Super Scripts, S for Network, SW for Crypto Ecosystem, W for Charting System, and NE for Masters Data Mine."
-
-go_to_the_workspace_node: "To go the workspace node, use the browser's zoom feature. This coincidentally takes you to the center of the design space, exactly where the workspace node is located by default."
\ No newline at end of file
diff --git a/docs/_data/network.md b/docs/_data/network.md
deleted file mode 100644
index 2798b8439..000000000
--- a/docs/_data/network.md
+++ /dev/null
@@ -1,53 +0,0 @@
-network: "The network hierarchy contains definitions regarding the physical location in which certain nodes live or function. For instance, a certain process my run and store data in your local machine or some other machine in the network."
-
-network_node: "A network node represents a machine in the network on which processes run or data is stored."
-
-data_mining: "Data mining is the activity of processing data. You need to process data to feed charts, and so that the trading bot may make decisions based on quality information. In the context of the network hierarchy, the data-mining node groups the task managers handling sensor and indicator bots instances."
-
-testing_environment: "The testing environment node organizes trading sessions involving testing of trading systems."
-
-production_environment: "The production environment node organizes trading sessions involving live trading."
-
-task_manager: "A task manager is a device used to organize and control any number of tasks, which, in turn, control bot instances. You use a task manager to start or stop several tasks at the same time."
-
-task: "A task is the device used to control bot instances, that is, to start and stop bots, including sensors, indicators and the trading bot."
-
-indicator_bot_instance: "An indicator bot instance is a reference to an indicator bot as defined in a data mine. The instance of the bot runs the defined processes and generates the defined data products."
-
-indicator_process_instance: "An indicator process instance is a reference to the process definition of an indicator bot, as defined in a data mine."
-
-sensor_bot_instance: "A sensor bot instance is a reference to a sensor bot as defined in a data mine. The instance of the bot runs the defined processes and generates the defined data products."
-
-sensor_process_instance: "A sensor process instance is a reference to the process definition of a sensor bot, as defined in a data mine."
-
-market_reference: "A market reference is a reference to a specific market in a specific exchange, as defined in the Crypto Ecosystem hierarchy. The reference dictates which market the process works with."
-
-trading_bot_instance: "A trading bot instance is a reference to the trading bot as defined in the Masters data mine. The instance of the bot runs the defined processes and generates the defined data products."
-
-trading_process_instance: "A trading process instance is a reference to the process definition of the trading bot, as defined in the Masters data mine."
-
-backtesting_session: "A backtesting session is a trading mode by which the trading bot instance reads historic market data in a user-defined datetime range, applies the rules defined in the associated trading system, and generates a trading simulation."
-
-paper_trading_session: "A paper trading session is a trading mode by which the trading bot instance reads a live market data feed, applies the rules defined in the associated trading system, and generates a trading simulation."
-
-forward_testing_session: "A forward testing session is a trading mode by which the trading bot instance performs live trading with a user-defined fraction of the available capital."
-
-live_trading_session: "A live trading session is a trading mode by which the trading bot instance reads a live market data feed, applies the rules as defined in the associated trading system, places the corresponding orders at the associated exchange, and stores the defined data products."
-
-key_instance: "The key instance is a reference to an exchange account key as defined in a specific user account, in a specific exchange, on the Crypto Ecosystem hierarchy."
-
-data_storage: "The data storage node controls aspects of what data is to be stored in the corresponding network node."
-
-session_based_data: "Session-based data refers to data that is generated as a consequence of running a session, that is, data the trading bot instance generates while running backtesting, paper trading, forward testing or live trading sessions."
-
-session_reference: "A session reference establishes which session is the one which shall store data in the current location."
-
-single_market_data: "Single market data represents the group of data products generated by the referenced session, in a specific market."
-
-data_product: "A data product represents the collection of datasets generated by the instance of a bot as defined in the corresponding data mine."
-
-dataset: "A data set is a collection of files stored in the designated location, as per the definitions on the referenced data product in the corresponding data mine."
-
-session_independent_data: "Session independent data refers to data generated by sensors and indicators, not related to trading sessions."
-
-session: "A session, or trading session, is a specific mode in which the trading bot instance may be run. The trading bot is prepared to run three different types of testing sessions—backtesting, paper trading, and forward testing—and the live trading session mode."
diff --git a/docs/_data/network.yml b/docs/_data/network.yml
deleted file mode 100644
index 2798b8439..000000000
--- a/docs/_data/network.yml
+++ /dev/null
@@ -1,53 +0,0 @@
-network: "The network hierarchy contains definitions regarding the physical location in which certain nodes live or function. For instance, a certain process my run and store data in your local machine or some other machine in the network."
-
-network_node: "A network node represents a machine in the network on which processes run or data is stored."
-
-data_mining: "Data mining is the activity of processing data. You need to process data to feed charts, and so that the trading bot may make decisions based on quality information. In the context of the network hierarchy, the data-mining node groups the task managers handling sensor and indicator bots instances."
-
-testing_environment: "The testing environment node organizes trading sessions involving testing of trading systems."
-
-production_environment: "The production environment node organizes trading sessions involving live trading."
-
-task_manager: "A task manager is a device used to organize and control any number of tasks, which, in turn, control bot instances. You use a task manager to start or stop several tasks at the same time."
-
-task: "A task is the device used to control bot instances, that is, to start and stop bots, including sensors, indicators and the trading bot."
-
-indicator_bot_instance: "An indicator bot instance is a reference to an indicator bot as defined in a data mine. The instance of the bot runs the defined processes and generates the defined data products."
-
-indicator_process_instance: "An indicator process instance is a reference to the process definition of an indicator bot, as defined in a data mine."
-
-sensor_bot_instance: "A sensor bot instance is a reference to a sensor bot as defined in a data mine. The instance of the bot runs the defined processes and generates the defined data products."
-
-sensor_process_instance: "A sensor process instance is a reference to the process definition of a sensor bot, as defined in a data mine."
-
-market_reference: "A market reference is a reference to a specific market in a specific exchange, as defined in the Crypto Ecosystem hierarchy. The reference dictates which market the process works with."
-
-trading_bot_instance: "A trading bot instance is a reference to the trading bot as defined in the Masters data mine. The instance of the bot runs the defined processes and generates the defined data products."
-
-trading_process_instance: "A trading process instance is a reference to the process definition of the trading bot, as defined in the Masters data mine."
-
-backtesting_session: "A backtesting session is a trading mode by which the trading bot instance reads historic market data in a user-defined datetime range, applies the rules defined in the associated trading system, and generates a trading simulation."
-
-paper_trading_session: "A paper trading session is a trading mode by which the trading bot instance reads a live market data feed, applies the rules defined in the associated trading system, and generates a trading simulation."
-
-forward_testing_session: "A forward testing session is a trading mode by which the trading bot instance performs live trading with a user-defined fraction of the available capital."
-
-live_trading_session: "A live trading session is a trading mode by which the trading bot instance reads a live market data feed, applies the rules as defined in the associated trading system, places the corresponding orders at the associated exchange, and stores the defined data products."
-
-key_instance: "The key instance is a reference to an exchange account key as defined in a specific user account, in a specific exchange, on the Crypto Ecosystem hierarchy."
-
-data_storage: "The data storage node controls aspects of what data is to be stored in the corresponding network node."
-
-session_based_data: "Session-based data refers to data that is generated as a consequence of running a session, that is, data the trading bot instance generates while running backtesting, paper trading, forward testing or live trading sessions."
-
-session_reference: "A session reference establishes which session is the one which shall store data in the current location."
-
-single_market_data: "Single market data represents the group of data products generated by the referenced session, in a specific market."
-
-data_product: "A data product represents the collection of datasets generated by the instance of a bot as defined in the corresponding data mine."
-
-dataset: "A data set is a collection of files stored in the designated location, as per the definitions on the referenced data product in the corresponding data mine."
-
-session_independent_data: "Session independent data refers to data generated by sensors and indicators, not related to trading sessions."
-
-session: "A session, or trading session, is a specific mode in which the trading bot instance may be run. The trading bot is prepared to run three different types of testing sessions—backtesting, paper trading, and forward testing—and the live trading session mode."
diff --git a/docs/_data/sidebars/suite_sidebar.yml b/docs/_data/sidebars/suite_sidebar.yml
deleted file mode 100644
index 839bbd20f..000000000
--- a/docs/_data/sidebars/suite_sidebar.yml
+++ /dev/null
@@ -1,457 +0,0 @@
-# This is your sidebar TOC. The sidebar code loops through sections here and provides the appropriate formatting.
-
-entries:
-- title: sidebar
- product: Superalgos
- version: 0.0.6
- folders:
-
-# - title:
-# output: pdf
-# type: frontmatter
-# folderitems:
-# - title:
-# url: /titlepage.html
-# output: pdf
-# type: frontmatter
-# - title:
-# url: /tocpage.html
-# output: pdf
-# type: frontmatter
-
- - title: Before you begin
- output: web
- folderitems:
-
- - title: Welcome!
- url: /index.html
- output: web
- type: homepage
-
- - title: What to expect
- url: /suite-what-to-expect.html
- output: web
-
- - title: System requirements
- url: /suite-system-requirements.html
- output: web
-
- - title: Getting Started
- output: web
- folderitems:
-
- - title: "Step 0: Get ready"
- url: /suite-step-0.html
- output: web
-
- - title: "Step 1: Download and set up"
- url: /suite-step-1.html
- output: web
-
- - title: "Step 2: Run the system"
- url: /suite-step-2.html
- output: web
-
- - title: "Step 3: First impression"
- url: /suite-step-3.html
- output: web
-
- - title: "Step 4: Import a workspace"
- url: /suite-step-4.html
- output: web
-
- - title: "Step 5: Quick overview"
- url: /suite-step-5.html
- output: web
-
- - title: "Step 6: Pull and process data"
- url: /suite-step-6.html
- output: web
-
-# - title: Run your first backtest
-# url: /suite-run-your-first-backtest.html
-# output: web
-
-# - title: Update datasets
-# url: /suite-update-datasets.html
-# output: web
-
-# - title: Trade with an open-source strategy
-# url: /suite-trade-live-with-an-open-source-strategy.html
-# output: web
-
-# - title: What's next?
-# url: /suite-what-is-next.html
-# output: web
-
-# - title: Charts
-# output: web
-# folderitems:
-
-# - title: Overview
-# url: /suite-charts-overview.html
-# output: web
-
-
-
-# - title: Layers panel
-# url: /suite-layers-panel.html
-# output: web
-
- - title: Design space
- output: web
- folderitems:
-
- - title: Fundamental concepts
- url: /suite-fundamental-design-space-concepts.html
- output: web
-
- - title: Interface
- url: /suite-design-space-interface.html
- output: web
-
- - title: Hierarchies
- url: /suite-hierarchies.html
- output: web
-
- - title: Charting space
- output: web
- folderitems:
-
- - title: Fundamental concepts
- url: /suite-fundamental-charting-space-concepts.html
- output: web
-
- - title: Interface
- url: /suite-charting-space-interface.html
- output: web
-
- - title: Arranging a dashboard
- url: /suite-arranging-dashboard.html
- output: web
- class: childItem
-
- - title: "Navigating time machines & charts"
- url: /suite-navigating-time-machines.html
- output: web
- class: childItem
-
- - title: Scale boxes
- url: /suite-scale-boxes.html
- output: web
- class: childItem
-
- - title: Layer managers
- url: /suite-layer-managers.html
- output: web
- class: childItem
-
- - title: Available layers
- url: /suite-available-layers.html
- output: web
-
- - title: Masters bots layers
- url: /suite-masters-bots-layers.html
- output: web
- class: childItem
-
- - title: Sparta bots layers
- url: /suite-sparta-bots-layers.html
- output: web
- class: childItem
-
- - title: Simulation layers
- url: /suite-simulation-layers.html
- output: web
- class: childItem
-
- - title: Live trading history layer
- url: /suite-live-trading-history-layer.html
- output: web
- class: childItem
-
- - title: Charting space
- url: /suite-charting-space.html
- output: web
-
- - title: Scales
- url: /suite-scales.html
- output: web
- class: childItem
-
- - title: Timeline charts
- url: /suite-timeline-charts.html
- output: web
- class: childItem
-
- - title: Trading system
- output: web
- folderitems:
-
- - title: Trading systems
- url: /suite-trading-systems.html
- output: web
-
- - title: Strategies
- url: /suite-strategies.html
- output: web
-
- - title: Situations, conditions and formulas
- url: /suite-situations-conditions-formulas.html
- output: web
-
- - title: Syntax overview
- url: /suite-syntax-overview.html
- output: web
- class: childItem
-
- - title: Internal variables
- url: /suite-internal-variables.html
- output: web
- class: childItem
-
- - title: Masters indicators
- url: /suite-masters-indicators.html
- output: web
- class: childItem
-
- - title: Sparta indicators
- url: /suite-sparta-indicators.html
- output: web
- class: childItem
-
-# - title: Using non-included indicators
-# url: /suite-using-non-included-indicators.html
-# output: web
-
- - title: Trading sessions
- url: /suite-trading-sessions.html
- output: web
-
- - title: Parameters
- url: /suite-parameters.html
- output: web
- class: childItem
-
- - title: Infrastructure
- output: web
- folderitems:
-
- - title: Fundamental concepts
- url: /suite-fundamental-infrastructure-concepts.html
- output: web
-
- - title: Crypto ecosystem
- url: /suite-crypto-ecosystem.html
- output: web
-
- - title: Exchange assets
- url: /suite-exchange-assets.html
- output: web
- class: childItem
-
- - title: Exchange markets
- url: /suite-exchange-markets.html
- output: web
- class: childItem
-
- - title: Exchange accounts
- url: /suite-exchange-accounts.html
- output: web
- class: childItem
-
- - title: Network
- url: /suite-network.html
- output: web
-
- - title: Data storage
- url: /suite-data-storage.html
- output: web
- class: childItem
-
- - title: Data mining
- url: /suite-data-mining.html
- output: web
- class: childItem
-
- - title: Testing environment
- url: /suite-testing-environment.html
- output: web
- class: childItem
-
- - title: Production environment
- url: /suite-production-environment.html
- output: web
- class: childItem
-
-# - title: Backtests & Paper Trading
-# output: web
-# folderitems:
-
-# - title: Overview
-# url: /suite-testing-overview.html
-# output: web
-
-# - title: Session parameters
-# url: /suite-session-parameters.html
-# output: web
-
-# - title: Simulation layers
-# url: /suite-simulation-layers.html
-# output: web
-
-# - title: Advanced backtesting
-# url: /suite-advanced-backtesting.html
-# output: web
-
-# - title: Forward Tests & Live Trading
-# output: web
-# folderitems:
-
-# - title: Overview
-# url: /suite-live-trading-overview.html
-# output: web
-
-# - title: Getting ready to trade live
-# url: /suite-getting-ready-to-trade-live.html
-# output: web
-
-# - title: Live trading history layer
-# url: /suite-live-trading-history-layer.html
-# output: web
-
-# - title: Execution limitations
-# url: /suite-execution-limitations.html
-# output: web
-
-# - title: Multiple sessions
-# url: /suite-multiple-forward-testing-and-live-trading-sessions.html
-# output: web
-
- - title: Data mines
- output: web
- folderitems:
-
- - title: Data mines
- url: /suite-data-mines.html
- output: web
-
- - title: Indicator bots
- url: /suite-indicator-bots.html
- output: web
-
- - title: Process definition
- url: /suite-process-definition.html
- output: web
- class: childItem
-
- - title: Product definition
- url: /suite-product-definition.html
- output: web
- class: childItem
-
- - title: Plotters
- url: /suite-plotters.html
- output: web
-
- - title: Plotter Panel
- url: /suite-plotter-panel.html
- output: web
- class: childItem
-
- - title: Shapes
- url: /suite-shapes.html
- output: web
- class: childItem
-
-# - title: Datasets
-# url: /suite-datasets.html
-# output: web
-
-# - title: Dependencies
-# url: /suite-dependencies.html
-# output: web
-
-# - title: Build an indicator
-# url: /suite-build-an-indicator.html
-# output: web
-
-# - title: Build a plotter
-# url: /suite-build-a-plotter.html
-# output: web
-
- - title: Productivity Tools
- output: web
- folderitems:
-
- - title: Backups
- url: /suite-backups.html
- output: web
-
- - title: Clones
- url: /suite-clones.html
- output: web
-
- - title: Shares
- url: /suite-shares.html
- output: web
-
-# - title: Telegram Announcements
-# url: /suite-telegram-announcements.html
-# output: web
-
- - title: Hierarchies directory
- output: web
- folderitems:
-
- - title: Crypto ecosystem
- url: /suite-crypto-ecosystem-hierarchy.html
- output: web
-
- - title: Charting space
- url: /suite-charting-space-hierarchy.html
- output: web
-
- - title: Trading system
- url: /suite-trading-system-hierarchy.html
- output: web
-
- - title: Network
- url: /suite-network-hierarchy.html
- output: web
-
- - title: Data mine
- url: /suite-data-mine-hierarchy.html
- output: web
-
- - title: Troubleshooting
- output: web
- folderitems:
-
- - title: Upgrading your existing installation
- url: /suite-upgrading-your-existing-instalation.html
- output: web
-
- - title: My system gets slow
- url: /suite-my-system-gets-slow.html
- output: web
-
- - title: On-screen errors and warnings
- url: /suite-on-screen-errors-and-warnings.html
- output: web
-
- - title: Market data seems to be outdated
- url: /suite-market-data-indicators-seem-to-be-outdated.html
- output: web
-
- - title: Reporting bugs
- url: /suite-reporting-bugs.html
- output: web
-
- - title: Consulting logs
- url: /suite-consulting-logs.html
- output: web
-
-
-
-
diff --git a/docs/_data/sidebars/systematic_sidebar.yml b/docs/_data/sidebars/systematic_sidebar.yml
deleted file mode 100644
index 37928de63..000000000
--- a/docs/_data/sidebars/systematic_sidebar.yml
+++ /dev/null
@@ -1,116 +0,0 @@
-# This is your sidebar TOC. The sidebar code loops through sections here and provides the appropriate formatting.
-
-entries:
-- title: sidebar
- product: Systematic Trading
- version:
- folders:
-
- - title:
- output: pdf
- type: frontmatter
- folderitems:
- - title:
- url: /titlepage.html
- output: pdf
- type: frontmatter
-
- - title:
- url: /tocpage.html
- output: pdf
- type: frontmatter
-
- - title: Trading System
- output: web
- folderitems:
-
- - title: Overview
- url: /systematic-trading-system-overview.html
- output: web
-
- - title: Working with strategies
- url: /systematic-working-with-strategies.html
- output: web
-
- - title: Conditions & Formulas
- output: web
- folderitems:
-
- - title: Syntax Overview
- url: /systematic-sysntax-overview.html
- output: web
-
- - title: Internal variables
- url: /systematic-internal-variables.html
- output: web
-
- - title: Indicators included in the data release
- url: /systematic-indicators-included-in-the-data-release.html
- output: web
-
- - title: Indicators not included in the release
- url: /systematic-indicators-not-included-in-the-data-release.html
- output: web
-
- - title: Using indicators not included in the release
- url: /systematic-using-indicators-not-included-in-the-data-release.html
- output: web
-
- - title: Backtests & Paper Trading
- output: web
- folderitems:
-
- - title: Overview
- url: /systematic-testing-overview.html
- output: web
-
- - title: Session parameters
- url: /systematic-session-parameters.html
- output: web
-
- - title: Simulation layers
- url: /systematic-simulation-layers.html
- output: web
-
- - title: Advanced backtesting
- url: /systematic-advanced-backtesting.html
- output: web
-
- - title: Forward Tests & Live Trading
- output: web
- folderitems:
-
- - title: Overview
- url: /systematic-live-trading-overview.html
- output: web
-
- - title: Getting ready to trade live
- url: /systematic-getting-ready-to-trade-live.html
- output: web
-
- - title: Live trading history layer
- url: /systematic-live-trading-history-layer.html
- output: web
-
- - title: Execution limitations
- url: /systematic-execution-limitations.html
- output: web
-
- - title: Multiple sessions
- url: /systematic-multiple-forward-testing-and-live-trading-sessions.html
- output: web
-
- - title: API Keys
- output: web
- folderitems:
-
- - title: Poloniex API keys
- url: /systematic-poloniex-api-keys.html
- output: web
-
-
-
-
-
-
-
diff --git a/docs/_data/strings.yml b/docs/_data/strings.yml
deleted file mode 100644
index 228aa579d..000000000
--- a/docs/_data/strings.yml
+++ /dev/null
@@ -1,5 +0,0 @@
-
-
-# placed here for translation purposes
-search_placeholder_text: Search...
-search_no_results_text: No results found.
diff --git a/docs/_data/tags.yml b/docs/_data/tags.yml
deleted file mode 100644
index 79d2545ae..000000000
--- a/docs/_data/tags.yml
+++ /dev/null
@@ -1,15 +0,0 @@
-# Note:
-# If you are using the createtag script, don't leave an blank line at the end of this file.
-# In other words, the last line must be the last tag in the allowed-tags list.
-allowed-tags:
- - getting_started
- - content_types
- - navigation
- - formatting
- - publishing
- - single_sourcing
- - special_layouts
- - collaboration
- - news
- - troubleshooting
- - mobile
diff --git a/docs/_data/terms.yml b/docs/_data/terms.yml
deleted file mode 100644
index 1e9144818..000000000
--- a/docs/_data/terms.yml
+++ /dev/null
@@ -1 +0,0 @@
-apple: "apple - the fruit of a disiduous tree."
\ No newline at end of file
diff --git a/docs/_data/topnav.yml b/docs/_data/topnav.yml
deleted file mode 100644
index 42e71b4a8..000000000
--- a/docs/_data/topnav.yml
+++ /dev/null
@@ -1,32 +0,0 @@
-## Topnav single links
-## if you want to list an external url, use external_url instead of url. the theme will apply a different link base.
-topnav:
-- title: Topnav
- items:
- - title: Issues
- external_url: https://github.com/Superalgos/Platform/issues
- - title: Suite Docs
- url: index.html
-
-#Topnav dropdowns
-#topnav_dropdowns:
-#- title: Topnav dropdowns
-# folders:
-# - title: Product Docs
-# folderitems:
-# - title: Systematic Trading
-# url: /systematic-trading-system-overview.html
-# - title: Algorithmic Trading
-# url: /algorithmic-trading-system-overview.html
-# - title: Discretionary Trading
-# url: /discretionary-introduction.html
-# - title: Smart Holding
-# url: /smart-introduction.html
-# - title: Trading Coach
-# url: /coach-introduction_page.html
-# - title: Signals Broadcast
-# url: /signal-introduction.html
-# - title: Markets Research
-# url: /market-introduction_page.html
-# - title: Data Mining
-# url: /mine-introduction.html
\ No newline at end of file
diff --git a/docs/_data/trading_system.md b/docs/_data/trading_system.md
deleted file mode 100644
index 1d322eacd..000000000
--- a/docs/_data/trading_system.md
+++ /dev/null
@@ -1,65 +0,0 @@
-trading_system: "A trading system is a framework handling the low-level logic that serves to structure the processes and methods used to implement and deploy trading strategies."
-
-parameters: "Parameters are user definitions over several concepts that influence the behavior of trading sessions and improve the quality of simulations. When defined at the level of a session, parameters take precedence over those defined at the level of the trading system, which acts as a fallback instance."
-
-base_asset: "In the context of a trading system or a session, the base asset is the asset in the pair on which capital stands when out of a trade."
-
-quoted_asset: "In the context of a trading system or a session, the quoted asset is the asset in the pair for which capital is traded."
-
-time_frame: "The time frame is the frequency on which the session runs, meaning that the associated process instance runs once per unit of the time frame."
-
-time_range: "The time range is the specific period between a starting and an ending date on which the session runs."
-
-slippage: "The slippage is an assumption on the difference between the simulated rate and the actual fill rate of an order, most relevant in the context of backtesting and paper-trading sessions. The parameter is a tool to make simulations more realistic."
-
-fee_structure: "The fee structure is a parameter enabling users to enter assumptions on fees, to be computed on backtesting and paper trading sessions to make simulations more realistic."
-
-strategy: "A strategy is a set of actions occurring in stages, designed to achieve a specific goal within a broader plan, via executing trades."
-
-trigger_stage: "The trigger stage deals with monitoring the market in search of trading opportunities with the corresponding strategy."
-
-trigger-on_event: "The trigger-on event defines the set of rules that need to be met for the corresponding strategy to be triggered on. A strategy that is triggered may use all the capital available to the trading system, preventing other strategies in the system from triggering."
-
-situation: "A situation refers to a specific state of the market in which a certain event should take place, as defined by any number of conditions."
-
-condition: "Conditions are rules within a situation. When all conditions under a situation validate true, then the situation gets validated as well, and the associated event is triggered."
-
-trigger-off_event: "The trigger-off event defines the situation in which the corresponding strategy shall be triggered-off. A strategy that is triggered-off releases the capital in reserve and makes it available to other strategies in the trading system."
-
-take_position_event: "The take position event defines the situation that needs to be met to enter a trade."
-
-open_stage: "The open stage deals with all the parameters that define a trade, including position rate and size as well as initial stop and take profit targets."
-
-initial_definition: "The initial definition node groups the parameters that define the trade at the moment the position is taken."
-
-initial_stop: "The initial stop defines the initial target to stop a loss before the trade gets to be managed."
-
-phase_0: "Phase 0 represents the starting point for a stop or take profit target, which may be managed in subsequent phases, on the manage stage."
-
-formula: "A formula is a mathematical expression intended to determine a numerical value to be applied dynamically to a certain property."
-
-next_phase_event: "The next-phase event describes a market situation upon which the management of the trade should shift from one phase to the next."
-
-initial_take_profit: "The initial take profit defines the initial target to take profit before the trade gets to be managed."
-
-position_size: "The size of the position is the amount of capital that will go in the trade, denominated in the quoted asset. The position size node allows setting a size for the position using a formula."
-
-position_rate: "The position rate is the rate at which the position is taken, denominated in the quoted asset. The position rate node allows setting the desired position rate with a formula."
-
-open_execution: "Open execution is the node that will eventually hold the information regarding the execution of the trade opening orders."
-
-manage_stage: "The manage stage is the third stage in the definition of a strategy and deals with the management of stop and take-profit targets."
-
-stop: "The stop node in the manage stage groups all phases managing stop loss targets as the trade develops."
-
-phase_1: "Phase 1 is the first phase in the management of a stop or take-profit target. The management of targets may have as many phases as required."
-
-take_profit: "Take profit node in the manage stage groups all phases managing take profit targets as the trade develops."
-
-close_stage: "Close stage is not developed yet. In the future, it will deal with the execution of the closing orders, trading log, and related matters."
-
-close_execution: "Close execution is the node that will eventually hold the information regarding the execution of the closing orders."
-
-event: "An event is an action triggered by predefined market situations."
-
-javascript_code: "The JavaScript code node may hold any snippet of valid JavaScript."
\ No newline at end of file
diff --git a/docs/_data/trading_system.yml b/docs/_data/trading_system.yml
deleted file mode 100644
index 1d322eacd..000000000
--- a/docs/_data/trading_system.yml
+++ /dev/null
@@ -1,65 +0,0 @@
-trading_system: "A trading system is a framework handling the low-level logic that serves to structure the processes and methods used to implement and deploy trading strategies."
-
-parameters: "Parameters are user definitions over several concepts that influence the behavior of trading sessions and improve the quality of simulations. When defined at the level of a session, parameters take precedence over those defined at the level of the trading system, which acts as a fallback instance."
-
-base_asset: "In the context of a trading system or a session, the base asset is the asset in the pair on which capital stands when out of a trade."
-
-quoted_asset: "In the context of a trading system or a session, the quoted asset is the asset in the pair for which capital is traded."
-
-time_frame: "The time frame is the frequency on which the session runs, meaning that the associated process instance runs once per unit of the time frame."
-
-time_range: "The time range is the specific period between a starting and an ending date on which the session runs."
-
-slippage: "The slippage is an assumption on the difference between the simulated rate and the actual fill rate of an order, most relevant in the context of backtesting and paper-trading sessions. The parameter is a tool to make simulations more realistic."
-
-fee_structure: "The fee structure is a parameter enabling users to enter assumptions on fees, to be computed on backtesting and paper trading sessions to make simulations more realistic."
-
-strategy: "A strategy is a set of actions occurring in stages, designed to achieve a specific goal within a broader plan, via executing trades."
-
-trigger_stage: "The trigger stage deals with monitoring the market in search of trading opportunities with the corresponding strategy."
-
-trigger-on_event: "The trigger-on event defines the set of rules that need to be met for the corresponding strategy to be triggered on. A strategy that is triggered may use all the capital available to the trading system, preventing other strategies in the system from triggering."
-
-situation: "A situation refers to a specific state of the market in which a certain event should take place, as defined by any number of conditions."
-
-condition: "Conditions are rules within a situation. When all conditions under a situation validate true, then the situation gets validated as well, and the associated event is triggered."
-
-trigger-off_event: "The trigger-off event defines the situation in which the corresponding strategy shall be triggered-off. A strategy that is triggered-off releases the capital in reserve and makes it available to other strategies in the trading system."
-
-take_position_event: "The take position event defines the situation that needs to be met to enter a trade."
-
-open_stage: "The open stage deals with all the parameters that define a trade, including position rate and size as well as initial stop and take profit targets."
-
-initial_definition: "The initial definition node groups the parameters that define the trade at the moment the position is taken."
-
-initial_stop: "The initial stop defines the initial target to stop a loss before the trade gets to be managed."
-
-phase_0: "Phase 0 represents the starting point for a stop or take profit target, which may be managed in subsequent phases, on the manage stage."
-
-formula: "A formula is a mathematical expression intended to determine a numerical value to be applied dynamically to a certain property."
-
-next_phase_event: "The next-phase event describes a market situation upon which the management of the trade should shift from one phase to the next."
-
-initial_take_profit: "The initial take profit defines the initial target to take profit before the trade gets to be managed."
-
-position_size: "The size of the position is the amount of capital that will go in the trade, denominated in the quoted asset. The position size node allows setting a size for the position using a formula."
-
-position_rate: "The position rate is the rate at which the position is taken, denominated in the quoted asset. The position rate node allows setting the desired position rate with a formula."
-
-open_execution: "Open execution is the node that will eventually hold the information regarding the execution of the trade opening orders."
-
-manage_stage: "The manage stage is the third stage in the definition of a strategy and deals with the management of stop and take-profit targets."
-
-stop: "The stop node in the manage stage groups all phases managing stop loss targets as the trade develops."
-
-phase_1: "Phase 1 is the first phase in the management of a stop or take-profit target. The management of targets may have as many phases as required."
-
-take_profit: "Take profit node in the manage stage groups all phases managing take profit targets as the trade develops."
-
-close_stage: "Close stage is not developed yet. In the future, it will deal with the execution of the closing orders, trading log, and related matters."
-
-close_execution: "Close execution is the node that will eventually hold the information regarding the execution of the closing orders."
-
-event: "An event is an action triggered by predefined market situations."
-
-javascript_code: "The JavaScript code node may hold any snippet of valid JavaScript."
\ No newline at end of file
diff --git a/docs/_includes/archive.html b/docs/_includes/archive.html
deleted file mode 100644
index 275850c9c..000000000
--- a/docs/_includes/archive.html
+++ /dev/null
@@ -1,15 +0,0 @@
----
-layout: default
-type: archive
----
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Think of the charting space as a huge drawing board. You may have lots of information plotted on different parts of the space and use a viewport to look into that space.
-
-There is only one charting space hierarchy, thus all charts are configured here. As is common throughout the system, different concepts and elements of the charts such as scales, data layers and so on, are represented by nodes in the hierarchy. The system allows great flexibility on how to visualize information over the charts by adding, configuring, and arranging these nodes.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.charts != "" %}
-
-{{include.charts}} Controlling the {{title}} from the Charts
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/charting_space/dashboard.md b/docs/_includes/charting_space/dashboard.md
deleted file mode 100644
index 9f1faac87..000000000
--- a/docs/_includes/charting_space/dashboard.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Dashboard" %}
-{% assign definition = site.data.charting_space.dashboard %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The concept of the dashboard allows having multiple charts configured all at once, so that you may consult different exchanges, different markets, different time frames, or different technical studies on demand, simply by moving around and zooming in or out. You may put charts side by side, or even superimpose them to study market flows, search for arbitrage opportunities, or simply keep them in sight when you analyze particular market situations.
-
-At the moment, the functionality of a dashboard is trivial: grouping time machines. However, in the future, it will offer various features to enhance the user experience.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a dashboard, select *Add Dashboard* on the Charting Space node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.charts != "" %}
-
-{{include.charts}} Controlling the {{title}} from the Charts
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/charting_space/layer.md b/docs/_includes/charting_space/layer.md
deleted file mode 100644
index 4c04b69c1..000000000
--- a/docs/_includes/charting_space/layer.md
+++ /dev/null
@@ -1,118 +0,0 @@
-
-
-{% assign title = "Layer" %}
-{% assign definition = site.data.charting_space.layer %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-To set up a layer, you need to establish a reference with the data product of your choice.
-
-
-
-{% endif %}
-
-{% if include.charts != "" %}
-
-{{include.charts}} Controlling the {{title}} from the Charts
-
-
-
-To turn layers on and off, simply click on the layer in the corresponding products panel.
-
-To turn on and off a layer panel, click the panel button on the bottom-left corner of the layer.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a layer, select *Add Layer* on the layer manager node menu.
-
-{% include note.html content="After adding a layer node, make sure you establish a reference to the corresponding data product in the data storage node of the network hierarchy." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Layer* on the menu to access the configuration.
-
-```json
-{
- "status":"on",
- "showPanels":true
-}
-```
-
-* ```status``` may be *on* or *off* and refers to the layer being visible or not on the charts.
-
-* ```showPanels``` may be *true* or *false*; *true* shows the plotter panel that may be associated with the data product as per the plotter module definitions; *false* makes panels invisible.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/charting_space/layers-manager.md b/docs/_includes/charting_space/layers-manager.md
deleted file mode 100644
index e1b695fa7..000000000
--- a/docs/_includes/charting_space/layers-manager.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "Layers Manager" %}
-{% assign definition = site.data.charting_space.layers_manager %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-In other words, you use the layers manager node to configure which data products you wish to be made available for visualization purposes on the charts, in particular, on a specific timeline chart to which the layers manager node is attached to.
-
-
-
-{% endif %}
-
-{% if include.charts != "" %}
-
-{{include.charts}} Controlling the {{title}} from the Charts
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a layers manager, select *Add Layers Manager* on the preferred timeline chart node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/charting_space/rate-scale.md b/docs/_includes/charting_space/rate-scale.md
deleted file mode 100644
index b6583a2c8..000000000
--- a/docs/_includes/charting_space/rate-scale.md
+++ /dev/null
@@ -1,173 +0,0 @@
-
-
-{% assign title = "Rate Scale" %}
-{% assign definition = site.data.charting_space.rate_scale %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Rate scales may exist both at the level of a time machine and at the level of a timeline chart, each affecting the corresponding concept.
-
-When set at the level of the time machine, the scale settings affect all charts within the time machine. When set at the level of the timeline chart, the settings override the rate scale at the time machine level. This allows having multiple charts on the same time machine, each with a different rate scale.
-
-{% if include.heading == "more" %}##{% else %}{{include.heading}}{% endif %}### Scale Minimum and Maximum Values
-
-A rate scale has a minimum and a maximum value. The minimum value is the value at bottom of the chart. The maximum, is the value at the top of the chart.
-
-In technical terms, the minimum and maximum scale values are constantly changing as, whenever you pan across the charts, you are directly affecting the minimum and maximum scale values. That said, the actual scale may change dynamically or not, depending on the scale-automation settings.
-
-{% if include.heading == "more" %}##{% else %}{{include.heading}}{% endif %}### Automatic Scale
-
-The system features an automatic adjustment of the scale, which is turned on by default in our shared workspaces. The scale may be automatic in its minimum value, in its maximum value, or both.
-
-When the scale is automatic in the minimum value, the scale is adjusted so that no piece of information in the span of the chart ever remains below the bottom of the chart. As a result, the lowest data point aligns with the bottom of the chart.
-
-When the scale is automatic in the maximum value, the scale is adjusted so that no piece of information in the span of the chart ever remains above the top of the chart. As a result, the highest data point aligns with the top of the chart.
-
-The scale may be automated on either, or both minimum and maximum values at the same time. In the later case, no data point in the span of the chart ever remains out of the visible area of the chart, as the lowest data point aligns with the bottom of the chart and the highest aligns with the top.
-
-{% if include.heading == "more" %}##{% else %}{{include.heading}}{% endif %}### Manual Scale
-
-The system also features a manual mode. When in manual mode the scale does not change, even if the minimum and maximum values change while panning across a chart. This design feature allows comparing different periods using the same scale, which may be valuable in many cases.
-
-{% if include.heading == "more" %}##{% else %}{{include.heading}}{% endif %}### Scale Offset
-
-The offset is a feature of the rate scale by which the scale may be shifted upwards or downwards. As a result, charts aligned on the vertical axis—synchronized in datetime by a shared time machine—may be put one above the other. In technical terms, what happens is that the scale is shifted upwards or downwards.
-
-
-
-{% endif %}
-
-{% if include.charts != "" %}
-
-{{include.charts}} Controlling the {{title}} from the Charts
-
-
-
-{{include.charts}}# Automatic Scale
-
-**1. To change the automatic scale settings**, place the mouse pointer over the corresponding time machine or timeline chart rate box, press the Shift key and slowly scroll the wheel of the mouse. The action cycles through different possible scale automation settings. Notice a tiny green triangle below and/or above the rate scale icon.
-
-* A triangle pointing up means that the maximum value of the scale is automatic.
-
-* A triangle pointing down means that the minimum value of the scale is automatic.
-
-* Both triangles present at the same time means that both minimum and maximum values are automatic.
-
-* No triangle means that both minimum and maximum values are in manual mode.
-
-{{include.charts}}# Manual Scale
-
-**2. To adjust the scale**, make sure either or both minimum and maximum values are in manual mode. Place the mouse pointer over the corresponding time machine or timeline chart rate box and scroll the wheel of the mouse. The scale will increase or decrease accordingly, depending on which values are set to manual.
-
-Notice that, while changing the scale, a number is displayed replacing the actual rate. This is a reference value of the scale, that may serve for comparison purposes, with scales in other charts.
-
-{% include note.html content="This action has no effect when both minimum and maximum values are set to automatic mode." %}
-
-{{include.charts}}# Scale Offset
-
-**3. To shift or offset a timeline chart on the vertical axis**, place the mouse pointer on the rate box, left-click and drag upwards or downwards, as desired. The timeline chart will shift in the specified direction while the remaining charts stay in the same position.
-
-{% include note.html content="Setting an offset in a timeline chart only makes sense in the context of a time machine with multiple charts. That is, if you are browsing a single chart, an offset behaves the same as moving the single chart up or down." %}
-
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a rate scale, select *Add Rate Scale* on the time machine or the timeline chart node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Rate Scale* on the menu to access the configuration.
-
-```json
-{
- "minValue": 388.60416666666424,
- "maxValue": 9715.104166666664,
- "autoMinScale": true,
- "autoMaxScale": true
-}
-```
-
-* ```minValue``` is a numerical value that represents the value of the scale at the bottom of the chart.
-
-* ```maxValue``` is a numerical value that represents the value of the scale at the top of the chart.
-
-* ```autoMinScale``` sets the mode of the scale for the minimum value; ```true``` sets the value to automatic, ```false``` sets the value to manual.
-
-* ```autoMaxScale``` sets the mode of the scale for the maximum value; ```true``` sets the value to automatic, ```false``` sets the value to manual.
-
-{% include note.html content="The ```minValue``` and ```maxValue``` may be entered via the design space and the charts. Both input methods are synchronized and the resulting values are stored in the node." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/charting_space/time-frame-scale.md b/docs/_includes/charting_space/time-frame-scale.md
deleted file mode 100644
index 6bc5e6034..000000000
--- a/docs/_includes/charting_space/time-frame-scale.md
+++ /dev/null
@@ -1,117 +0,0 @@
-
-
-{% assign title = "Time Frame Scale" %}
-{% assign definition = site.data.charting_space.time_frame_scale %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-When the time frame scale is set at the level of the time machine, the scale setting affects all charts within the time machine. When set at the level of the timeline chart, the setting overrides the time frame scale at the time machine level. This allows comparing charts in different time frames, but still synchronized at the datetime level.
-
-
-
-{% endif %}
-
-{% if include.charts != "" %}
-
-{{include.charts}} Controlling the {{title}} from the Charts
-
-
-
-**1. To set a time frame value**, place the mouse pointer over the corresponding time machine or timeline chart time frame box and scroll the mouse wheel.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a time frame scale, select *Add Time Frame Scale* on the time machine or the timeline chart node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Frame Scale* on the menu to access the configuration.
-
-```json
-{
- "value":"06-hs"
-}
-```
-
-* ```value``` can be any of the time frames supported by the system:
-
- * ```01-min```, ```02-min```, ```03-min```, ```04-min```, ```05-min```, ```10-min```, ```15-min```, ```20-min```, ```30-min```, ```40-min```, and ```45-min```.
-
- * ```01-hs```, ```02-hs```, ```03-hs```, ```04-hs```, ```06-hs```, ```08-hs```, ```12-hs```, and ```24-hs```.
-
- {% include note.html content="The values entered via the design space and the charts are synchronized and stored in the node." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/charting_space/time-machine.md b/docs/_includes/charting_space/time-machine.md
deleted file mode 100644
index b0860adaf..000000000
--- a/docs/_includes/charting_space/time-machine.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Time Machine" %}
-{% assign definition = site.data.charting_space.time_machine %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Think of a time machine as an aide that helps you keep any number of pieces of information synchronized on the same time scale. Every data structure that you set up within the same time machine, will always be synchronized in time. Put in other words, the open and closing datetime of each dataset will always be aligned on the vertical axis.
-
-On the other hand, when you arrange charts on different time machines, they are completely independent of one another.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a time machine, select *Add Time Machine* on the Dashboard node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.charts != "" %}
-
-{{include.charts}} Controlling the {{title}} from the Charts
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/charting_space/time-scale.md b/docs/_includes/charting_space/time-scale.md
deleted file mode 100644
index 3d382116a..000000000
--- a/docs/_includes/charting_space/time-scale.md
+++ /dev/null
@@ -1,160 +0,0 @@
-
-
-{% assign title = "Time Scale" %}
-{% assign definition = site.data.charting_space.time_scale %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-{% if include.heading == "more" %}##{% else %}{{include.heading}}{% endif %}### Scale Minimum and Maximum Values
-
-A time scale has a minimum and a maximum value. The minimum value is the value at the left border of the chart. The maximum, is the value at the right border of the chart.
-
-In technical terms, the minimum and maximum scale values are constantly changing as, whenever you pan across the charts, you are directly affecting the minimum and maximum scale values. That said, the actual scale doesn't change when panning across a chart.
-
-{% if include.heading == "more" %}##{% else %}{{include.heading}}{% endif %}### Automatic Scale
-
-The system features an automatic adjustment of the scale, which is turned on by default in our shared workspaces. The scale may be automatic in its minimum value, in its maximum value, or both.
-
-When the scale is automatic in the minimum value, the scale is adjusted so that the chart shows all data from the beginning of the market. Panning the charts under such setting has the effect of compressing and decompressing the data against the left border of the chart.
-
-When the scale is automatic in the maximum value, the scale is adjusted so that the chart shows all data until the end of the market. In such case, panning the charts has the effect of compressing and decompressing the data against the right border of the chart.
-
-When the scale is automatic in both the minimum and maximum value, the scale is adjusted so that the chart shows the whole market. In such case, when you click and drag to pan the charts, the settings turns back to manual on both ends of the chart.
-
-{% include note.html content="Having the time scale set to automatic by default helps finding the data as soon as it starts being processed the first time you run the Masters bot instances." %}
-
-{% if include.heading == "more" %}##{% else %}{{include.heading}}{% endif %}### Manual Scale
-
-The scale features a manual mode. When in manual mode the scale does not change, even if the minimum and maximum values change while panning through a chart. This is the natural state of the time scale.
-
-
-
-{% endif %}
-
-{% if include.charts != "" %}
-
-{{include.charts}} Controlling the {{title}} from the Charts
-
-
-
-{{include.charts}}# Automatic Scale
-
-**1. To change the automatic scale settings**, place the mouse pointer over the corresponding time box, press the Shift key and slowly scroll the wheel of the mouse. The action cycles through different possible scale automation settings. Notice a tiny green triangle below and/or above the rate scale icon.
-
-* A triangle pointing right means that the maximum value of the scale is automatic.
-
-* A triangle pointing left means that the minimum value of the scale is automatic.
-
-* Both triangles present at the same time means that both minimum and maximum values are automatic.
-
-* No triangle means that both minimum and maximum values are in manual mode.
-
-{{include.charts}}# Manual Scale
-
-**2. To adjust the scale**, make sure either or both minimum and maximum values are in manual mode. Place the mouse pointer over the time box and scroll the wheel of the mouse. The scale will increase or decrease accordingly, depending on which values are set to manual.
-
-Notice that, while changing the scale, a number is displayed replacing the actual datetime. This is a reference value of the scale, that may serve for comparison purposes, with scales in other charts.
-
-{% include note.html content="This action has no effect when both minimum and maximum values are set to automatic mode." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a time scale, select *Add Time Scale* on the time machine node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Rate Scale* on the menu to access the configuration.
-
-```json
-{
- "fromDate": "2019-05-02T20:07:50.872Z",
- "toDate": "2019-05-22T20:28:21.515Z",
- "autoMinScale": false,
- "autoMaxScale": false
-}
-```
-
-* ```minValue``` is a date in the Epoch time format that represents the value of the scale at the left border of the chart.
-
-* ```maxValue``` is a date in the Epoch time format that represents the value of the scale at the right border of the chart.
-
-* ```autoMinScale``` sets the mode of the scale for the minimum value; ```true``` sets the value to automatic, ```false``` sets the value to manual.
-
-* ```autoMaxScale``` sets the mode of the scale for the maximum value; ```true``` sets the value to automatic, ```false``` sets the value to manual.
-
-{% include note.html content="The ```minValue``` and ```maxValue``` may be entered via the design space and the charts. Both input methods are synchronized and the resulting values are stored in the node." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/charting_space/timeline-chart.md b/docs/_includes/charting_space/timeline-chart.md
deleted file mode 100644
index 1a1e188ad..000000000
--- a/docs/_includes/charting_space/timeline-chart.md
+++ /dev/null
@@ -1,107 +0,0 @@
-
-
-{% assign title = "Timeline Chart" %}
-{% assign definition = site.data.charting_space.timeline_chart %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-In other words, a timeline chart—often referred simply as *chart*—is a set of information to be displayed over a timeline. The information may include candles—the main and foremost resource—as well as any other indicator, study or—in general—data products that may be available.
-
-You may add as many charts as you wish. Charts within the same time machine are synchronized in the y-axis, that is, in the datetime dimension. Charts in different time machines are independent of each other concerning the datetime. In either case, you may also add rate scales and time frame scales at the timeline charts level.
-
-The information that each timeline chart makes available on the screen is given by the layers set up in the corresponding layers manager.
-
-
-
-{% endif %}
-
-{% if include.charts != "" %}
-
-{{include.charts}} Controlling the {{title}} from the Charts
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a timeline chart, select *Add Timeline Chart* on the preferred time machine node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/charting_space/viewport.md b/docs/_includes/charting_space/viewport.md
deleted file mode 100644
index ae55388e1..000000000
--- a/docs/_includes/charting_space/viewport.md
+++ /dev/null
@@ -1,111 +0,0 @@
-
-
-{% assign title = "Viewport" %}
-{% assign definition = site.data.charting_space.viewport %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The viewport offers an opening into the visual environment in which you may see, analyze and go over every piece of data involved in the process of trading cryptocurrencies:
-
-* Live and historic market data;
-* Data crunched in the form of indicators;
-* The specific effects of the rules you will program into your strategies, and how strategies behave during testing and live trading sessions.
-
-At this point, the system supports one viewport only. In the future, different viewports may give you direct access to different parts of the charting space.
-
-{% include note.html content="The information that is out of focus, that is, out of the viewport, is not read nor rendered graphically, thus, does not consume resources." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.charts != "" %}
-
-{{include.charts}} Controlling the {{title}} from the Charts
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/commento.html b/docs/_includes/commento.html
deleted file mode 100644
index c38386b51..000000000
--- a/docs/_includes/commento.html
+++ /dev/null
@@ -1,5 +0,0 @@
-{% unless page.comments == false %}
-
-
-
-{% endunless %}
diff --git a/docs/_includes/concepts/--------------------------------------------template.md b/docs/_includes/concepts/--------------------------------------------template.md
deleted file mode 100644
index 0fa91ce0f..000000000
--- a/docs/_includes/concepts/--------------------------------------------template.md
+++ /dev/null
@@ -1,77 +0,0 @@
-
-
-{% assign title = "XXXXXXXXXXXXXXXX" %}
-{% assign definition = site.data.concepts.XXXXXXXXXXXXXXXX %}
-{% assign preposition = "XXXXXXXXXXXXXXXX" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-{{include.heading}}## Establishing and Removing References
-
-To establish a reference, right-click on the first node and drag it close to the target node. Grey rings show which nodes you may establish a reference with. In case there are multiple nodes that would accept the reference, the one closer to the node where the reference originates will have its ring highlighted. Releasing the mouse button establishes the reference, or *links* both nodes.
-
-The reference is visually represented by a faint grey dotted line. Such line is visible only when both ends of the reference are visible.
-
-To remove a reference or *delink* two nodes, simply right-click the node where the reference originates and make a dentle swipping motion away from the target node.
-
-[](https://user-images.githubusercontent.com/13994516/71175267-7057ce80-2267-11ea-8e97-4cffaa14b993.gif)
-
-{% include note.html content="Throughout this documentation we may use the verbs *to link*, *to reference* or *to establish a reference* interchangeably, as synonyms." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.extended == "more" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.extended != "no" %}
-
-
-
-{{include.heading}}## Direction
-
-References have a *direction* property relative to each of the nodes involved in the reference: the node establishing the reference sets an *outgoing* reference, while the one accepting the reference sets an *incoming* reference.
-
-For example, a session establishes an outgoing reference with a trading system. This allows the session to access the information within the whole trading system hierarchy, including strategies. At the trading system level, the same reference is viewed as an incoming reference.
-
-[](https://user-images.githubusercontent.com/13994516/70355703-0e649580-1873-11ea-925e-1f0250148d2c.gif)
-
-{{include.heading}}## Scope
-
-A reference established between nodes of any particular structure within a hierarchy is said to be an *internal* reference relative to the said structure of nodes. Similarly, a reference established with a node outside of the said structure, that is, in a different part of the hierarchy or in another hierarchy, is said to be an *external* reference.
-
-Examples of internal references may be found in the data mine and crypto ecosystem hierarchies. For example, let's briefly look into one such case within a plotter module:
-
-The capture below shows the shapes node and several offspring nodes: on one hand, several polygons; on the other hand, the chart points node.
-
-[](https://user-images.githubusercontent.com/13994516/71106204-316e3e00-21bf-11ea-8ba0-df5fe9d0000e.gif)
-
-Notice that vertices under each polygon reference to points under the chart points node.
-
-This means that the node *shapes* feature several internal references.
-
-{% include note.html content="The *backup*, *clone* and *share* operations make different uses of the properties of references. We will cover the three of them extensively so that you may make the most of these features." %}
-
-
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/crypto_ecosystem/asset.md b/docs/_includes/crypto_ecosystem/asset.md
deleted file mode 100644
index 74eb0c31d..000000000
--- a/docs/_includes/crypto_ecosystem/asset.md
+++ /dev/null
@@ -1,113 +0,0 @@
-
-
-{% assign title = "Asset" %}
-{% assign definition = site.data.crypto_ecosystem.asset %}
-{% assign preposition = "an" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a crypto exchange, select *Add Crypto Exchange* on the crypto exchanges node menu. The crypto exchange node is created along with the rest of the basic structure of nodes required to define assets, markets and user accounts.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Crypto Exchange* on the menu to access the configuration.
-
-```json
-{
-"codeName": "Poloniex"
-}
-```
-
-* codeName is the name of the exchange as handled in the code of the system.
-
-{% include note.html content="Consult the list of supported exchanges for the list of possible values for the ```codeName``` field. When a supported exchange is successfully configured, the standard crypto exchange icon is replaced with the logotype of the corresponding exchange." %}
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/crypto_ecosystem/crypto-exchanges.md b/docs/_includes/crypto_ecosystem/crypto-exchanges.md
deleted file mode 100644
index 6ca550fc6..000000000
--- a/docs/_includes/crypto_ecosystem/crypto-exchanges.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Crypto Exchanges" %}
-{% assign definition = site.data.crypto_ecosystem.crypto_exchanges %}
-{% assign preposition = "a" %}
-{% assign plural = "" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add an exchange account key, select *Add Key* on the user keys node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Key* on the menu to access the configuration.
-
-```json
-{
-"codeName": "Paste your exchange API name or label here",
-"secret": "Paste your exchange API secret key here."
-}
-```
-
-* ```codeName``` is the name or label of your key, as supplied by the exchange.
-
-* ```secret``` is the *secret key* as supplied by the exchange.
-
-{% include warning.html content="To keep your exchange keys safe, never share data structures you may download from the system, as downloads contain all information in the data structure, including personal information such as exchange keys. Use the share option on the menu instead. The share option strips sensitive information and outputs a file that is safe for sharing." %}
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/crypto_ecosystem/exchange-accounts.md b/docs/_includes/crypto_ecosystem/exchange-accounts.md
deleted file mode 100644
index 4e59004eb..000000000
--- a/docs/_includes/crypto_ecosystem/exchange-accounts.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Exchange Accounts" %}
-{% assign definition = site.data.crypto_ecosystem.exchange_accounts %}
-{% assign preposition = "an" %}
-{% assign plural = "" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-{% include important.html content="Only markets that are effectively listed on the exchange may be configured and used with the system. Check with the exchange and make sure you understand what tickers they are using, which is the base asset and which the quoted asset on the listed markets." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a market, select *Add Market* on the crypto exchange node menu. The market node is created along with the basic structure of nodes used to define the market.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/crypto_ecosystem/user-account.md b/docs/_includes/crypto_ecosystem/user-account.md
deleted file mode 100644
index ec69fe46d..000000000
--- a/docs/_includes/crypto_ecosystem/user-account.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "User Account" %}
-{% assign definition = site.data.crypto_ecosystem.user_account %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a user account, select *Add User Account* on the exchange accounts node menu. The user account node is created along with the basic structure of nodes used to define keys and user assets with the exchange.
-
-{% include tip.html content="You may add and administer as many user accounts as you wish." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/crypto_ecosystem/user-assets.md b/docs/_includes/crypto_ecosystem/user-assets.md
deleted file mode 100644
index ed58d5052..000000000
--- a/docs/_includes/crypto_ecosystem/user-assets.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "User Assets" %}
-{% assign definition = site.data.crypto_ecosystem.user_assets %}
-{% assign preposition = "a" %}
-{% assign plural = "" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add user keys node, select *Add User Keys* on the user account node menu. The user keys node is created along with the first exchange account key.
-
-{% include note.html content="Only one user keys node may exist under a user account." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/custom/getting_started_series.html b/docs/_includes/custom/getting_started_series.html
deleted file mode 100644
index 5b573a9d0..000000000
--- a/docs/_includes/custom/getting_started_series.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
-
- {% assign pages = site.pages | sort:"weight" %}
- {% for p in pages %}
- {% if p.series == "Getting Started" %}
- {% if p.url == page.url %}
-
If you run into any of these setup issues, you must solve them before you can continue on.
-
-
-
-
-
-
- →
-
-
-
-
-
-
-
-
-
-
Build your widgets
-
-
-
In this step, you will build the widgets for your system. The widgets form the various components that blah blah blah this is dummy text power the nuclear capabilities of your energy transformer into deep space using wormhole technology and warp drive speeds.
-
-
In order to configure your widgets, you will need to follow these topics:
After you've configured all the necessary components to build your space transformer, you need to publish your app. Of course this content is also just dummy text. Pay no particular attention to the content but rather the format and placement of the map.
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Bots store data in the minimized array format as a strategy to build the lightest possible datasets. For the same reason, a bot may choose not to store easily calculable information.
-
-For example, imagine an indicator that stores buy and sell volumes... does it *need* to store the total volume? Given that it is so easy to calculate, the answer is *probably* no. IT is up to the developer to decide, but it is certainly not required.
-
-{% include note.html content="It may not be worthy to store information that can be easily calculated at a later stage." %}
-
-The calculations procedure calculates the properties that the developer chose not to store in the dataset.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a calculations procedure, select *Add Missing Items* on the product definition node menu. Items that may be missing are created along with the basic structure of nodes required to define them.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/chart-points.md b/docs/_includes/data_mine/chart-points.md
deleted file mode 100644
index a2c2c5880..000000000
--- a/docs/_includes/data_mine/chart-points.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "Chart Points" %}
-{% assign definition = site.data.data_mine.chart_points %}
-{% assign preposition = "a" %}
-{% assign plural = "" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-This procedure holds the core logic of the bot, as it features the code that performs the calculations required to produce the new data set. The code is split between a procedure initialization and a procedure loop.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a data buildings procedure, select *Add Missing Items* on the product definition node menu. Items that may be missing are created along with the basic structure of nodes required to define them.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/data-dependency.md b/docs/_includes/data_mine/data-dependency.md
deleted file mode 100644
index 2a9b551ec..000000000
--- a/docs/_includes/data_mine/data-dependency.md
+++ /dev/null
@@ -1,109 +0,0 @@
-
-
-{% assign title = "Data Dependency" %}
-{% assign definition = site.data.data_mine.data_dependency %}
-{% assign preposition = "a" %}
-{% assign plural = "" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about data dependencies
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Most bots consume data other bots have produced. Because bots need the data as input for their calculations, processes establish a data dependency with the dataset definitions of other bots. The reference provides the process with all the information needed to decode the dataset, enabling it to perform the required calculations.
-
-[](https://user-images.githubusercontent.com/13994516/68993034-7840df00-0873-11ea-804d-d24e88ce25f7.gif)
-
-The image above shows data dependencies in one bot referencing dataset definitions of another bot.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about data dependencies
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a data dependency, select *Add Data Dependency* on the process dependencies node menu.
-
-{% include tip.html content="Remember that a data dependency must establish a reference to the appropriate dataset definition." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/data-formula.md b/docs/_includes/data_mine/data-formula.md
deleted file mode 100644
index 5780f61bb..000000000
--- a/docs/_includes/data_mine/data-formula.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "Data Formula" %}
-{% assign definition = site.data.data_mine.data_formula %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-In a way, data mines are catalogs of bots that anyone may create. This hierarchy provides all the tools required to create sensors, indicators, and plotters, with minimal coding required.
-
-Because the hierarchy provides definitions, it does not intervene in the execution of bots. Instead, the definitions in data mines are instantiated from the network hierarchy by bot instances. Bot instances and process instances are the ones running the code according to the definitions in the corresponding data mine.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a data mine, select *Add Data Mine* on the workspace node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Data Mine* on the menu to access the configuration.
-
-```json
-{
-"codeName": "Supermine"
-}
-```
-
-* ```codeName``` is the name of the data mine as used within the code of the system.
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/dataset-definition.md b/docs/_includes/data_mine/dataset-definition.md
deleted file mode 100644
index 2dbea5402..000000000
--- a/docs/_includes/data_mine/dataset-definition.md
+++ /dev/null
@@ -1,142 +0,0 @@
-
-
-{% assign title = "Dataset Definition" %}
-{% assign definition = site.data.data_mine.dataset_definition %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-A good part of what makes datasets easy to consume by other bots is the fact that they are standardized in terms of their structure. It is that structure that is specified in the dataset definitions.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a dataset definition, select *Add Dataset Definition* on the bot's node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Definition* on the menu to access the configuration.
-
-**Multi-Period-Market:**
-
-```json
-{
- "codeName": "Multi-Period-Market",
- "type": "Market Files",
- "validTimeFrames": [ "24-hs", "12-hs", "08-hs", "06-hs", "04-hs", "03-hs", "02-hs", "01-hs" ],
- "filePath": "Data-Mine-Name/Bot-Name/@Exchange/Output/Product-Name/Multi-Period-Market/@Period",
- "fileName": "@BaseAsset_@QuotedAsset.json"
-}
-```
-
-**Multi-Period-Daily:**
-
-```json
-{
- "codeName": "Multi-Period-Daily",
- "type": "Daily Files",
- "validTimeFrames": [ "45-min", "40-min", "30-min", "20-min", "15-min", "10-min", "05-min", "04-min", "03-min", "02-min", "01-min" ],
- "filePath": "Data-Mine-Name/Bot-Name/@Exchange/Output/Product-Name/Multi-Period-Daily/@Period/@Year/@Month/@Day",
- "fileName": "@BaseAsset_@QuotedAsset.json",
- "dataRange": {
- "filePath": "Data-Mine-Name/Bot-Name/@Exchange/Output/Product-Name/Multi-Period-Daily",
- "fileName": "Data.Range.@BaseAsset_@QuotedAsset.json"
- }
-}
-```
-
-
-* ```codeName``` is the name of the dataset as used within the code.
-
-* ```type``` refers to the type of dataset; possible values are ```Market Files``` and ```Daily Files```.
-
-* ```validPeriods``` refers to the time frames handled by the dataset.
-
-* ```filePath``` sets the path on which files are stored; the proper name of the data mine, the bot and the product need to be entered.
-
-* ```fileName``` sets the name of the files that constitute the dataset.
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/execution-finished-event.md b/docs/_includes/data_mine/execution-finished-event.md
deleted file mode 100644
index 9e31263e2..000000000
--- a/docs/_includes/data_mine/execution-finished-event.md
+++ /dev/null
@@ -1,107 +0,0 @@
-
-
-{% assign title = "Execution Finished Event" %}
-{% assign definition = site.data.data_mine.execution_finished_event %}
-{% assign preposition = "an" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The execution finished event is responsible for triggering the execution of every process that depends on the data a bot produces. If bot Alice depends on bot Bob, Alice listens to the execution finished event of Bob so that it may start a new execution cycle as soon as Bob finishes its cycle. Alice listens to Bob's execution finished event by establishing a reference from its execution started event.
-
-[](https://user-images.githubusercontent.com/13994516/68993254-39605880-0876-11ea-9ee7-9f49976bd2dc.gif)
-
-The image above shows a reference established from the execution started event of a process to the execution finished event of another process.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add an execution finished event, select *Add Missing Items* on the process definition node menu. Items that may be missing are created along with the basic structure of nodes required to define them.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/execution-started-event.md b/docs/_includes/data_mine/execution-started-event.md
deleted file mode 100644
index e89a1ae12..000000000
--- a/docs/_includes/data_mine/execution-started-event.md
+++ /dev/null
@@ -1,107 +0,0 @@
-
-
-{% assign title = "Execution Started Event" %}
-{% assign definition = site.data.data_mine.execution_started_event %}
-{% assign preposition = "an" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-These references determine when a process is due for another run. By listening to the execution finished event of the process it depends on, it may wake up just in time to process the new batch of data the dependency has just delivered.
-
-Bots form a sort of multi-branched execution sequence with an indeterminate number of dependencies. Every time the bot further down the tree of dependencies finishes a cycle, it triggers the execution of multiple bots listening to its execution finished event.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add an execution started event, select *Add Missing Items* on the process definition node menu. Items that may be missing are created along with the basic structure of nodes required to define them.
-
-{% include tip.html content="Remember that an execution started event must establish a reference to the appropriate execution finished event." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/formula.md b/docs/_includes/data_mine/formula.md
deleted file mode 100644
index d7a6c526c..000000000
--- a/docs/_includes/data_mine/formula.md
+++ /dev/null
@@ -1,107 +0,0 @@
-
-
-{% assign title = "Formula" %}
-{% assign definition = site.data.data_mine.formula %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-A formula may act in slightly different ways depending on the ```isCaculated``` attribute in the record property configuration:
-
-* When a property is calculated (```"isCalculated": true```), the formula assigns to the property a value that is calculated in the calculations procedure. Even if the property is not stored in the dataset, it is made available as a *calculated property* to other bots that may have the dataset as input.
-
-* When a property is not calculated (```"isCalculated": false``` or the attribute is not defined in the configuration) the formula is applied in the data building procedure.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a formula, select *Add Formula* on the record property menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/indicator-bot.md b/docs/_includes/data_mine/indicator-bot.md
deleted file mode 100644
index 785825cdf..000000000
--- a/docs/_includes/data_mine/indicator-bot.md
+++ /dev/null
@@ -1,112 +0,0 @@
-
-
-{% assign title = "Indicator Bot" %}
-{% assign definition = site.data.data_mine.indicator_bot %}
-{% assign preposition = "an" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The indicator bot node holds all definitions required for an indicator bot to function. Definitions are split between the definition of processes and products. Processes are algorithms that go through an input dataset, perform certain calculations, and produce an output. Part of that output is the data products the bot creates.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add an indicator bot, select *Add Indicator Bot* on the data mine node menu. An indicator bot is created along with the basic structure of nodes required to define it.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Bot* on the menu to access the configuration.
-
-```json
-{
-"codeName": "Super",
-"repo": "Super-Indicator-Bot"
-}
-```
-
-* ```codeName``` is the name of the bot as used within the code of the system.
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/javascript-code.md b/docs/_includes/data_mine/javascript-code.md
deleted file mode 100644
index 37e5117e0..000000000
--- a/docs/_includes/data_mine/javascript-code.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "JavaScript Code" %}
-{% assign definition = site.data.data_mine.javascript_code %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-There are other effects of establishing a reference from the output dataset to a product dataset definition. Upon execution, every time a process finishes a processing cycle, it triggers an event that may be consumed by other entities. This event indicates that the datasets impacted by the process have been updated.
-
-An example of other entities that may be listening to such events is that of plotters. Plotters read datasets and create graphical representations of this data over the charts. Charts are constantly updating the information in the form of candles and indicators in realtime, synchronized with the data being extracted from the exchange by the sensor bot. That kind of automatism is possible thanks to the events that processes trigger every time an execution cycle is finished, signaling to everyone listening that new data is available on each of the impacted datasets.
-
-[](https://user-images.githubusercontent.com/13994516/68976798-f01cf400-07f6-11ea-9ffb-198b5853a220.gif)
-
-The image above shows the typical references from output datasets to datasets definitions.
-
-{% include note.html content="An output dataset must reference a dataset definition." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add an output dataset, select *Add Output Dataset* on the process output node menu.
-
-{% include tip.html content="Remember that an output dataset must reference a valid dataset definition after creating the output dataset." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/panel-data.md b/docs/_includes/data_mine/panel-data.md
deleted file mode 100644
index c6b58d379..000000000
--- a/docs/_includes/data_mine/panel-data.md
+++ /dev/null
@@ -1,124 +0,0 @@
-
-
-{% assign title = "Panel Data" %}
-{% assign definition = site.data.data_mine.panel_data %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The system renders a panel featuring a centered, single-column vertical arrangement of data, with a label and a data field right below it. The label of each data field on the panel is given—by default—by the label set for each panel data node.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a panel data node, select *Add Panel Data* on the plotter panel menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Panel Data* on the menu to access the configuration.
-
-```json
-{
- "valueDecimals": 2
-}
-```
-
-* ```valueDecimals``` sets the number of decimals to be shown on the corresponding data field.
-
-To override the default manner in which the data is assembled on the panel, the following properties may be included and defined:
-
-```json
-{
- "labelText": "The Label",
- "labelPosition": 15,
- "valuePosition": 20,
- "valueDecimals": 2
-}
-```
-
-* ```labelPosition``` and ```valuePosition``` represent the vertical distance of the corresponding fields to the top margin of the panel.
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/plotter-module.md b/docs/_includes/data_mine/plotter-module.md
deleted file mode 100644
index e2bbf7582..000000000
--- a/docs/_includes/data_mine/plotter-module.md
+++ /dev/null
@@ -1,141 +0,0 @@
-
-
-{% assign title = "Plotter Module" %}
-{% assign definition = site.data.data_mine.plotter_module %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-A single plotter may have several modules. Different modules may be used to plot each product of the bot, or as best suits the expected use-pattern.
-
-[](https://user-images.githubusercontent.com/13994516/71016077-eab41180-20f4-11ea-87e7-7262ff10a1ab.gif)
-
-{% include important.html content="For a bot to use a plotter, the corresponding product definition must establish a reference with the plotter module built to interpret the dataset." %}
-
-[](https://user-images.githubusercontent.com/13994516/71016079-eab41180-20f4-11ea-8afb-96321f9c68d8.gif)
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a plotter module, select *Add Plotter Module* on the plotter node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Plotter Module* on the menu to access the configuration.
-
-```json
-{
- "codeName": "Module Name",
- "isLegacy": true,
- "icon": "histogram"
-}
-```
-
-* ```codeName``` is the name used in the code to refer to the module.
-
-* ```isLegacy``` is ```true``` for plotters modules developed entirely in JavaScript, and is ```false``` or doesn't show in the configuration for plotters built with the tools featured in the data mine hierarchy.
-
-* ```icon``` is the name of the image that illustrates the corresponding layer in the Layers Panel. In case the banner is not specified, the *default banner* is used. Current possible values are:
-
-
-| Value | Image|
-| :---: | :---: |
-| ```default``` |  |
-| ```histogram``` |  |
-| ```band``` |  |
-| ```moving-average``` |  |
-| ```oscillator``` |  |
-| ```trend``` |  |
-
-Custom images may be added too. To do that:
-
-1. name the image in the following format: ```image-name.png```;
-
-1. place images in the ```WebServer\Images\Icons``` folder;
-
-1. in the configuration of the module, use the name as is (e.g.: ```"icon": "image-name"```)
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/plotter-panel.md b/docs/_includes/data_mine/plotter-panel.md
deleted file mode 100644
index 5b6450036..000000000
--- a/docs/_includes/data_mine/plotter-panel.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "Plotter Panel" %}
-{% assign definition = site.data.data_mine.plotter_panel %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Beyond the graphic representation of data over the charts, plotters may also feature a *data panel*, that is, a numerical representation of the data showing the exact figures corresponding to the column or period that is in focus (the point of the charts where the mouse pointer is at any point).
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a plotter panel, select *Add Plotter Panel* on the plotter module node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/plotter.md b/docs/_includes/data_mine/plotter.md
deleted file mode 100644
index d6ebe3092..000000000
--- a/docs/_includes/data_mine/plotter.md
+++ /dev/null
@@ -1,113 +0,0 @@
-
-
-{% assign title = "Plotter" %}
-{% assign definition = site.data.data_mine.plotter %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Plotters usually have a one-to-one relationship with bots, as they are often created as a customized solution. However, in practice, there is no constraint to creating any number of plotters for a single bot or a single plotter for multiple bots.
-
-The overall workflow of a plotter, while reading a dataset, consists in:
-
-* Applying a set of rules to identify certain data points;
-
-* Use those points to form lines and polygons;
-
-* Apply graphical styles to those lines and polygons.
-
-Those actions are performed recursively for each record, and the graphics are plotted on the charts in real-time as data is processed.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a plotter, select *Add Plotter* on the data mine node menu. An indicator bot is created along with the basic structure of nodes required to define it.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/point-formula.md b/docs/_includes/data_mine/point-formula.md
deleted file mode 100644
index 2faa0fbeb..000000000
--- a/docs/_includes/data_mine/point-formula.md
+++ /dev/null
@@ -1,171 +0,0 @@
-
-
-{% assign title = "Point Formula" %}
-{% assign definition = site.data.data_mine.point_formula %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-To represent some form of variation of the price or a price derivative over time, a typical point formula consists of the following two coordinates: ```x = datetime``` and ```y = rate```.
-
-For example:
-
-**Point *SMA 20 Begin***
-```js
-x = record.begin
-y = record.previous.sma20
-```
-
-The example above shows the definition of the first of two points necessary to draw the segment of the 20-periods SMA curve for any particular period or candle. In this case, ```x = record.begin``` is the starting datetime of the period and ```y = record.previous.sma20``` is the rate of the 20-periods SMA of the previous period.
-
-{% include note.html content="The above variables are constructed with information originating at the product definition that references the corresponding plotter module." %}
-
-To complete the line segment corresponding to a single period, the closing datetime of the period and the closing rate for the 20-periods SMA are required:
-
-**Point *SMA 20 End***
-```js
-x = record.end
-y = record.sma20
-```
-
-The above system works very well for plotting all sorts of information over the candles, on the charts.
-
-An oscillator like RSI too needs the definition of the starting and ending datetime of the period as the value for the *x-axis*. However, the value for *axis y* fits a different scale.
-
-Anyway, the points definition is just as straight forward, for example:
-
-**Point *RSI Begin***
-```js
-x = record.begin
-y = record.previous.value
-```
-
-**Point *RSI End***
-```js
-x = record.end
-y = record.value
-```
-
-Points do not necessarily need to refer to values on the dataset produced by the corresponding data product. For example, absolute values for the *y-axis* may be used to describe fixed graphical elements, for instance, a horizontal line, or a box.
-
-**Point *Begin 20***
-```js
-x = record.begin
-y = 20
-```
-
-**Point *End 20***
-```js
-x = record.end
-y = 20
-```
-
-**Point *Begin 30***
-```js
-x = record.begin
-y = 30
-```
-
-**Point *End 30***
-```js
-x = record.end
-y = 30
-```
-
-The above four points are used to paint the background of the 20 to 30 value range of the RSI chart. The first two points are also used to draw the dotted line signaling the 20-value mark, and the last two are used for the dotted line indicating the 30-value mark.
-
-{% include note.html content="The reason from separating the definition of points from the definition of polygons is that any point may be used by one or more polygons." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a point formula, select *Add Point Formula* on the point node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/point.md b/docs/_includes/data_mine/point.md
deleted file mode 100644
index b2314d77f..000000000
--- a/docs/_includes/data_mine/point.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Point" %}
-{% assign definition = site.data.data_mine.point %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-These coordinate points are used to define polygons. Values for ```[x,y]```coordinates are entered with a point formula.
-
-{% include tip.html content="Each point should be given a significant name so that it is easier to identify them at the time of establishing references with polygon vertices." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a point, select *Add Point* on the chart points node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/polygon-body.md b/docs/_includes/data_mine/polygon-body.md
deleted file mode 100644
index c6756c72e..000000000
--- a/docs/_includes/data_mine/polygon-body.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "Polygon Body" %}
-{% assign definition = site.data.data_mine.polygon_body %}
-{% assign preposition = "a" %}
-{% assign plural = "" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Vertices are the main element defining polygons. Once created, each vertex must establish a reference to the corresponding point in the charts point.
-
-[](https://user-images.githubusercontent.com/13994516/71016081-eb4ca800-20f4-11ea-8fee-4d38ecfb0596.gif)
-
-Drawing curves requires two vertices. Painting areas, such as the background of a chart, likely requires four vertices. Note that vertices are not capable of featuring a style. Instead, styles are applied to polygon borders and polygon bodies.
-
-{% include important.html content="Bear in mind that the order in which vertices in a polygon are arranged around the parent polygon node when their *rotational symmetry* property is selected, is the order in which the plotter computes the points. This means that points need to be in the correct order, for example, when drawing a box. Imagine drawing a box on a piece of paper without lifting the pencil... that is how the plotter does it." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a polygon vertex, select *Add Polygon Vertex* on the polygon node menu.
-
-{% include tip.html content="Remember that a vertex must establish a reference to a point in the charts point to be properly defined" %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/polygon.md b/docs/_includes/data_mine/polygon.md
deleted file mode 100644
index e57f1c8e6..000000000
--- a/docs/_includes/data_mine/polygon.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Polygon" %}
-{% assign definition = site.data.data_mine.polygon %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Polygons are defined by two or more vertices, which map points in a charts point. The graphic representation of polygons originates in styles applied to either or both polygon bodies and polygon borders.
-
-{% include note.html content="The order in which polygons are ordered around the parent shapes node determines the order in which they are drawn on the screen. In cases on which polygons intersect, those drawn last are drawn on top of those drawn first." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a polygon, select *Add Polygon* on the shapes node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/procedure-initialization.md b/docs/_includes/data_mine/procedure-initialization.md
deleted file mode 100644
index f627d8f42..000000000
--- a/docs/_includes/data_mine/procedure-initialization.md
+++ /dev/null
@@ -1,108 +0,0 @@
-
-
-{% assign title = "Procedure Initialization" %}
-{% assign definition = site.data.data_mine.procedure_initialization %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-This is an example of a procedure loop code snippet, in particular, the code that calculates the Popular SMAs product of the Simple Moving Average (SMA) indicator.
-
-{% include important.html content="Calculation procedures may only access data up to 48 hours in the past counting from the datetime of the record being processed. For that reason, the calculation of a moving average requires temporarily storing data in an array." %}
-
-```js
-/* Loop Code. */
-
-let candle = record.current // Our main dependencies are candles
-variable.last200.push(candle.close) // Add the current close value to the last 200 array.
-
-if (variable.last200.length > 200) {
- variable.last200.splice(0, 1) // Remove the first element of the array to keep it at a maximun of 200 elements.
-}
-
-variable.sma20 = calculateSMA(20)
-variable.sma50 = calculateSMA(50)
-variable.sma100 = calculateSMA(100)
-variable.sma200 = calculateSMA(200)
-
-function calculateSMA(periods) { // Having a function saves us from duplicating code.
- /* We check we have enough values to make the calculation */
- if (variable.last200.length < periods) { return 0 } // If we dont, we define the value is zero.
-
- let sum = 0 // Initialize sum variable.
- for (let i = variable.last200.length - periods; i < variable.last200.length; i++) { // Iterate through the last periods
- sum = sum + variable.last200[i]
- }
- let sma = sum / periods
- return sma
-}
-```
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a procedure loop, select *Add Procedure loop* on the corresponding procedure node menu. A procedure loop node is created along with the corresponding JavaScript node.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/process-definition.md b/docs/_includes/data_mine/process-definition.md
deleted file mode 100644
index 61980ea1e..000000000
--- a/docs/_includes/data_mine/process-definition.md
+++ /dev/null
@@ -1,191 +0,0 @@
-
-
-{% assign title = "Process Definition" %}
-{% assign definition = site.data.data_mine.process_definition %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-While processes run autonomously, most processes participate in a value-adding chain by which a process produces a data product that other processes may consume as an input to be processed further. This means that bots—while autonomous in their particular jobs—do depend both on other bots and on the data other bots produce.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a process dependencies node, select *Add Missing Items* on the process definition node menu. Items that may be missing are created along with the basic structure of nodes required to define them.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/process-output.md b/docs/_includes/data_mine/process-output.md
deleted file mode 100644
index c223fe644..000000000
--- a/docs/_includes/data_mine/process-output.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "Process Output" %}
-{% assign definition = site.data.data_mine.process_output %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-A bot may feature multiple products, thus, there may be multiple product definitions. Three main aspects need to be defined in terms of products: the characteristics of the dataset, the composition of each record, and the way records are calculated.
-
-{% include note.html content="A product definition usually references a plotter module, which provides a graphic representation of the underlying dataset" %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a product definition, select *Add Product Definition* on the bot's node menu. A product definition is created along with the basic structure of nodes required to make up a product.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Product* on the menu to access the configuration.
-
-```json
-{
- "codeName": "New-Product-Name",
- "singularVariableName": "newProductName",
- "pluralVariableName": "newProductNames"
-}
-```
-
-* ```codeName``` is the name of the product as it is used within the bot's code.
-
-* ```singularVariableName``` is the singular form of the name of the variable representing the product, as is used on strategies (*i.e.:* ```bollingerChannel.direction```, where *bollingerChannel* is the name of the product as defined in its configuration and *direction* is the name of the property.
-
-* ```pluralVariableName``` is the plural form of the variable.
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/record-definition.md b/docs/_includes/data_mine/record-definition.md
deleted file mode 100644
index 57b61a540..000000000
--- a/docs/_includes/data_mine/record-definition.md
+++ /dev/null
@@ -1,111 +0,0 @@
-
-
-{% assign title = "Record Definition" %}
-{% assign definition = site.data.data_mine.record_definition %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Bots store data in the form of arrays of records, in a minimized plain text file and the standard JSON format, although not as objects with named properties, but as arrays.
-
-[](https://user-images.githubusercontent.com/13994516/68998023-303eae00-08ad-11ea-9baa-ddea801c7d6d.png)
-
-The choice of plain text for storage of large volumes of information has benefits in terms of not requiring any sophisticated technology to store and serve the data (*i.e.:* no database is required).
-
-Best practice indicates that there needs to be a balance between the amount of data that is stored and calculations that may be performed at runtime.
-
-Storing objects with named properties in the JSON format would be inappropriate as labels would repeat over and over, creating a ridiculous amount of unnecessary information. However, storing arrays in the JSON standard facilitates the handling of files in the context of JavaScript and Node.JS.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a record definition node, select *Add Record Definition* on the product definition node menu. A record definition node is created along with the first record property.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/record-property.md b/docs/_includes/data_mine/record-property.md
deleted file mode 100644
index 88ddbbe85..000000000
--- a/docs/_includes/data_mine/record-property.md
+++ /dev/null
@@ -1,125 +0,0 @@
-
-
-{% assign title = "Record Property" %}
-{% assign definition = site.data.data_mine.record_property %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about record properties
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Records may have as many properties as required.
-
-{% include important.html content="The order in which record properties are defined around the parent record definition node is the order in which they are stored in the actual record." %}
-
-{% include tip.html content="The first two records are usually the *begin* and *end* records, featuring the corresponding datetimes that indicate when the record starts and ends." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about record properties
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a record property, select *Add Record Property* on the bot's node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Property* on the menu to access the configuration.
-
-```js
-{
- "codeName": "record-name",
- "isString": false,
- "isCalculated": true
-}
-```
-
-* ```codeName``` is the name of the record as it is used in the bot's code.
-
-* ```isString``` determines if the field is a text string or if, in turn, is a numeric field. Dates are stored in the *epoch* format, which is numeric. The reason why this configuration is important is that fields that are strings need to be stored between "double quotes".
-
-* ```isCalculated``` determines if the field is stored in the dataset or if, instead, is calculated at a later stage. A value *true* means that the record is not stored. In the case ```isCaculated``` is not defined in the configuration, it is assumed to be false.
-
-[](https://user-images.githubusercontent.com/13994516/69139160-3ce72000-0ac0-11ea-9566-a259c9ea6194.gif)
-
-The image above shows a record definition with four record properties.
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/sensor-bot.md b/docs/_includes/data_mine/sensor-bot.md
deleted file mode 100644
index b1eaf97c2..000000000
--- a/docs/_includes/data_mine/sensor-bot.md
+++ /dev/null
@@ -1,112 +0,0 @@
-
-
-{% assign title = "Sensor Bot" %}
-{% assign definition = site.data.data_mine.sensor_bot %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The sensor bot node holds all definitions required for a sensor bot to function. Definitions are split between the definition of processes and products. A sensor's processes is an algorithm that obtains data from a third pary and produces an output for other bots to consume. Part of that output is the data products the bot creates.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a sensor bot, select *Add Sensor Bot* on the data mine node menu. A sensor bot is created along with the basic structure of nodes required to define it.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Bot* on the menu to access the configuration.
-
-```json
-{
-"codeName": "Super",
-"repo": "Super-Sensor-Bot"
-}
-```
-
-* ```codeName``` is the name of the bot as used within the code of the system.
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/shapes.md b/docs/_includes/data_mine/shapes.md
deleted file mode 100644
index 4935f9040..000000000
--- a/docs/_includes/data_mine/shapes.md
+++ /dev/null
@@ -1,112 +0,0 @@
-
-
-{% assign title = "Shapes" %}
-{% assign definition = site.data.data_mine.shapes %}
-{% assign preposition = "a" %}
-{% assign plural = "" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-A plotter recursively renders graphics for each period or candle. This means that a definition of what shapes need to be drawn for a single period is required. The plotter does the same thing for every period or candle that is visible on the screen at any point in time, for any time frame, as long as the corresponding data is available.
-
-[](https://user-images.githubusercontent.com/13994516/71016080-eab41180-20f4-11ea-84c6-a514b87d568f.gif)
-
-In general terms, the process of defining what is going to be rendered on the screen consist of the following four steps:
-
- 1. Identifying points defined by ```[x,y]``` coordinates
- 2. Defining polygons
- 3. Defining default styles
- 4. Defining conditional styles
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a shapes node, select *Add Shapes* on the plotter module menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/status-dependency.md b/docs/_includes/data_mine/status-dependency.md
deleted file mode 100644
index 290d4369e..000000000
--- a/docs/_includes/data_mine/status-dependency.md
+++ /dev/null
@@ -1,125 +0,0 @@
-
-
-{% assign title = "Status Dependency" %}
-{% assign definition = site.data.data_mine.status_dependency %}
-{% assign preposition = "a" %}
-{% assign plural = "" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about status dependencies
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The reference is established to acquire the information relative to what the target process is doing. For example, by reading a status report a process may learn when was the last time the referenced process ran, and what was the last file processed.
-
-The status report referenced may belong to the same process— which is called a self-reference. In such a case, the process is learning what it did the last time it ran. Also, the status report referenced may belong to another process—another bot. In that case, the dependency may be of the Market Starting Point or Market Ending Point types.
-
-* **Self Reference** is mandatory, as a process needs to read it's own status report every time it wakes up.
-
-* **Market Starting Point** is a status dependency existing on Multi-Period-Daily processes so that the process establishing the reference learns the datetime of the start of the market. Usually, the reference is established with the sensor's Historic-Trades process status report. Multi-Period-Market processes do not have this type of status dependency as the date of the start of the market is implied in their dataset (a single file with all market data).
-
-* **Market Ending Point** is a status dependency existing both in Multi-Period-Market and Multi-Period-Daily processes so that the process establishing the reference knows the datetime of the end of the market.
-
-[](https://user-images.githubusercontent.com/13994516/68991956-dfa36280-0864-11ea-87ec-f0e4e3b7bf0f.gif)
-
-The image above shows a case of a self-reference status dependency as well as a market ending point status dependency.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about status dependencies
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a status dependency, select *Add Status Dependency* on the process dependencies node menu.
-
-{% include tip.html content="Remember that a status dependency must be configured, and must establish a reference to the appropriate status report." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Status Dependency* on the menu to access the configuration.
-
-```json
-{
-"mainUtility": "Self Reference|Market Starting Point|Market Ending Point"
-}
-```
-
-* ```mainUtility``` determines the type of status dependency, with possible values being ```Self Reference```, ```Market Starting Point```, or ```Market Ending Point```.
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/status-report.md b/docs/_includes/data_mine/status-report.md
deleted file mode 100644
index 7686854c1..000000000
--- a/docs/_includes/data_mine/status-report.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Status Report" %}
-{% assign definition = site.data.data_mine.status_report %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Bots do not run continuously. Instead, they run in cycles. A cycle usually lasts until there is no more data to process, and once they finish, they shut down until the next cycle is due. A status report is a file every bot writes at the end of each cycle with information about the last run, including the datetime of the run and the last record processed.
-
-A status report may be consumed by the same bot producing it, or by other bots.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a status report, select *Add Missing Items* on the process definition node menu. Items that may be missing are created along with the basic structure of nodes required to define them.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/style-condition.md b/docs/_includes/data_mine/style-condition.md
deleted file mode 100644
index 5200f1c38..000000000
--- a/docs/_includes/data_mine/style-condition.md
+++ /dev/null
@@ -1,131 +0,0 @@
-
-
-{% assign title = "Style Condition" %}
-{% assign definition = site.data.data_mine.style_condition %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Style conditions offer a way to introduce additional intelligence on the visual representation of data by using styles that respond to certain conditions.
-
-For example, the *Percentage Bandwidth* plotter module assigns a different color to the Moving Average line when it's going up or down.
-
-To do that, a style condition features it's own style so that, when the condition validates true, the new style is applied.
-
-Style conditions me be created in a sequence so that the style may continue changing upon the validation of a series of style conditions. The system evaluates all style conditions in a sequential order determined by their position in the rotational symmetry around the parent node. Each condition that is met may modify or add up to the resulting style that is rendered on screen. That is, the final style is the result of the sequential application of the styles defined for each condition that is met, on top of the default style.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a style condition, select *Add Style Condition* on a polygon border or polygon body node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Editing a {{title}}
-
-
-
-Select *Edit Condition* on the menu to access the configuration.
-
-Style conditions work pretty much like conditions used on trading systems. The main difference is that the variables available are solely those provided by the bot product definition that reference the corresponding plotter module.
-
-To continue the example of the Percentage Bandwidth plotter, the following is the condition that determines the newly added styles:
-
-```js
-record.previous.movingAverage > record.movingAverage
-```
-
-As hinted earlier, when the condition is met, the default style is modified by a second style that may be created on the menu of the style condition node.
-
-The definition of secondary styles is slightly different from that of the default style, as—in such cases—the ```atMousePosition``` property may no longer be defined:
-
-```js
-{
- "opacity": 0.55,
- "lineWidth": 1,
- "lineDash": [0,0],
- "paletteColor": "UI_COLOR.RED"
-}
-```
-
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/style.md b/docs/_includes/data_mine/style.md
deleted file mode 100644
index d6668b7a9..000000000
--- a/docs/_includes/data_mine/style.md
+++ /dev/null
@@ -1,169 +0,0 @@
-
-
-{% assign title = "Style" %}
-{% assign definition = site.data.data_mine.style %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-A style applied to a polygon body or a polygon border node acts as the default style.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a style, select *Add Style* on a polygon border or polygon body node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Style* on the menu to access the configuration.
-
-A typical definition for a polygon body style looks like this:
-
-```json
-{
- "default": {
- "opacity": 0.2,
- "paletteColor": "UI_COLOR.DARK_TURQUOISE"
- },
- "atMousePosition": {
- "opacity": 0.3,
- "paletteColor": "UI_COLOR.DARK_TURQUOISE"
- }
-}
-```
-
-A typical definition for a polygon border style has a couple more properties:
-
-```json
-{
- "default": {
- "opacity": 0.2,
- "lineWidth": 1,
- "lineDash": [0,0],
- "paletteColor": "UI_COLOR.DARK_TURQUOISE"
- },
- "atMousePosition": {
- "opacity": 0.3,
- "lineWidth": 2,
- "lineDash": [0,0],
- "paletteColor": "UI_COLOR.RUSTED_RED"
- }
-}
-```
-
-The first section of the definition refers, as explicitly stated, to the default state of the style.
-
-The second section refers to the style assigned to the column or period on which the mouse pointer is located. This is very useful for highlighting the specific zone of interest as the user browses the charts.
-
-* ```opacity``` is probably self-explanatory: it may range from ```0``` for a fully transparent object to ```1``` for a solid object.
-
-* ```paletteColor``` sets the color for the *fill* or *stroke* in cases of polygon bodies and polygon borders respectively. Use the variable ```UI_COLOR``` followed by a ```.``` and any of the properties in the following list for a selection of currently available colors:
-
-| Variable Value | RGB Value | Color Sample |
-| :--- | :---: | :------------------- |
-| ```DARK``` | 48, 48, 54 | |
-| ```LIGHT``` | 234, 226, 222 | |
-| ```GREY``` | 150, 150, 150 | |
-| ```LIGHT_GREY``` | 247, 247, 247 | |
-| ```WHITE``` | 255, 255, 255 | |
-| ```BLACK``` | 0, 0, 0 | |
-| ```GOLDEN_ORANGE``` | 240, 162, 2 | |
-| ```RUSTED_RED``` | 204, 88, 53 | |
-| ```GREEN``` | 188, 214, 67 | |
-| ```RED``` | 223, 70, 60 | |
-| ```PATINATED_TURQUOISE``` | 27, 153, 139 | |
-| ```TITANIUM_YELLOW``` | 244, 228, 9 | |
-| ```MANGANESE_PURPLE``` | 91,80, 122 | |
-| ```TURQUOISE``` | 74, 207, 217 | |
-| ```DARK_TURQUOISE``` | 2, 149, 170 | |
-
-* ```lineWidth``` is the width of the border line, which should be greater than 0.
-
-* ```lineDash``` is used to turn the border into a dashed-line; the first value corresponds to the length of the dash while the second value defines the length of the space.
-
-{% include note.html content="When using dashed lines, bear in mind that the drawing from one column or period is independent of the next. Big values for dashes and spaces may not work well for lines that span several columns." %}
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/data_mine/template.md b/docs/_includes/data_mine/template.md
deleted file mode 100644
index 45b1bb57c..000000000
--- a/docs/_includes/data_mine/template.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "XXXXXXXXXXXXXXXX" %}
-{% assign definition = site.data.data_mine.XXXXXXXXXXXXXXXX %}
-{% assign preposition = "XXXXXXXXXXXXXXXX" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Trading bots are complex pieces of software. The system does not yet encourage the creation of further trading bots, as it is not currently possible to create them with minimal coding. However, developers are free to clone the existing trading bot and improve it as they see fit.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/feedback.html b/docs/_includes/feedback.html
deleted file mode 100644
index 6031797fc..000000000
--- a/docs/_includes/feedback.html
+++ /dev/null
@@ -1,13 +0,0 @@
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn how to {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-**1. Go to the workspace node.**
-
-{% include /how_to/go-to-the-workspace-node.md heading="more" definition="yes" content="yes" extended="no" table="no" more="yes"%}
-
-**2. Pan the design space in the desired direction.**
-
-The design space is organized over a square perimeter around the workspace node, and each hierarchy is located on one of the cardinal directions. Hierarchies feature an ever-present white ring. The ring hints the direction in which a hierarchy is located.
-
-| Hierarchy | Cardinal Direction | Direction | Keyboard Shortcut (windows only) |
-| :--- | :---: | :---: | :--- |
-| **Sparta Data Mine** | North | ↑ | Ctrl + Alt + S (*S for Sparta*) |
-| **WHB Trading System** | North East | ↗ | Ctrl + Alt + W (*W for Weak Hands Buster*) |
-| **BRR trading System** | East | → | Ctrl + Alt + B (*B for Bull Run Rider*) |
-| **Super Scripts** | South East | ↘ | Ctrl + Alt + Z (*Z for, well...*) |
-| **Network** | South | ↓ | Ctrl + Alt + N (*N for Network*) |
-| **Crypto Ecosystem** | South West | ↙ | Ctrl + Alt + E (*E for Ecosystem*) |
-| **Charting System** | West | ← | Ctrl + Alt + C (*C for Charting System*) |
-| **Masters Data Mine** | North West | ↖ | Ctrl + Alt + M (*M for Masters*) |
-
-{% include image.html file='how-to/find-a-hierarchy-00.gif' url='yes' max-width='100' caption='Navigate to the desired hierarchy starting from the workspace node and following the corresponding vertical, horizontal or diagonal direction. Once on a hierarchy, you can reach the next one by following a square perimeter around the workspace.' %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.extended == "more" and include.content != "more" and include.heading != "more" %}
-Click to learn how to {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.extended != "no" %}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/how_to/go-to-the-workspace-node.md b/docs/_includes/how_to/go-to-the-workspace-node.md
deleted file mode 100644
index dcfd7c378..000000000
--- a/docs/_includes/how_to/go-to-the-workspace-node.md
+++ /dev/null
@@ -1,68 +0,0 @@
-
-
-{% assign title = "Go to the Workspace Node" %}
-{% assign definition = site.data.how_to.go_to_the_workspace_node %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn how to {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} How to {{title}}
-{% endif %}
-
-{% if include.table == "yes" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-A backtesting session node must reference a trading system to gain access to the trading logic to be applied during the session. Other considerations framing the session come from the set of parameters attached to it.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a backtesting session, select *Add Backtesting Session* on the trading process instance node menu. When a session is added, it is created with the full set of parameters.
-
-{% include note.html content="After adding a session node, make sure you establish a reference to the trading system you want it to work with." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Session* on the menu to access the configuration.
-
-```json
-{
-"folderName": "Session-Name"
-}
-```
-
-* ```folderName``` allows you to set a significant name to the folder in which the data products—and logs—generated by the session are stored. If left blank, the system names the folders with the session id. This may be handy when you intend to consult the raw data generated by the session, as, otherwise, the folder would be hard to identify.
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-Before you start a backtesting session, the corresponding task needs to be running, as it is the task that puts the trading bot instance to run. Once the trading bot instance is running, select *Run* on the menu to start the session.
-
-After a few seconds, a literal indication of the progress of the calculations appears below the session node, displaying the date that is currently being processed. Once the calculation is finished, the session stops and the date below the session node dissapears.
-
-To stop a backtesting session, select *Stop* on the menu.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/data-mining.md b/docs/_includes/network/data-mining.md
deleted file mode 100644
index 6881066e2..000000000
--- a/docs/_includes/network/data-mining.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "Data Mining" %}
-{% assign definition = site.data.network.data_mining %}
-{% assign preposition = "a" %}
-{% assign plural = "" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Having access to quality information is a crucial element of trading. For that reason, Superalgos strives to give users full control over how, where and when data is processed. You will use this section of the network hierarchy to exert that control.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/data-product.md b/docs/_includes/network/data-product.md
deleted file mode 100644
index 0a23eee55..000000000
--- a/docs/_includes/network/data-product.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Data Product" %}
-{% assign definition = site.data.network.data_product %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Data products generated by the bot instances you run need to be stored somewhere—specifically. The data storage node and its chain of offspring determine that the data is to be stored in the corresponding node.
-
-{% include note.html content="At this point, the only node in which you may store data is your local *My Computer* node, however, in the future you will be able to store data, or even run bots, on remote machines that you will control from within your local deployment of the system." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a data storage, select *Add Data Storage* on the network node menu.
-
-{% include note.html content="Only one data storage may exist on each network node." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/forward-testing-session.md b/docs/_includes/network/forward-testing-session.md
deleted file mode 100644
index 2da249f5b..000000000
--- a/docs/_includes/network/forward-testing-session.md
+++ /dev/null
@@ -1,128 +0,0 @@
-
-
-{% assign title = "Forward Testing Session" %}
-{% assign definition = site.data.network.forward_testing_session %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-A forward testing session node must reference a trading system to gain access to the trading logic to be applied during the session. Other considerations framing the session come from the set of parameters attached to it.
-
-{% include note.html content="Running a forward testing session requires the setup of a key instance at the market reference. It also requires a live data feed, meaning that the corresponding sensor bot, along with all indicators used by the referenced trading system, must be up and running" %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a forward testing session, select *Add Forward Testing Session* on the trading process instance node menu. When a session is added, it is created with the full set of parameters.
-
-{% include note.html content="After adding a session node, make sure you establish a reference to the trading system you want it to work with." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Session* on the menu to access the configuration.
-
-```json
-{
-"folderName": "Session-Name",
-"balancePercentage": 1
-}
-```
-
-* ```folderName``` allows you to set a significant name to the folder in which the data products—and logs—generated by the session are stored. If left blank, the system names the folders with the session id. This may be handy when you intend to consult the raw data generated by the session, as, otherwise, the folder would be hard to identify.
-
-* ```balancePercentage``` is a number defining the percentage of the initialBalance specified in the base aset configuration that will be used for trading. For instance, ```"balancePercentage": 1``` means that 1% of your balance will be made available. Just like the ```initialBalance``` is scaled down, the ```minimumBalance``` and ```maximumBalance``` are also scaled down accordingly (see base asset).
-
-Let's draw a quick example:
-
-Your base asset is USDT and your initialBalance is USDT 10,000.
-
-If you set up your forward-testing session with "balancePercentage": "1", then USDT 10,000 * 1% = USDT 100. This is the balance that will be available to your forward-testing session.
-
-{% include important.html content="You need to take this into account at the time of defining your positionSize formula. If the formula is a constant, you may easily run out of balance, as only a fraction of the balance will be available for the strategy to use. It may be a good idea to set up your positionSize as a function of your available balance instead." %}
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-Before you start a forward testing session, the corresponding task needs to be running, as it is the task that puts the trading bot instance to run. Once the trading bot instance is running, select *Run* on the menu to start the session.
-
-To stop a backtesting session, select *Stop* on the menu.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/indicator-bot-instance.md b/docs/_includes/network/indicator-bot-instance.md
deleted file mode 100644
index 8be482382..000000000
--- a/docs/_includes/network/indicator-bot-instance.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Indicator Bot Instance" %}
-{% assign definition = site.data.network.indicator_bot_instance %}
-{% assign preposition = "an" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-{{site.data.concepts.indicator_bot}}
-
-The indicator bot instance holds no definitions as to what the bot does. Instead, its processes instances reference the process definitions in the corresponding data mine. That is how the indicator bot instance obtains the information of what it needs to do once it is run.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add an indicator bot instance, select *Add Indicator Bot Instance* on the task node menu. When an indicator bot instance is added, it is created with one indicator process instance, and a market reference.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-You do not start or stop an indicator bot instance directly. Instead, you start or stop the corresponding task.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/indicator-process-instance.md b/docs/_includes/network/indicator-process-instance.md
deleted file mode 100644
index 0b69a7c19..000000000
--- a/docs/_includes/network/indicator-process-instance.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Indicator Process Instance" %}
-{% assign definition = site.data.network.indicator_process_instance %}
-{% assign preposition = "an" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Indicator bot instances usually require two indicator process instances. One of them references the indicator's *multi-period-market* process definition and the second references the *multi-period-daily* process definition.
-
-Once the reference is established, the indicator process instance adopts the name of the process definition it references.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add an indicator process instance, select *Add Indicator Process Instance* on the indicator bot instance node menu. When an indicator process instance is added, it is created with a market reference.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-You do not start or stop an indicator process instance directly. Instead, you start or stop the corresponding task.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/key-instance.md b/docs/_includes/network/key-instance.md
deleted file mode 100644
index e99819447..000000000
--- a/docs/_includes/network/key-instance.md
+++ /dev/null
@@ -1,111 +0,0 @@
-
-
-{% assign title = "Key Instance" %}
-{% assign definition = site.data.network.key_instance %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The key instance must be attached to market reference nodes that participate in forward testing and live trading sessions, as that is the scenario in which the user must validate the account with the exchange.
-
-Some exchanges—like Binance—require validating the user even when retrieving data from the exchange. For such reasons, the key instance must also be attached to the market reference of the sensor process instance that connects to such exchanges.
-
-In all cases, the key instance node must reference a valid exchange account key from an account with the exchange, as defined in the Crypto Ecosystem hierarchy.
-
-{% include important.html content="Most exchanges do not allow the same exchange account key to be used with multiple processes querying the exchange API. This means that if you are trading with multiple trading systems or multiple sessions on the same exchange, each session requires different exchange account keys." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a key instance, select *Add Key Instance* on the market reference node menu.
-
-{% include note.html content="Remember to establish a reference with a valid exchange account key after creating the key instance." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/live-trading-session.md b/docs/_includes/network/live-trading-session.md
deleted file mode 100644
index e8d223447..000000000
--- a/docs/_includes/network/live-trading-session.md
+++ /dev/null
@@ -1,117 +0,0 @@
-
-
-{% assign title = "Live Trading Session" %}
-{% assign definition = site.data.network.live_trading_session %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-A live trading session node must reference a trading system to gain access to the trading logic to be applied during the session. Other considerations framing the session come from the set of parameters attached to it.
-
-{% include note.html content="Running a live trading session requires the setup of a key instance at the market reference. It also requires a live data feed, meaning that the corresponding sensor bot, along with all indicators used by the referenced trading system, must be up and running" %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a live trading session, select *Add Live Trading Session* on the trading process instance node menu. When a session is added, it is created with the full set of parameters.
-
-{% include note.html content="After adding a session node, make sure you establish a reference to the trading system you want it to work with." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Session* on the menu to access the configuration.
-
-```json
-{
-"folderName": "Session-Name"
-}
-```
-
-* ```folderName``` allows you to set a significant name to the folder in which the data products—and logs—generated by the session are stored. If left blank, the system names the folders with the session id. This may be handy when you intend to consult the raw data generated by the session, as, otherwise, the folder would be hard to identify.
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-Before you start a live trading session, the corresponding task needs to be running, as it is the task that puts the trading bot instance to run. Once the trading bot instance is running, select *Run* on the menu to start the session.
-
-To stop a backtesting session, select *Stop* on the menu.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/market-reference.md b/docs/_includes/network/market-reference.md
deleted file mode 100644
index e087c99c1..000000000
--- a/docs/_includes/network/market-reference.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Market Reference" %}
-{% assign definition = site.data.network.market_reference %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-At the moment, processes run locally in a network node representing your computer. In the future, you will also be able to deploy other nodes, such as virtual machines in the cloud, and control execution in those remote computers from within your local instance of the system.
-
-In a more distant future, you will also be able to connect to and consume services from other people's nodes.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/network.md b/docs/_includes/network/network.md
deleted file mode 100644
index 3e6da1c2c..000000000
--- a/docs/_includes/network/network.md
+++ /dev/null
@@ -1,111 +0,0 @@
-
-
-{% assign title = "Network" %}
-{% assign definition = site.data.network.network %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-You will use the network hierarchy for the following purposes:
-
-* To control your data mining, that is, processes running sensor and indicator bots. These keep your data feeds up to date so that you may trade live with quality information.
-
-* To control your testing environment, that is trading sessions including backtesting and paper trading.
-
-* To control your production environment, that is, forward testing, and live trading sessions running the trading bot.
-
-* To control your data storage, that is, to administer the physical location in which the data products produced by bots reside.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/paper-trading-session.md b/docs/_includes/network/paper-trading-session.md
deleted file mode 100644
index f5b6f93dc..000000000
--- a/docs/_includes/network/paper-trading-session.md
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-{% assign title = "Paper Trading Session" %}
-{% assign definition = site.data.network.paper_trading_session %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-A paper trading session node must reference a trading system to gain access to the trading logic to be applied during the session. Other considerations framing the session come from the set of parameters attached to it.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a paper trading session, select *Add Paper Trading Session* on the trading process instance node menu. When a session is added, it is created with the full set of parameters.
-
-{% include note.html content="After adding a session node, make sure you establish a reference to the trading system you want it to work with." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Session* on the menu to access the configuration.
-
-```json
-{
-"folderName": "Session-Name"
-}
-```
-
-* ```folderName``` allows you to set a significant name to the folder in which the data products—and logs—generated by the session are stored. If left blank, the system names the folders with the session id. This may be handy when you intend to consult the raw data generated by the session, as, otherwise, the folder would be hard to identify.
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-Before you start a paper trading session, the corresponding task needs to be running, as it is the task that puts the trading bot instance to run. Once the trading bot instance is running, select *Run* on the menu to start the session.
-
-To stop a backtesting session, select *Stop* on the menu.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/production-environment.md b/docs/_includes/network/production-environment.md
deleted file mode 100644
index efd87252b..000000000
--- a/docs/_includes/network/production-environment.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Production Environment" %}
-{% assign definition = site.data.network.production_environment %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-{{site.data.concepts.sensor_bot}}
-
-The sensor bot instance holds no definitions as to what the bot does. Instead, its process instance references a process definition in the corresponding data mine. That is how the sensor bot instance obtains the information regarding what it needs to do once it is run.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a sensor bot instance, select *Add Sensor Bot Instance* on the task node menu. When a sensor bot instance is added, it is created with one sensor process instance, and a market reference.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Sensor Bot Instance* on the menu to access the configuration.
-
-```json
- {
- "startDate": "2020-01-01"
- }
-```
-
-* ```startDate``` is the *desired starting date* of the data product the sensor bot instance builds, in the ```YYYY-MM-DD``` format. The sensor bot instance queries its data source for data starting on the configured ```startDate```.
-
- * The actual date in which the dataset starts depends on external factors: A. The market may start at a later date. B. The exchange may limit how far in the past data may be retrieved. In both cases, the sensor bot automatically discovers the date closest to the *desired starting date* that is possible to start with, and proceeds accordingly.
-
- * In the case the ```startDate``` is changed after the sensor bot has started building a data product, either for an earlier or later date, the sensor re-evaluates the feasibility of starting at the new date. The actual date may or may not change; regardless, the sensor bot discards the existing data product and starts over from the newly discovered date. In other words, if the ```startDate``` is changed, the sensor bot starts over.
-
- * Notice that the above starts a chain reaction among all indicator bots that have a data dependency with the sensor bot's output dataset. Also, if the actual date ends up changing, all indicators that determine the starting date of the market by looking at the date discovered by the sensor bot have to discard their existing data products and start over from the new date.
-
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-You do not start or stop a sensor bot instance directly. Instead, you start or stop the corresponding task.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/sensor-process-instance.md b/docs/_includes/network/sensor-process-instance.md
deleted file mode 100644
index a48b96fcc..000000000
--- a/docs/_includes/network/sensor-process-instance.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "Sensor Process Instance" %}
-{% assign definition = site.data.network.sensor_process_instance %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-For example, in the case of an instance of the Masters data mine Charly sensor bot, the sensor bot process instance references the *Historic Trades* process definition. Once the reference is established, the sensor process instance adopts the name of the process definition it references.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a sensor process instance, select *Add Sensor Process Instance* on the sensor bot instance node menu. When a sensor process instance is added, it is created with a market reference.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-You do not start or stop a sensor process instance directly. Instead, you start or stop the corresponding task.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/session-based-data.md b/docs/_includes/network/session-based-data.md
deleted file mode 100644
index 57f1e380f..000000000
--- a/docs/_includes/network/session-based-data.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Session Based Data" %}
-{% assign definition = site.data.network.session_based_data %}
-{% assign preposition = "a" %}
-{% assign plural = "" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-A task manager facilitates the organization of tasks. For example, you may wish to set up a task manager to handle tasks related to a particular set of indicators you use with a certain strategy. Or, for example, to organize multiple backtesting sessions.
-
-{% include tip.html content="The key aspect of a task manager is that it allows starting and stopping all tasks at once." %}
-
-{% include note.html content="Users may have access to several data mines, each offering different indicators and studies. For organizational purposes, it is recommended each data mine has its task manager. However, the system allows any form of organization." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a task manager, select *Add Task Manager* on the *My Computer* network node menu. A task manager is added along with a task.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-Select *Run All Tasks* or *Stop All Tasks* on the menu to start and stop all tasks respectively.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/task.md b/docs/_includes/network/task.md
deleted file mode 100644
index 4a938f037..000000000
--- a/docs/_includes/network/task.md
+++ /dev/null
@@ -1,107 +0,0 @@
-
-
-{% assign title = "Task" %}
-{% assign definition = site.data.network.task %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Each task controls a single bot. A bot instance running on its own task is independent from other bots at the operating system level, thus, may not be affected by errors ocurring on those other bots.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a task, select *Add Task* on the task manager node menu.
-
-{% include tip.html content="Instead of adding nodes, configuring them, and setting references one by one, you may want to clone an existing, fully functional task with all its offspring." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-Select *Run* on the menu to start a task. When a task is started, the process instance of the bot instance attached to the task is started. Also, a visual indication that both the task and the process instance are running appear surrounding the corresponding nodes, in the form of a progress ring.
-
-To stop a task, select *Stop* on the menu.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/testing-environment.md b/docs/_includes/network/testing-environment.md
deleted file mode 100644
index becfb91cd..000000000
--- a/docs/_includes/network/testing-environment.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Testing Environment" %}
-{% assign definition = site.data.network.testing_environment %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-A thorough and comprehensive testing of strategies is at the core of successful trading. Superalgos strives to put you in control of the testing process providing you with flexible tools to fit your criteria.
-
-Depending on how you use the system, how many markets and exchanges you work with, the number of trading systems you use, or the way you choose to test your strategies, you may find yourself with a large number of testing sessions. It is recommended you organize all of your testing sessions below the testing environment node.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/trading-bot-instance.md b/docs/_includes/network/trading-bot-instance.md
deleted file mode 100644
index 05dcc3323..000000000
--- a/docs/_includes/network/trading-bot-instance.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Trading Bot Instance" %}
-{% assign definition = site.data.network.trading_bot_instance %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-{{site.data.concepts.trading_bot}}
-
-The trading bot instance holds no definitions as to what the bot does. Instead, its process instance references the process definition in the Masters data mine. That is how the indicator bot instance obtains the information of what it needs to do once it is run.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a trading bot instance, select *Add Trading Bot Instance* on the task node menu. When a trading bot instance is added, it is created with one trading process instance, and a market reference.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-You do not start or stop a trading bot instance directly. Instead, you start or stop the corresponding task.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/network/trading-process-instance.md b/docs/_includes/network/trading-process-instance.md
deleted file mode 100644
index 4337e3d1a..000000000
--- a/docs/_includes/network/trading-process-instance.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Trading Process Instance" %}
-{% assign definition = site.data.network.trading_process_instance %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The trading process instance must reference the *Multi-Period* process definition of the Jason trading bot in the Masters data mine.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a trading process instance, select *Add Trading Process Instance* on the trading bot instance node menu. When a trading process instance is added, it is created with a market reference.
-
-{% include note.html content="After adding a trading process instance node, make sure you establish the reference to the *Multi-Period* process definition of the Jason trading bot in the Masters data mine." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-You do not start or stop a trading process instance directly. Instead, you start or stop the corresponding task.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/note.html b/docs/_includes/note.html
deleted file mode 100644
index 2c1cfe967..000000000
--- a/docs/_includes/note.html
+++ /dev/null
@@ -1 +0,0 @@
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The basse asset must reference an asset in a specific market of a specific exchange in the Crypto Ecosystem hierarchy.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu.
-
-{% include note.html content="After adding a base asset node, make sure you establish a reference to the asset in a specific market of a specific exchange in the Crypto Ecosystem hierarchy." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Base Asset* on the menu to access the configuration.
-
-```json
-{
-"initialBalance": 0.001,
-"minimumBalance": 0.0001,
-"maximumBalance": 0.1
-}
-```
-
-* ```initialBalance``` is the amount of capital you wish to allocate to the trading system.
-
-* ```minimumBalance``` is the threshold of accummulated losses that switches off the session; when your overall balance (balanceAssetA + balanceAssetB) drops to this value, all trading stops; think of the ```minimumBalance``` as a general safety switch.
-
-* ```maximumBalance``` is a similar concept as with the ```minimumBalance``` but on the high side of the ```initialBalance```.
-
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/close-execution.md b/docs/_includes/trading_system/close-execution.md
deleted file mode 100644
index fec293814..000000000
--- a/docs/_includes/trading_system/close-execution.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "Close Execution" %}
-{% assign definition = site.data.trading_system.close_execution %}
-{% assign preposition = "the" %}
-{% assign plural = "" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-As explained earlier while discussing the open stage, the execution functionality is currently under development. Needless to say, execution of the closing orders is of the highest significance, but in the meantime some temporal execution limitations apply.
-
-Also pending development is the keeping of a formal trading log. The current functionality allows you to see each trade on the screen, along with all the corresponding details, as well as a consolidated report on the live trading panel. This information is stored as a data product, thus, it is not lost. In the future, the system should incorporate a user-friendly feature to browse such logs, and even help analyze them in search for potential optimizations of your trading systems.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a close stage node, select *Add Missing Stages* on the strategy node menu. All stages that may be missing are created along with the rest of the basic structure of nodes required to define each of them and their events.
-
-{% include note.html content="Only one close stage may exist in each strategy." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/condition.md b/docs/_includes/trading_system/condition.md
deleted file mode 100644
index 012ad418c..000000000
--- a/docs/_includes/trading_system/condition.md
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-{% assign title = "Condition" %}
-{% assign definition = site.data.trading_system.condition %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Therefore, conditions are used to mathematically describe what needs to happen with the market for a certain action to be taken.
-
-**For example:**
-
-**Situation 1**
-
-* Condition A: ```chart.at01hs.candle.close > chart.at01hs.bollingerBand.MovingAverage``` → This means that the latest candle at the 1 hour chart closed above the Bollinger Bands moving average.
-
-* Condition B: ```chart.at01hs.candle.previous.max > chart.at01hs.bollingerBand.previous.MovingAverage``` → This means that the maximum value of the candle before the last one, was higher than the Bollinger Bands moving average.
-
-In the example above, conditions A and B are comparison statements that may evaluate either _true_ or _false_. In the case both would evaluate _true_ then Situation 1 would be true as well.
-
-{% include note.html content="To learn how to write conditions, start with the Syntax Overview." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a condition, select *Add Condition* on the corresponding situation node menu. A condition with its JavaScript code node is added.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/fee-structure.md b/docs/_includes/trading_system/fee-structure.md
deleted file mode 100644
index f32563c46..000000000
--- a/docs/_includes/trading_system/fee-structure.md
+++ /dev/null
@@ -1,130 +0,0 @@
-
-
-{% assign title = "Fee Structure" %}
-{% assign definition = site.data.trading_system.fee_structure %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Exchange fees are a crucial part of trading. A strategy may work like a charm when you leave fees out of the equation but would lead you to bankruptcy in a live trading situation.
-
-Fee structures are factored both in the session reports and in the graphic representation of each trade provided by the simulation trades product of the trading bot.
-
-To illustrate how fees affect your bottom line, take a look at the image below.
-
-[](https://user-images.githubusercontent.com/13994516/63636432-8d8cdf80-c66f-11e9-86a3-480d157d8126.gif)
-
-The trade hits the take profit target above the Position Rate level, however, due to fees, the trade has a negative 0.32% ROI.
-
-In the context of forward testing and live trading sessions, the fee structure assumptions do not affect actual transactions. However, the parameter is taken into account when creating simulation layers, which are also available during forward testing and live trading.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Fee Structure* on the menu to access the configuration.
-
-```json
-{
-"maker": 0.15,
-"taker": 0.25
-}
-```
-
-* ```maker``` is the setting for the fee the exchange charges when an order adds liquidity to the market, such as with limit orders.
-
-* ```taker``` is the setting for the fee the exchange charges when an order takes liquidity from the market, such as with market or instant orders.
-
-{% include note.html content="Check the fees structure in your exchange, carefully looking into the tier you fall in to feed accurate assumptions to your backtesting and paper trading sessions." %}
-
-{% include note.html content="If the fee structure parameter is left empty or detached both from your session and your trading system, fees are not computed during simulations." %}
-
-{% include important.html content="Remember that, for the time being, and until the new execution engine is released, all orders placed by the trading bot are *market orders*, thus, the *taker* fee applies in all cases." %}
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/formula.md b/docs/_includes/trading_system/formula.md
deleted file mode 100644
index b97ad11a9..000000000
--- a/docs/_includes/trading_system/formula.md
+++ /dev/null
@@ -1,111 +0,0 @@
-
-
-{% assign title = "Formula" %}
-{% assign definition = site.data.trading_system.formula %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-In the context of a trading system, formulas are used to determine the values for stopLoss, takeProfit, positionRate and positionSize.
-
-Formulas may use [internal variables](suite-internal-variables.html) made available by the system. In addition to the ones listed above, other variables such as balanceAssetA and balanceAssetB may be of use.
-
-**For example:**
-
-* ```positionRate - positionRate * 2.5 / 100``` → This formula may be used to define an initial stop target 2.5% below the rate at which the position was taken.
-
-{% include note.html content="To learn which variables may be used in formulas, see the page about internal variables." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a formula, select *Add Formula* on the corresponding parent node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/initial-definition.md b/docs/_includes/trading_system/initial-definition.md
deleted file mode 100644
index 3de483bea..000000000
--- a/docs/_includes/trading_system/initial-definition.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "Initial Definition" %}
-{% assign definition = site.data.trading_system.initial_definition %}
-{% assign preposition = "an" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Notice that the setting of the stop target has no relation to the execution of orders. The stop is a target, not an order to be placed. That is, the system does not place stop orders.
-
-This is a design feature that allows you to keep your cards, not allowing anyone to anticipate what your strategy may be, not even the exchange. It is a known fact that some exchanges may attempt or allow to front-run stop orders.
-
-Instead, the trading bot instance monitors the market, and only once the stop target has been hit does it place the corresponding order to close the trade.
-
-The initial target is set in phase 0, that is, the departing point for the management of the trade to be handled in the manage stage.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add an initial stop node, select *Add Missing Items* on the initial definitions node menu. All items that may be missing are created along with the rest of the basic structure of nodes required to define each of them.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/initial-take-profit.md b/docs/_includes/trading_system/initial-take-profit.md
deleted file mode 100644
index 6ec0683df..000000000
--- a/docs/_includes/trading_system/initial-take-profit.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Initial Take Profit" %}
-{% assign definition = site.data.trading_system.initial_take_profit %}
-{% assign preposition = "the" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Pretty much like with the initial stop, the initial take profit is a target, and not an order to be placed. Only when the trading bot instance detects that the target has been hit does it place an order to close the trade.
-
-The initial target is set in phase 0, which may shift to the following phase once the corresponding next phase event is validated.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add an initial take-profit node, select *Add Missing Items* on the initial definitions node menu. All items that may be missing are created along with the rest of the basic structure of nodes required to define each of them.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/javascript-code.md b/docs/_includes/trading_system/javascript-code.md
deleted file mode 100644
index 37e5117e0..000000000
--- a/docs/_includes/trading_system/javascript-code.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "JavaScript Code" %}
-{% assign definition = site.data.data_mine.javascript_code %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The management of a trade aims to increase the efficiency of your trading system. Conceptually, a trade is not an instantaneous event, but an event which has an opening, a period of maturation, and a closing. The management of the trade happens in that period of maturation.
-
-The concept of managing the trade means that the formulas to determine the take profit and stop may change as the trade develops. The typical situation in which you may want to change your original take profit and stop formulas is when the trade seems to be going well in your favor.
-
-It may be in your best interest to manage both stop and take-profit targets, moving them in the direction of the trade as the market moves, allowing some leeway for a larger profit than expected and, at the same time, cutting the potential for losses.
-
-The management of the trade is handled in phases. Actually, the management of take profit and stop—while correlated—is done independently of each other, therefore, each concept has its own set of phases.
-
-When a situation defined by a set of conditions is met, the next phase event indicates that the take profit or stop formulas shall be changed. At the moment those predefined conditions are met, you enter the next phase. Keep in mind that the trade is in constant development, so there may be as many phases as you deem appropriate for your particular strategy.
-
-The idea of having different phases comes from the notion that big market moves tend to provide clues as to what may come up next. For instance, rallies may accelerate as more traders join the move. Recognizable patterns may emerge. Signs of exhaustion may be identified.
-
-All of these considerations should feed the dynamic analysis performed as the trade develops, and may be contrasted with the predefined conditions that may push take profit or stop further, entering one phase after the next.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a manage stage node, select *Add Missing Stages* on the strategy node menu. All stages that may be missing are created along with the rest of the basic structure of nodes required to define each of them and their events.
-
-{% include note.html content="Only one manage stage may exist in each strategy." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/next-phase-event.md b/docs/_includes/trading_system/next-phase-event.md
deleted file mode 100644
index 367c30e54..000000000
--- a/docs/_includes/trading_system/next-phase-event.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "Next Phase Event" %}
-{% assign definition = site.data.trading_system.next_phase_event %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The management of a trade is performed in sequential phases. Each phase may define a new formula for stop loss and take profit targets. To move from one phase to the next, a certain situation must be validated. When that happens, the next phase event is triggered and the formulas corresponding to the following phase are applied. Such situations must be defined under the next phase event.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a next phase event, select *Add Next Phase Event* on the corresponding phase node menu. The event is added along with the basic structure of nodes to define it.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/open-execution.md b/docs/_includes/trading_system/open-execution.md
deleted file mode 100644
index d01879900..000000000
--- a/docs/_includes/trading_system/open-execution.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "Open Execution" %}
-{% assign definition = site.data.trading_system.open_execution %}
-{% assign preposition = "the" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-Conceptually, the open stage deals with the details that concern the opening of a trade once the decision to take a position has been made. In this stage, you deal with the aforementioned parameters, each of which is defined by a formula.
-
-Ideally, the open stage would also handle the parameters that define the execution of the trade, that is, how and which kinds of orders are to be placed, on which exchanges and so on. However, the execution side of the system is still under development. For the time being, execution is drastically simplified: a single market order is placed for each order.
-
-{% include note.html content="Learn more about the temporal execution limitations." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add an open stage node, select *Add Missing Stages* on the strategy node menu. All stages that may be missing are created along with the rest of the basic structure of nodes required to define each of them and their events.
-
-{% include note.html content="Only one open stage may exist in each strategy." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/parameters.md b/docs/_includes/trading_system/parameters.md
deleted file mode 100644
index b779a8ae1..000000000
--- a/docs/_includes/trading_system/parameters.md
+++ /dev/null
@@ -1,108 +0,0 @@
-
-
-{% assign title = "Parameters" %}
-{% assign definition = site.data.trading_system.parameters %}
-{% assign preposition = "a" %}
-{% assign plural = "" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The behavior of parameters may vary depending on the type of session.
-
-Each testing session has its own set of parameters. This allows you to configure different trading sessions with different parameters, and go back and forth between them as required. For instance, you may have different backtesting sessions with different date ranges, different exchange fees or different slippage settings to account for different possible scenarios.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a parameters node, select *Add Parameters* on the session or the trading system menu, depending on the context. When a parameters node is added, the full set of parameters are created with it.
-
-If you already have a parameters node but are missing some of the parameters, then select *Add Missing Params* on the menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
-
diff --git a/docs/_includes/trading_system/phase-0.md b/docs/_includes/trading_system/phase-0.md
deleted file mode 100644
index cd6e2853e..000000000
--- a/docs/_includes/trading_system/phase-0.md
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-{% assign title = "Phase 0" %}
-{% assign definition = site.data.trading_system.phase_0 %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The management of phases happens in a sequence. Phase 1 comes after phase 0, which holds the initial definitions for stop and take profit targets. You may continue adding phase 2, phase 3 and so on. Once the next phase event is triggered in one phase, the system applies the targets of the following phase and starts monitoring the situations defined in the corresponding next phase event.
-
-{% include note.html content="Notice that stop loss and take profit phases are independent and defined separately from each other, each below the corresponding stop and take-profit branch of the manage stage." %}
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a new phase, select *Add Phase* on the stop or take-profit node menu. A new phase is added along with the basic structure of nodes required to define each of them and their events.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/position-rate.md b/docs/_includes/trading_system/position-rate.md
deleted file mode 100644
index ce4bbe83c..000000000
--- a/docs/_includes/trading_system/position-rate.md
+++ /dev/null
@@ -1,104 +0,0 @@
-
-
-{% assign title = "Position Rate" %}
-{% assign definition = site.data.trading_system.position_rate %}
-{% assign preposition = "the" %}
-{% assign plural = "s" %}
-
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-However, for the time being, the formula is overridden by the system as execution is currently limited to market orders until a more robust execution system is deployed. Therefore, the position rate is currently taken from the closing value of the last candle.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a position rate node, select *Add Missing Items* on the initial definitions node menu. All items that may be missing are created along with the rest of the basic structure of nodes required to define each of them.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/position-size.md b/docs/_includes/trading_system/position-size.md
deleted file mode 100644
index ddde3e0eb..000000000
--- a/docs/_includes/trading_system/position-size.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "Position Size" %}
-{% assign definition = site.data.trading_system.position_size %}
-{% assign preposition = "the" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-The quoted asset must reference the second asset in the same market of the same exchange as the reference established with the base asset.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu.
-
-{% include note.html content="After adding a quoted asset node, make sure you establish a reference to the second asset in the same market of the same exchange as the reference established with the base asset." %}
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/situation.md b/docs/_includes/trading_system/situation.md
deleted file mode 100644
index 1437485a8..000000000
--- a/docs/_includes/trading_system/situation.md
+++ /dev/null
@@ -1,107 +0,0 @@
-
-
-{% assign title = "Situation" %}
-{% assign definition = site.data.trading_system.situation %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-In other words, you define situations in which you wish a certain event to happen (*i.e.:* trigger on the strategy, take a position, etc.) and each situation is described as a set of conditions that need to be met for the event to be triggered.
-
-A situation gets validated when all conditions under it are true.
-
-An event may have more than one situation attached to it. In such a case, when any of the situations gets validated, the event gets triggered. That is, events may be triggered in different circumstances, meaning that you are free to define different situations upon which the same event would be triggered. In such a case, when any of the situations evaluate true, then the event is triggered.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a situation, select *Add Situation* on the corresponding event node menu. A situation is added along with a condition and JavaScript code node.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/slippage.md b/docs/_includes/trading_system/slippage.md
deleted file mode 100644
index 2b983c1a8..000000000
--- a/docs/_includes/trading_system/slippage.md
+++ /dev/null
@@ -1,123 +0,0 @@
-
-
-{% assign title = "Slippage" %}
-{% assign definition = site.data.trading_system.slippage %}
-{% assign preposition = "a" %}
-{% assign plural = "" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-{% if include.more == "yes" and include.content == "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.content != "no" %}
-
-
-
-In the context of forward testing and live trading sessions, slippage does not affect the actual transactions. However, the parameter is taken into account when creating simulation layers, which are also available during forward testing and live trading.
-
-Slippage is factored both in the session reports and in the graphic representation of each trade provided by the simulation trades product of the trading bot.
-
-
-
-{% endif %}
-
-{% if include.more == "yes" and include.content != "more" and include.heading != "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.adding != "" %}
-
-{{include.adding}} Adding {{preposition}} {{title}} Node
-
-
-
-To add a parameter that may be missing, select *Add Missing Params* on the parameters node menu.
-
-
-
-{% endif %}
-
-{% if include.configuring != "" %}
-
-{{include.configuring}} Configuring the {{title}}
-
-
-
-Select *Configure Slippage* on the menu to access the configuration.
-
-```json
-{
-"positionRate": 0.1,
-"stopLoss": 0.2,
-"takeProfit": 0.3
-}
-```
-
-* ```positionRate``` is the slippage value to be applied to the rate of the take position order, expressed as a percentage (*i.e.:* 0.1 means 0.1%).
-
-* ```stopLoss``` is the slippage value to be applied to the rate of the stop order, expressed as a percentage (*i.e.:* 0.2 means 0.2%).
-
-* ```takeProfit``` is the slippage value to be applied to the rate of the take profit order, expressed as a percentage (*i.e.:* 0.3 means 0.3%).
-
-The number you enter is applied as a percentage of the price of the order and added or subtracted from the price depending on the circumstances, always working against you. For instance, ```"positionRate": 0.1``` means the position will be set at a price 0.1% higher or lower depending on which of the assets in the pair is your base asset.
-
-{% include note.html content="If the slippage parameter is left empty or detached both from your session and your trading system, slippage is not computed during simulations."%}
-
-
-
-{% endif %}
-
-{% if include.starting != "" %}
-
-{{include.starting}} Starting {{preposition}} {{title}}
-
-
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
-
-
-{% endif %}
-
-{% if include.more == "yes" %}
-
-{% endif %}
\ No newline at end of file
diff --git a/docs/_includes/trading_system/stop.md b/docs/_includes/trading_system/stop.md
deleted file mode 100644
index 96e15ed31..000000000
--- a/docs/_includes/trading_system/stop.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-{% assign title = "Stop" %}
-{% assign definition = site.data.trading_system.stop %}
-{% assign preposition = "a" %}
-{% assign plural = "s" %}
-
-
-
-{% if include.more == "yes" and include.heading == "more" %}
-Click to learn more about {{ title | downcase }}{{plural}}
-
-{% endif %}
-
-{% if include.heading != "" and include.heading != "more" %}
-{{include.heading}} {{title}}
-{% endif %}
-
-{% if include.icon != "no" %}
-
-{% if include.table == "yes" and include.icon != "no" %}
-
-{% endif %}
-
-
-
-{% if include.table == "yes" and include.icon != "no" %}
-