diff --git a/build_report.sh b/build_report.sh
new file mode 100644
index 0000000..bbd9c1e
--- /dev/null
+++ b/build_report.sh
@@ -0,0 +1 @@
+retype watch
\ No newline at end of file
diff --git a/node_modules/.bin/retype b/node_modules/.bin/retype
new file mode 100644
index 0000000..bb94e36
--- /dev/null
+++ b/node_modules/.bin/retype
@@ -0,0 +1,16 @@
+#!/bin/sh
+basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')")
+
+case `uname` in
+ *CYGWIN*|*MINGW*|*MSYS*)
+ if command -v cygpath > /dev/null 2>&1; then
+ basedir=`cygpath -w "$basedir"`
+ fi
+ ;;
+esac
+
+if [ -x "$basedir/node" ]; then
+ exec "$basedir/node" "$basedir/../retypeapp-win-x64/retype.js" "$@"
+else
+ exec node "$basedir/../retypeapp-win-x64/retype.js" "$@"
+fi
diff --git a/node_modules/.bin/retype.cmd b/node_modules/.bin/retype.cmd
new file mode 100644
index 0000000..b3b34cf
--- /dev/null
+++ b/node_modules/.bin/retype.cmd
@@ -0,0 +1,17 @@
+@ECHO off
+GOTO start
+:find_dp0
+SET dp0=%~dp0
+EXIT /b
+:start
+SETLOCAL
+CALL :find_dp0
+
+IF EXIST "%dp0%\node.exe" (
+ SET "_prog=%dp0%\node.exe"
+) ELSE (
+ SET "_prog=node"
+ SET PATHEXT=%PATHEXT:;.JS;=;%
+)
+
+endLocal & goto #_undefined_# 2>NUL || title %COMSPEC% & "%_prog%" "%dp0%\..\retypeapp-win-x64\retype.js" %*
diff --git a/node_modules/.bin/retype.ps1 b/node_modules/.bin/retype.ps1
new file mode 100644
index 0000000..8c82fe3
--- /dev/null
+++ b/node_modules/.bin/retype.ps1
@@ -0,0 +1,28 @@
+#!/usr/bin/env pwsh
+$basedir=Split-Path $MyInvocation.MyCommand.Definition -Parent
+
+$exe=""
+if ($PSVersionTable.PSVersion -lt "6.0" -or $IsWindows) {
+ # Fix case when both the Windows and Linux builds of Node
+ # are installed in the same directory
+ $exe=".exe"
+}
+$ret=0
+if (Test-Path "$basedir/node$exe") {
+ # Support pipeline input
+ if ($MyInvocation.ExpectingInput) {
+ $input | & "$basedir/node$exe" "$basedir/../retypeapp-win-x64/retype.js" $args
+ } else {
+ & "$basedir/node$exe" "$basedir/../retypeapp-win-x64/retype.js" $args
+ }
+ $ret=$LASTEXITCODE
+} else {
+ # Support pipeline input
+ if ($MyInvocation.ExpectingInput) {
+ $input | & "node$exe" "$basedir/../retypeapp-win-x64/retype.js" $args
+ } else {
+ & "node$exe" "$basedir/../retypeapp-win-x64/retype.js" $args
+ }
+ $ret=$LASTEXITCODE
+}
+exit $ret
diff --git a/node_modules/.package-lock.json b/node_modules/.package-lock.json
new file mode 100644
index 0000000..f3bff67
--- /dev/null
+++ b/node_modules/.package-lock.json
@@ -0,0 +1,15 @@
+{
+ "name": "bonares-handbook",
+ "lockfileVersion": 3,
+ "requires": true,
+ "packages": {
+ "node_modules/retypeapp-win-x64": {
+ "version": "3.5.0",
+ "resolved": "https://registry.npmjs.org/retypeapp-win-x64/-/retypeapp-win-x64-3.5.0.tgz",
+ "integrity": "sha512-II9fqg6gBBiCdlJ2n5EB89dNusgko9D2qKXaqCgCPuNOS7c7rMgL5bORt3r8mVWbL25gC1U+40KNuchYuzUpvQ==",
+ "bin": {
+ "retype": "retype.js"
+ }
+ }
+ }
+}
diff --git a/node_modules/retypeapp-win-x64/LICENSE b/node_modules/retypeapp-win-x64/LICENSE
new file mode 100644
index 0000000..c5a1422
--- /dev/null
+++ b/node_modules/retypeapp-win-x64/LICENSE
@@ -0,0 +1,248 @@
+Retype Software License Agreement
+
+Version 3.5.0
+
+THIS DOCUMENT IS A LEGAL AGREEMENT (the "License Agreement") BETWEEN OBJECT.NET, INC. ("We," "Us")
+AND YOU OR THE ORGANIZATION ON WHOSE BEHALF YOU ARE UNDERTAKING THE LICENSE DESCRIBED BELOW ("You",
+"Your") IN RELATION TO THE RETYPE SOFTWARE LIBRARY(IES) (THE "Software"), IN BOTH SOURCE AND OBJECT
+CODE FORM, AND/OR ALL RELATED MATERIALS.
+
+BY DOWNLOADING, INSTALLING, COPYING OR OTHERWISE USING THE SOFTWARE, YOU ACCEPT THE FOLLOWING TERMS
+AND CONDITIONS. IF YOU DO NOT AGREE WITH ANY OF THE TERMS OR CONDITIONS OF THIS LICENSE AGREEMENT,
+DO NOT PROCEED WITH THE DOWNLOADING, COPYING, INSTALLATION OR ANY OTHER USE OF THE SOFTWARE OR ANY
+PORTION THEREOF AS YOU HAVE NO RIGHTS TO DO SO. THE SOFTWARE IS PROTECTED BY UNITED STATES
+COPYRIGHT LAWS AND INTERNATIONAL COPYRIGHT LAWS, AS WELL AS OTHER INTELLECTUAL PROPERTY LAWS AND
+TREATIES. THE SOFTWARE IS LICENSED, NOT SOLD.
+
+THIS LICENSE AGREEMENT DESCRIBES YOUR RIGHTS AND RESTRICTIONS WITH RESPECT TO THE SOFTWARE AND
+ITS COMPONENTS.
+
+1. DEFINITIONS
+
+"Application" means any software, application, or elements that Your Designated Users develop using
+the Software or Modifications in accordance with this Agreement; provided that any such Application
+(i) must have substantially different functionality than the Software, and (ii) must not allow any
+third party to use the Software or Modifications, or any portion thereof, for software development
+or application development purposes.
+
+"Designated User" shall mean a single distinct person for whom You have purchased a license to use
+the Software, whether such person is an employee acting within the scope of their employment with
+You or Your consultant or contractor acting within the scope of the services they provide for You.
+A Designated User can be replaced with a new Designated User only after being a Designated User
+for a minimum of six (6) months.
+
+"End User" means an end user of Your Application who acquires a license to such solely for their
+own internal use and not for distribution, resale, user interface design, or software development
+purposes.
+
+"Modification" means: a) any addition to or deletion from the contents of a file included in the
+original Software or previous Modifications created by You, and/or b) any new file that leverages
+any part of the original Software or previous Modifications.
+
+"Sample Code" means sample source code included with the Software and designated as "sample code,"
+"samples," "sample application code," and/or "snippets," and/or found in directories labeled
+"samples", "learn", "docs", "examples" or "examples explorer".
+
+2. LICENSE GRANT
+
+Subject to the payment of the fee required, and subject to your compliance with all of the terms
+and conditions of this Agreement, We grant to You a revocable, non-exclusive, non-transferable and
+non-sublicensable license (i) for Designated User(s) to use the Software to create Modifications
+and Applications; (ii) for You to distribute the Software and/or Modifications to End Users solely
+as integrated into the Applications; and (iii) for End Users to use the Software as integrated into
+Your Applications in accordance with the terms of this Agreement.
+
+In addition to the other terms contained herein, We grant to You a revocable, non-exclusive,
+non-transferable and non-sublicensable license to install and use the Software (the "Free License")
+for Your internal evaluation, review, and production purposes. The Free License may contain
+restricted functionality. You are explicitly not permitted to distribute the Software to any user
+outside the Organization on whose behalf you have undertaken this license. We reserve the right to
+terminate Your License at any time in Our absolute and sole discretion. Without the purchase and
+inclusion of a License Key, the Software may contain restricted functionality, which from
+time-to-time may differ in its limitations. If you wish to remove these restrictions, you are
+required to purchase a Retype License Key; otherwise you must leave this limitation intact and not
+attempt to modify or circumvent it in any way.
+
+In addition to the other terms contained herein, in the event You have downloaded or received beta
+or pre-release versions of the Software (the "Beta Software") from Us, We grant to You a revocable,
+non-exclusive, non-transferable and non-sublicensable license to install and use the Beta Software
+strictly for Your internal evaluation and review purposes and not for production purposes (the
+"Beta License"). You are explicitly not permitted to distribute the Software to any user outside
+the Organization on whose behalf you have undertaken this license. Your rights to use the Beta
+Software will immediately terminate upon the earlier of (i) the expiration of the evaluation period
+established by Us, or (ii) such time that You purchase a license to a non-evaluation version of the
+Software. We reserve the right to terminate Your Beta License at any time in Our absolute and sole
+discretion.
+
+YOU ACKNOWLEDGE THAT TRIAL AND/OR BETA SOFTWARE MIGHT PLACE WATERMARKS ON OUTPUT, CONTAIN LIMITED
+FUNCTIONALITY, FUNCTION FOR A LIMITED PERIOD OF TIME, OR LIMIT THE FUNCTIONALITY OR TIME OF
+FUNCTIONING OF ANY OUTPUT. ACCESS TO AND/OR USE OF ANY FILES OR OUTPUT CREATED WITH SUCH SOFTWARE
+IS ENTIRELY AT YOUR OWN RISK. WE ARE LICENSING THE SOFTWARE ON AN "AS IS" BASIS AT YOUR OWN RISK
+AND WE DISCLAIM ANY WARRANTY OR LIABILITY TO YOU OF ANY KIND.
+
+You may modify the "Sample Code" solely for the purposes of designing, developing and testing Your
+own Applications. However, You are permitted to use, copy and redistribute Your modified Sample
+Code only if all of the following conditions are met: (a) You include Our copyright notice (if any)
+with Your Application, including every location in which any other copyright notice appears in such
+Application; and (b) You do not otherwise use Our name, logos or other of Our trademarks to market
+Your Application, unless otherwise agree by Us in writing.
+
+3. OWNERSHIP
+
+This is a license agreement and not an agreement for sale. We reserve ownership of all intellectual
+property rights inherent in or relating to the Software, which include, but are not limited to, all
+copyright, patent rights, all rights in relation to registered and unregistered trademarks
+(including service marks), confidential information (including trade secrets and know-how) and all
+rights other than those expressly granted by this Agreement.
+
+We may provide You with source code so that You can create Modifications and Applications. While You
+retain all rights to any original work authored by You as part of the Modifications, We continue to
+own all copyright and other intellectual property rights in the Software.
+
+You must not remove, obscure or interfere with any copyright, acknowledgment, attribution,
+trademark, warning or disclaimer statement affixed to, incorporated in or otherwise applied in
+connection with the Software.
+
+4. PROHIBITED USES
+
+You may not redistribute the Software or Modifications other than by including the Software or a
+portion thereof within Your Application. You may not redistribute the Software or Modifications as
+part of any Application that can be described as a development toolkit or library, an application
+builder, a website builder or any Application that is intended for use by software, application, or
+website developers or designers. You may not redistribute any part of the Software documentation.
+You may not change or remove the copyright notice from any of the files included in the Software or
+Modifications.
+
+UNDER NO CIRCUMSTANCES MAY YOU USE THE SOFTWARE FOR AN APPLICATION THAT IS INTENDED FOR SOFTWARE OR
+APPLICATION DEVELOPMENT PURPOSES.
+
+UNDER NO CIRCUMSTANCES MAY YOU USE THE SOFTWARE (INCLUDING WITHOUT LIMITATION THE SOURCE CODE
+THEREOF) AS THE BASIS FOR OR IN CONNECTION WITH A PRODUCT THAT CONTAINS THE SAME, OR SUBSTANTIALLY
+THE SAME, FUNCTIONALITY AS THE SOFTWARE.
+
+You are required to ensure that the Software is not reused by or with any applications other than
+those with which You distribute it as permitted herein. For example, if You install the Software on
+a customer's server, that customer is not permitted to use the Software independently of Your
+Application, and must be informed as such.
+
+5. TERMINATION
+
+This Agreement and Your right to use the Software and Modifications will terminate immediately if
+You fail to comply with any of the terms and conditions of this Agreement. Upon termination, You
+agree to immediately cease using and destroy the Software or Modifications, including all
+accompanying documents. The provisions of sections 4, 5, 6, 7, 8, 9, and 11 will survive any
+termination of this Agreement.
+
+6. DISCLAIMER OF WARRANTIES
+
+TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, WE AND OUR RESELLERS DISCLAIM ALL WARRANTIES AND
+CONDITIONS, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND TITLE AND NON-INFRINGEMENT, WITH REGARD TO
+THE SOFTWARE. WE DO NOT GUARANTEE THAT THE OPERATION OF THE SOFTWARE OR THE CODE IT PRODUCES WILL
+BE UNINTERRUPTED OR ERROR-FREE, AND YOU ACKNOWLEDGE THAT IT IS NOT TECHNICALLY PRACTICABLE FOR US
+TO DO SO.
+
+7. LIMITATION OF LIABILITIES
+
+TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL WE OR OUR RESELLERS BE LIABLE
+UNDER ANY LEGAL OR EQUITABLE THEORY FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES
+WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS
+INTERRUPTION, LOSS OF BUSINESS INFORMATION OR ANY OTHER PECUNIARY LAW) ARISING OUT OF THE USE OF OR
+INABILITY TO USE THE SOFTWARE OR THE CODE IT PRODUCES OR ANY OTHER SUBJECT MATTER RELATING TO THIS
+AGREEMENT, EVEN IF WE OR OUR RESELLERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN ANY
+CASE, OUR ENTIRE LIABILITY WITH RESPECT TO ANY SUBJECT MATTER RELATING TO THIS AGREEMENT SHALL BE
+LIMITED TO THE GREATER OF (I) THE AMOUNT ACTUALLY PAID BY YOU FOR THE SOFTWARE OR (II) ONE HUNDRED
+DOLLARS ($100).
+
+8. PAYMENT AND TAXES
+
+If credit has been extended to You by Us, all payments under this Agreement are due within thirty
+(30) days of the date We mail an invoice to You. If We have not extended credit to You, You shall
+be required to make payment concurrent with the delivery of the Software by Us. Any value added
+tax, use tax, sales tax or similar tax ("Transaction Taxes") shall be your sole responsibility.
+Each party shall pay all taxes (including, but not limited to, taxes based upon its income) or
+levies imposed on it under applicable laws, regulations and tax treaties as a result of this
+Agreement and any payments made hereunder (including those required to be withheld or deducted
+from payments); provided that You shall be responsible for all Transactions Taxes and shall pay or
+reimburse Us for the same upon invoice. Each party shall furnish evidence of such paid taxes as is
+sufficient to enable the other party to obtain any credits available to it, including original
+withholding tax certificates. Notwithstanding the foregoing, Software ordered through Our resellers
+is subject to the fees and payment terms set forth on the applicable reseller invoice.
+
+9. MISCELLANEOUS
+
+The license granted herein applies only to the version of the Software available when purchased in
+connection with the terms of this Agreement, and to any updates and/or upgrades to which you may be
+entitled. Any previous or subsequent license granted to You for use of the Software shall be
+governed by the terms and conditions of the agreement entered in connection with purchase or
+download of that version of the Software. You agree that you will comply with all applicable laws
+and regulations with respect to the Software, including without limitation all export and re-export
+control laws and regulations.
+
+While redistributing the Software or Modifications thereof as part of Your Application, You may
+choose to offer acceptance of support, warranty, indemnity, or other liability obligations and/or
+rights consistent with this Agreement. However, in accepting such obligations, You may act only on
+Your own behalf and on Your sole responsibility, not on our behalf. You shall indemnify Us and our
+resellers, or at Our option, defend Us and our resellers against any claim, suit or proceeding
+brought against Us or our resellers (i) arising by reason of Your accepting any such support,
+warranty, indemnity or additional liability; or (ii) arising out of the use, reproduction or
+distribution of Your Application, except to the extent such claim is solely based on the inclusion
+of the Software therein. Further, You agree only to distribute the Software pursuant to an
+enforceable written agreement for Our benefit that includes all the limitations and restrictions of
+this Agreement and is as protective of Us and Software as is this Agreement. For clarity, You must
+purchase Designated User licenses for each contractor or consultant who uses the Software to create
+an Application on your behalf (including system integrators), whether or not such contractor or
+consultant has its own license to the Software.
+
+You agree to be identified as a customer of ours and You agree that We may refer to You by name,
+trade name and trademark, if applicable, and may briefly describe Your business in our marketing
+materials and web site.
+
+You may not assign or transfer this Agreement without Our prior written consent. This Agreement
+may be assigned by Us in whole or part and will inure to the benefit of Our successors and
+assigns. Notwithstanding the foregoing, in any instance in which You transfer ownership of an
+Application on a work for hire basis, You may assign licenses for the total Designated Users that
+have used the Software to develop said Application under this Agreement to another party (Assignee)
+provided (i) you provide written notice to Us prior to the effective date of such assignment; and
+(ii) there is a written agreement, wherein the Assignee accepts the terms of this Agreement. Upon
+any such transfer, the Assignee may appoint new Designated Users.
+
+You acknowledge that this Agreement is complete and is the exclusive representation of our
+agreement. No oral or written information given by Us, Our resellers, or otherwise on Our behalf
+shall create a warranty or collateral contract, or in any way increase the scope of this Agreement
+in any way, and You may not rely on any such oral or written information. No term or condition
+contained in any purchase order shall have any force or effect.
+
+There are no implied licenses or other implied rights granted under this Agreement, and all rights,
+save for those expressly granted hereunder, shall remain with Us and our licensors. In addition, no
+licenses or immunities are granted to the combination of the Software and/or Modifications, as
+applicable, with any other software or hardware not delivered by Us or Our resellers to You under
+this Agreement. Your rights under this Agreement apply only to Software, Modifications, and/or
+Applications for which all Designated Users are duly licensed hereunder.
+
+If any provision in this Agreement shall be determined to be invalid, such provision shall be
+deemed omitted; the remainder of this Agreement shall continue in full force and effect. If any
+remedy provided is determined to have failed for its essential purpose, all limitations of
+liability and exclusions of damages set forth in this Agreement shall remain in effect.
+
+This Agreement may be modified only by a written instrument signed by an authorized representative
+of each party. The failure of either party to enforce any provision of this Agreement may not be
+deemed a waiver of that or any other provision of this Agreement.
+
+This Agreement is governed by the law of the Province of Alberta, Canada and all parties
+irrevocably submit to the jurisdiction of the courts of the Province of Alberta and further agree
+to commence any litigation which may arise hereunder in the courts located in the judicial district
+of Edmonton, Alberta, Canada.
+
+If the Software or any related documentation is licensed to the U.S. Government or any agency
+thereof, it will be considered to be "commercial computer software" or "commercial computer
+software documentation," as those terms are used in 48 CFR § 12.212 or 48 CFR § 227.7202, and is
+being licensed with only those rights as are granted to all other licensees as set forth in this
+Agreement.
+
+ Copyright 2008-2021 Object.NET, Inc., All rights reserved.
+
+ Object.NET, Inc.
+ +1(888)775-5888
+ licensing@object.net
+ object.net
\ No newline at end of file
diff --git a/node_modules/retypeapp-win-x64/README.md b/node_modules/retypeapp-win-x64/README.md
new file mode 100644
index 0000000..0fe6d0a
--- /dev/null
+++ b/node_modules/retypeapp-win-x64/README.md
@@ -0,0 +1,80 @@
+# Retype - Write anything
+
+[Retype](https://retype.com/) is an :sparkles: ultra-high-performance :sparkles: generator that builds a website based on simple text files. Focus on your writing while Retype builds the rest.
+
+![](https://user-images.githubusercontent.com/62210/151030834-7f7eb27e-8e5c-44a3-bcc9-f0968336111f.png)
+
+No coding is required and just one Markdown file, such as a [`README.md`](https://www.makeareadme.com/), will get you started.
+
+> The [retype.com](https://retype.com/) website was generated using Retype.
+
+A new Retype powered website can be up and running within seconds once Retype is installed, which itself takes only a few seconds. :+1:
+
+## Quick start
+
+You [install](https://retype.com/guides/getting-started/) Retype using [`npm`](https://www.npmjs.com/get-npm), [`yarn`](https://classic.yarnpkg.com/en/docs/install/), or the [`dotnet`](https://dotnet.microsoft.com/download/dotnet-core) CLI.
+
+From your command line, navigate to a folder location where you have one or more Markdown `.md` files, such as a GitHub or GitLab project.
+
+Next, choose one of the following tools to first install `retypeapp` and then start Retype by using the [`retype watch`](https://retype.com/guides/cli/#retype-watch) command:
+
+### NPM
+
+```
+npm install retypeapp-win-x64 --global
+retype watch
+```
+
+### Yarn
+
+```
+yarn global add retypeapp-win-x64
+retype watch
+```
+
+### dotnet
+
+```
+dotnet tool install retypeapp --global
+retype watch
+```
+
+That's it! Your new Retype website should be up and running.
+
+## Features
+
+#### :tada: It just works
+
+Retype has been built to be easy to use and should _"just work"_ out-of-the-box without any special configuration or troublesome setup.
+
+#### :zap: Lightning fast
+
+Don't blink. Retype was built for speed.
+
+#### :white_check_mark: Easy install
+
+[Installation](https://retype.com/guides/getting-started/) takes only a few seconds. Then you need at least one Markdown `.md` file which Retype will start building a new website from.
+
+#### :muscle: Powerful
+
+Project level [configuration](https://retype.com/configuration/project/) using `retype.yml` unlocks many more Retype features and customization.
+
+#### :pencil2: Simple formatting
+
+Pages are [formatted](https://retype.com/guides/formatting/) using Markdown syntax and Retype [components](https://retype.com/components/). Page level [configuration](https://retype.com/configuration/page/) is available, such as customizing the navigation [`label`](https://retype.com/configuration/page/#label) or [`description`](https://retype.com/configuration/page/#description) used by search engines.
+
+#### :arrows_clockwise: Live reload
+
+If a change is detected, such as editing and saving an `.md` file, your Retype website will be updated almost instantly within the browser. After running [`retype watch`](https://retype.com/guides/cli/#retype-watch), edit any `.md` file and see your changes appear in the browser almost instantly.
+
+#### :computer: Host anywhere
+
+Retype generates a basic HTML website that you can self-host on any web hosting service, such as [GitHub](https://docs.github.com/en/pages/quickstart) or [GitLab](https://docs.gitlab.com/ee/user/project/pages/). No special server-side software or external dependencies are required. You can host your Retype site as a public website or as a private website inside your organization.
+
+## Support
+
+Technical support questions are best asked in the [Discussions](https://github.com/retypeapp/retype/discussions). The discussions are monitored 24 hours a day and we will do our best to assist.
+
+If you find a defect or would like to submit a feature request, please create an [Issue](https://github.com/retypeapp/retype/issues) and we will investigate right away.
+
+Do you have a general inquiry? Please feel free to contact us at hello@object.net.
diff --git a/node_modules/retypeapp-win-x64/bin/LICENSE/command-line-api.LICENSE.txt b/node_modules/retypeapp-win-x64/bin/LICENSE/command-line-api.LICENSE.txt
new file mode 100644
index 0000000..cf3ae88
--- /dev/null
+++ b/node_modules/retypeapp-win-x64/bin/LICENSE/command-line-api.LICENSE.txt
@@ -0,0 +1,23 @@
+The MIT License (MIT)
+
+Copyright .NET Foundation and Contributors
+
+All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
\ No newline at end of file
diff --git a/node_modules/retypeapp-win-x64/bin/LICENSE/markdig.LICENSE.txt b/node_modules/retypeapp-win-x64/bin/LICENSE/markdig.LICENSE.txt
new file mode 100644
index 0000000..0b2323f
--- /dev/null
+++ b/node_modules/retypeapp-win-x64/bin/LICENSE/markdig.LICENSE.txt
@@ -0,0 +1,23 @@
+Copyright (c) 2018-2019, Alexandre Mutel
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification
+, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
\ No newline at end of file
diff --git a/node_modules/retypeapp-win-x64/bin/LICENSE/mojee.LICENSE.txt b/node_modules/retypeapp-win-x64/bin/LICENSE/mojee.LICENSE.txt
new file mode 100644
index 0000000..5b6859f
--- /dev/null
+++ b/node_modules/retypeapp-win-x64/bin/LICENSE/mojee.LICENSE.txt
@@ -0,0 +1,252 @@
+Mojee Software License Agreement
+
+Version 1.1.0
+
+THIS DOCUMENT IS A LEGAL AGREEMENT (the "License Agreement") BETWEEN OBJECT.NET, INC. ("We," "Us")
+AND YOU OR THE ORGANIZATION ON WHOSE BEHALF YOU ARE UNDERTAKING THE LICENSE DESCRIBED BELOW ("You",
+"Your") IN RELATION TO THE MOJEE SOFTWARE LIBRARY(IES) (THE "Software"), IN BOTH SOURCE AND OBJECT
+CODE FORM, AND/OR ALL RELATED MATERIALS.
+
+BY DOWNLOADING, INSTALLING, COPYING OR OTHERWISE USING THE SOFTWARE, YOU ACCEPT THE FOLLOWING TERMS
+AND CONDITIONS. IF YOU DO NOT AGREE WITH ANY OF THE TERMS OR CONDITIONS OF THIS LICENSE AGREEMENT,
+DO NOT PROCEED WITH THE DOWNLOADING, COPYING, INSTALLATION OR ANY OTHER USE OF THE SOFTWARE OR ANY
+PORTION THEREOF AS YOU HAVE NO RIGHTS TO DO SO. THE SOFTWARE IS PROTECTED BY UNITED STATES
+COPYRIGHT LAWS AND INTERNATIONAL COPYRIGHT LAWS, AS WELL AS OTHER INTELLECTUAL PROPERTY LAWS AND
+TREATIES. THE SOFTWARE IS LICENSED, NOT SOLD.
+
+THIS LICENSE AGREEMENT DESCRIBES YOUR RIGHTS AND RESTRICTIONS WITH RESPECT TO THE SOFTWARE AND
+ITS COMPONENTS.
+
+1. DEFINITIONS
+
+"Application" means any software, application, or elements that Your Designated Users develop using
+the Software or Modifications in accordance with this Agreement; provided that any such Application
+(i) must have substantially different functionality than the Software, and (ii) must not allow any
+third party to use the Software or Modifications, or any portion thereof, for software development
+or application development purposes.
+
+"Designated User" shall mean a single distinct person for whom You have purchased a license to use
+the Software, whether such person is an employee acting within the scope of their employment with
+You or Your consultant or contractor acting within the scope of the services they provide for You.
+A Designated User can be replaced with a new Designated User only after being a Designated User
+for a minimum of six (6) months.
+
+"End User" means an end user of Your Application who acquires a license to such solely for their
+own internal use and not for distribution, resale, user interface design, or software development
+purposes.
+
+"Modification" means: a) any addition to or deletion from the contents of a file included in the
+original Software or previous Modifications created by You, and/or b) any new file that leverages
+any part of the original Software or previous Modifications.
+
+"Sample Code" means sample source code included with the Software and designated as "sample code,"
+"samples," "sample application code," and/or "snippets," and/or found in directories labeled
+"samples", "learn", "examples" or "examples explorer".
+
+2. LICENSE GRANT
+
+Subject to the payment of the fee required, and subject to your compliance with all of the terms
+and conditions of this Agreement, We grant to You a revocable, non-exclusive, non-transferable and
+non-sublicensable license (i) for Designated User(s) to use the Software to create Modifications
+and Applications; (ii) for You to distribute the Software and/or Modifications to End Users solely
+as integrated into the Applications; and (iii) for End Users to use the Software as integrated into
+Your Applications in accordance with the terms of this Agreement.
+
+In addition to the other terms contained herein, We grant to You a revocable, non-exclusive,
+non-transferable and non-sublicensable license to install and use the Software (the "Free License")
+for Your internal evaluation, review, and production purposes. The Free License may contain
+restricted functionality. You are explicitly not permitted to distribute the Software to any user
+outside the Organization on whose behalf you have undertaken this license. We reserve the right to
+terminate Your License at any time in Our absolute and sole discretion. Without the purchase and
+inclusion of a License Key, the Software may contain restricted functionality, which from
+time-to-time may differ in its limitations. If you wish to remove these restrictions, you are
+required to purchase a Mojee License Key; otherwise you must leave this limitation intact and not
+attempt to modify or circumvent it in any way.
+
+In addition to the other terms contained herein, in the event You have downloaded or received beta
+or pre-release versions of the Software (the "Beta Software") from Us, We grant to You a revocable,
+non-exclusive, non-transferable and non-sublicensable license to install and use the Beta Software
+strictly for Your internal evaluation and review purposes and not for production purposes (the
+"Beta License"). You are explicitly not permitted to distribute the Software to any user outside
+the Organization on whose behalf you have undertaken this license. Your rights to use the Beta
+Software will immediately terminate upon the earlier of (i) the expiration of the evaluation period
+established by Us, or (ii) such time that You purchase a license to a non-evaluation version of the
+Software. We reserve the right to terminate Your Beta License at any time in Our absolute and sole
+discretion.
+
+YOU ACKNOWLEDGE THAT TRIAL AND/OR BETA SOFTWARE MIGHT PLACE WATERMARKS ON OUTPUT, CONTAIN LIMITED
+FUNCTIONALITY, FUNCTION FOR A LIMITED PERIOD OF TIME, OR LIMIT THE FUNCTIONALITY OR TIME OF
+FUNCTIONING OF ANY OUTPUT. ACCESS TO AND/OR USE OF ANY FILES OR OUTPUT CREATED WITH SUCH SOFTWARE
+IS ENTIRELY AT YOUR OWN RISK. WE ARE LICENSING THE SOFTWARE ON AN "AS IS" BASIS AT YOUR OWN RISK
+AND WE DISCLAIM ANY WARRANTY OR LIABILITY TO YOU OF ANY KIND.
+
+You may modify the "Sample Code" solely for the purposes of designing, developing and testing Your
+own Applications. However, You are permitted to use, copy and redistribute Your modified Sample
+Code only if all of the following conditions are met: (a) You include Our copyright notice (if any)
+with Your Application, including every location in which any other copyright notice appears in such
+Application; and (b) You do not otherwise use Our name, logos or other of Our trademarks to market
+Your Application, unless otherwise agree by Us in writing.
+
+3. OWNERSHIP
+
+This is a license agreement and not an agreement for sale. We reserve ownership of all intellectual
+property rights inherent in or relating to the Software, which include, but are not limited to, all
+copyright, patent rights, all rights in relation to registered and unregistered trademarks
+(including service marks), confidential information (including trade secrets and know-how) and all
+rights other than those expressly granted by this Agreement.
+
+We provide You with source code so that You can create Modifications and Applications. While You
+retain all rights to any original work authored by You as part of the Modifications, We continue to
+own all copyright and other intellectual property rights in the Software.
+
+You must not remove, obscure or interfere with any copyright, acknowledgment, attribution,
+trademark, warning or disclaimer statement affixed to, incorporated in or otherwise applied in
+connection with the Software.
+
+You will not owe Us any royalties for Your distribution of the Software in accordance with this
+Agreement.
+
+4. PROHIBITED USES
+
+You may not redistribute the Software or Modifications other than by including the Software or a
+portion thereof within Your Application. You may not redistribute the Software or Modifications as
+part of any Application that can be described as a development toolkit or library, an application
+builder, a website builder or any Application that is intended for use by software, application, or
+website developers or designers. You may not redistribute any part of the Software documentation.
+You may not change or remove the copyright notice from any of the files included in the Software or
+Modifications.
+
+UNDER NO CIRCUMSTANCES MAY YOU USE THE SOFTWARE FOR AN APPLICATION THAT IS INTENDED FOR SOFTWARE OR
+APPLICATION DEVELOPMENT PURPOSES.
+
+UNDER NO CIRCUMSTANCES MAY YOU USE THE SOFTWARE (INCLUDING WITHOUT LIMITATION THE SOURCE CODE
+THEREOF) AS THE BASIS FOR OR IN CONNECTION WITH A PRODUCT THAT CONTAINS THE SAME, OR SUBSTANTIALLY
+THE SAME, FUNCTIONALITY AS THE SOFTWARE.
+
+You are required to ensure that the Software is not reused by or with any applications other than
+those with which You distribute it as permitted herein. For example, if You install the Software on
+a customer's server, that customer is not permitted to use the Software independently of Your
+Application, and must be informed as such.
+
+5. TERMINATION
+
+This Agreement and Your right to use the Software and Modifications will terminate immediately if
+You fail to comply with any of the terms and conditions of this Agreement. Upon termination, You
+agree to immediately cease using and destroy the Software or Modifications, including all
+accompanying documents. The provisions of sections 4, 5, 6, 7, 8, 9, and 11 will survive any
+termination of this Agreement.
+
+6. DISCLAIMER OF WARRANTIES
+
+TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, WE AND OUR RESELLERS DISCLAIM ALL WARRANTIES AND
+CONDITIONS, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND TITLE AND NON-INFRINGEMENT, WITH REGARD TO
+THE SOFTWARE. WE DO NOT GUARANTEE THAT THE OPERATION OF THE SOFTWARE OR THE CODE IT PRODUCES WILL
+BE UNINTERRUPTED OR ERROR-FREE, AND YOU ACKNOWLEDGE THAT IT IS NOT TECHNICALLY PRACTICABLE FOR US
+TO DO SO.
+
+7. LIMITATION OF LIABILITIES
+
+TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL WE OR OUR RESELLERS BE LIABLE
+UNDER ANY LEGAL OR EQUITABLE THEORY FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES
+WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS
+INTERRUPTION, LOSS OF BUSINESS INFORMATION OR ANY OTHER PECUNIARY LAW) ARISING OUT OF THE USE OF OR
+INABILITY TO USE THE SOFTWARE OR THE CODE IT PRODUCES OR ANY OTHER SUBJECT MATTER RELATING TO THIS
+AGREEMENT, EVEN IF WE OR OUR RESELLERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN ANY
+CASE, OUR ENTIRE LIABILITY WITH RESPECT TO ANY SUBJECT MATTER RELATING TO THIS AGREEMENT SHALL BE
+LIMITED TO THE GREATER OF (I) THE AMOUNT ACTUALLY PAID BY YOU FOR THE SOFTWARE OR (II) ONE HUNDRED
+DOLLARS ($100).
+
+8. PAYMENT AND TAXES
+
+If credit has been extended to You by Us, all payments under this Agreement are due within thirty
+(30) days of the date We mail an invoice to You. If We have not extended credit to You, You shall
+be required to make payment concurrent with the delivery of the Software by Us. Any value added
+tax, use tax, sales tax or similar tax ("Transaction Taxes") shall be your sole responsibility.
+Each party shall pay all taxes (including, but not limited to, taxes based upon its income) or
+levies imposed on it under applicable laws, regulations and tax treaties as a result of this
+Agreement and any payments made hereunder (including those required to be withheld or deducted
+from payments); provided that You shall be responsible for all Transactions Taxes and shall pay or
+reimburse Us for the same upon invoice. Each party shall furnish evidence of such paid taxes as is
+sufficient to enable the other party to obtain any credits available to it, including original
+withholding tax certificates. Notwithstanding the foregoing, Software ordered through Our resellers
+is subject to the fees and payment terms set forth on the applicable reseller invoice.
+
+9. MISCELLANEOUS
+
+The license granted herein applies only to the version of the Software available when purchased in
+connection with the terms of this Agreement, and to any updates and/or upgrades to which you may be
+entitled. Any previous or subsequent license granted to You for use of the Software shall be
+governed by the terms and conditions of the agreement entered in connection with purchase or
+download of that version of the Software. You agree that you will comply with all applicable laws
+and regulations with respect to the Software, including without limitation all export and re-export
+control laws and regulations.
+
+While redistributing the Software or Modifications thereof as part of Your Application, You may
+choose to offer acceptance of support, warranty, indemnity, or other liability obligations and/or
+rights consistent with this Agreement. However, in accepting such obligations, You may act only on
+Your own behalf and on Your sole responsibility, not on our behalf. You shall indemnify Us and our
+resellers, or at Our option, defend Us and our resellers against any claim, suit or proceeding
+brought against Us or our resellers (i) arising by reason of Your accepting any such support,
+warranty, indemnity or additional liability; or (ii) arising out of the use, reproduction or
+distribution of Your Application, except to the extent such claim is solely based on the inclusion
+of the Software therein. Further, You agree only to distribute the Software pursuant to an
+enforceable written agreement for Our benefit that includes all the limitations and restrictions of
+this Agreement and is as protective of Us and Software as is this Agreement. For clarity, You must
+purchase Designated User licenses for each contractor or consultant who uses the Software to create
+an Application on your behalf (including system integrators), whether or not such contractor or
+consultant has its own license to the Software.
+
+You agree to be identified as a customer of ours and You agree that We may refer to You by name,
+trade name and trademark, if applicable, and may briefly describe Your business in our marketing
+materials and web site.
+
+You may not assign or transfer this Agreement without Our prior written consent. This Agreement
+may be assigned by Us in whole or part and will inure to the benefit of Our successors and
+assigns. Notwithstanding the foregoing, in any instance in which You transfer ownership of an
+Application on a work for hire basis, You may assign licenses for the total Designated Users that
+have used the Software to develop said Application under this Agreement to another party (Assignee)
+provided (i) you provide written notice to Us prior to the effective date of such assignment; and
+(ii) there is a written agreement, wherein the Assignee accepts the terms of this Agreement. Upon
+any such transfer, the Assignee may appoint new Designated Users.
+
+You acknowledge that this Agreement is complete and is the exclusive representation of our
+agreement. No oral or written information given by Us, Our resellers, or otherwise on Our behalf
+shall create a warranty or collateral contract, or in any way increase the scope of this Agreement
+in any way, and You may not rely on any such oral or written information. No term or condition
+contained in any purchase order shall have any force or effect.
+
+There are no implied licenses or other implied rights granted under this Agreement, and all rights,
+save for those expressly granted hereunder, shall remain with Us and our licensors. In addition, no
+licenses or immunities are granted to the combination of the Software and/or Modifications, as
+applicable, with any other software or hardware not delivered by Us or Our resellers to You under
+this Agreement. Your rights under this Agreement apply only to Software, Modifications, and/or
+Applications for which all Designated Users are duly licensed hereunder.
+
+If any provision in this Agreement shall be determined to be invalid, such provision shall be
+deemed omitted; the remainder of this Agreement shall continue in full force and effect. If any
+remedy provided is determined to have failed for its essential purpose, all limitations of
+liability and exclusions of damages set forth in this Agreement shall remain in effect.
+
+This Agreement may be modified only by a written instrument signed by an authorized representative
+of each party. The failure of either party to enforce any provision of this Agreement may not be
+deemed a waiver of that or any other provision of this Agreement.
+
+This Agreement is governed by the law of the Province of Alberta, Canada and all parties
+irrevocably submit to the jurisdiction of the courts of the Province of Alberta and further agree
+to commence any litigation which may arise hereunder in the courts located in the judicial district
+of Edmonton, Alberta, Canada.
+
+If the Software or any related documentation is licensed to the U.S. Government or any agency
+thereof, it will be considered to be "commercial computer software" or "commercial computer
+software documentation," as those terms are used in 48 CFR 12.212 or 48 CFR 227.7202, and is
+being licensed with only those rights as are granted to all other licensees as set forth in this
+Agreement.
+
+
+ Copyright 2008-2020 Object.NET, Inc., All rights reserved.
+
+ Object.NET, Inc.
+ +1(888)775-5888
+ licensing@object.net
+ object.net
\ No newline at end of file
diff --git a/node_modules/retypeapp-win-x64/bin/LICENSE/scriban.LICENSE.txt b/node_modules/retypeapp-win-x64/bin/LICENSE/scriban.LICENSE.txt
new file mode 100644
index 0000000..28e74c4
--- /dev/null
+++ b/node_modules/retypeapp-win-x64/bin/LICENSE/scriban.LICENSE.txt
@@ -0,0 +1,23 @@
+Copyright (c) 2016-2020, Alexandre Mutel
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification
+, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
\ No newline at end of file
diff --git a/node_modules/retypeapp-win-x64/bin/LICENSE/yamldotnet.LICENSE.txt b/node_modules/retypeapp-win-x64/bin/LICENSE/yamldotnet.LICENSE.txt
new file mode 100644
index 0000000..e63f0bd
--- /dev/null
+++ b/node_modules/retypeapp-win-x64/bin/LICENSE/yamldotnet.LICENSE.txt
@@ -0,0 +1,19 @@
+Copyright (c) 2008, 2009, 2010, 2011, 2012, 2013, 2014 Antoine Aubry and contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
\ No newline at end of file
diff --git a/node_modules/retypeapp-win-x64/bin/retype.exe b/node_modules/retypeapp-win-x64/bin/retype.exe
new file mode 100644
index 0000000..7fc6acf
Binary files /dev/null and b/node_modules/retypeapp-win-x64/bin/retype.exe differ
diff --git a/node_modules/retypeapp-win-x64/package.json b/node_modules/retypeapp-win-x64/package.json
new file mode 100644
index 0000000..18b4c28
--- /dev/null
+++ b/node_modules/retypeapp-win-x64/package.json
@@ -0,0 +1,21 @@
+{
+ "name": "retypeapp-win-x64",
+ "version": "3.5.0",
+ "description": "Retype CLI.",
+ "main": "retype.js",
+ "bin": {
+ "retype": "retype.js"
+ },
+ "directories": {
+ "bin": "bin"
+ },
+ "scripts": {
+ "test": "echo \"Error: no test specified\" && exit 1"
+ },
+ "keywords": [
+ "documentation",
+ "api docs"
+ ],
+ "author": "Object.NET, Inc",
+ "license": "See LICENSE IN LICENSE"
+}
\ No newline at end of file
diff --git a/node_modules/retypeapp-win-x64/retype.js b/node_modules/retypeapp-win-x64/retype.js
new file mode 100644
index 0000000..920c8de
--- /dev/null
+++ b/node_modules/retypeapp-win-x64/retype.js
@@ -0,0 +1,39 @@
+#!/usr/bin/env node
+const spawn = require('child_process').spawn;
+const path = require('path');
+
+var execPath = path.resolve(path.join(__dirname, './bin', './retype'))
+var args = [];
+
+var verbose = false,
+ reading_args = true;
+if (process.argv.length > 2) {
+ for (var i = 2; i < process.argv.length; i++) {
+ var arg = process.argv[i];
+ if (arg == "--") {
+ reading_args = false;
+ } else if (reading_args && process.argv[i] == "--verbose") {
+ verbose = true;
+ }
+
+ args.push(process.argv[i]);
+ }
+}
+
+function verboseLog(message) {
+ if (verbose) {
+ console.log("Node.JS wrapper: " + message);
+ }
+}
+
+function cleanQuit(code) {
+ verboseLog("exiting with status " + code + ".");
+ process.exit(code);
+}
+
+var processHandle = spawn(execPath, args, { stdio: 'inherit' });
+
+// Continue execution on SIGINT; Retype is supposed to handle it.
+process.on("SIGINT", () => {});
+
+processHandle.on('exit', (code, signal) => cleanQuit(code));
\ No newline at end of file
diff --git a/package-lock.json b/package-lock.json
new file mode 100644
index 0000000..14ad4f5
--- /dev/null
+++ b/package-lock.json
@@ -0,0 +1,20 @@
+{
+ "name": "bonares-handbook",
+ "lockfileVersion": 3,
+ "requires": true,
+ "packages": {
+ "": {
+ "dependencies": {
+ "retypeapp-win-x64": "^3.5.0"
+ }
+ },
+ "node_modules/retypeapp-win-x64": {
+ "version": "3.5.0",
+ "resolved": "https://registry.npmjs.org/retypeapp-win-x64/-/retypeapp-win-x64-3.5.0.tgz",
+ "integrity": "sha512-II9fqg6gBBiCdlJ2n5EB89dNusgko9D2qKXaqCgCPuNOS7c7rMgL5bORt3r8mVWbL25gC1U+40KNuchYuzUpvQ==",
+ "bin": {
+ "retype": "retype.js"
+ }
+ }
+ }
+}
diff --git a/package.json b/package.json
new file mode 100644
index 0000000..086ae6d
--- /dev/null
+++ b/package.json
@@ -0,0 +1,5 @@
+{
+ "dependencies": {
+ "retypeapp-win-x64": "^3.5.0"
+ }
+}
diff --git a/readme.md b/readme.md
new file mode 100644
index 0000000..7d11c6b
--- /dev/null
+++ b/readme.md
@@ -0,0 +1,5 @@
+
+
+
+
+# Practical handbook for publishing research data in the BonaRes Repository – Tips & Tricks
\ No newline at end of file
diff --git a/src/_includes/head.html b/src/_includes/head.html
new file mode 100644
index 0000000..9a746d4
--- /dev/null
+++ b/src/_includes/head.html
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/src/creation_of_templates/data_publication.md b/src/creation_of_templates/data_publication.md
new file mode 100644
index 0000000..a208577
--- /dev/null
+++ b/src/creation_of_templates/data_publication.md
@@ -0,0 +1,245 @@
+---
+label: Data Publication
+order: 30
+---
+
+# Data Publication
+
+The publication of research is a central issue in science. Beside traditional scientific papers, data publication became
+more important in the past years. Research data are stored and published by data journals, central (thematic) data
+repositories or in open databases (e.g., university). To provide proper findability, reusability and citeability of these data,
+(persistent) identifiers are necessary, e.g. to assign data sets or authors to research. Most significant is the:
+
+
+
+### DataCite, DOI
+
+The DOI system became the standard for information and documentation **(ISO 26324:2012)**. In the DOI system the object is
+identified unambiguously to its institution (prefix). There is no limit of the length of either suffix or prefix.
+For example, all DOI, which are provided by BonaRes Data Centre, have the prefix: _10.20387_. Metadata can be associated with the object.
+
+
+
+_Persistent identifier (PI)_
+
+Persistent individual digital identifiers for authors and researchers can be used as name lists for creator
+and contributor names e.g. in DataCite. Examples are:
+
+[ORCID](https://orcid.org) (Open Researcher and Contributor ID), [Scopus](https://www.scopus.com/home.uri) (Elsevier),
+[Publons](https://publons.com/wos-op/) (Clarivate Analytics, Thomas Reuters), [LinkedIn](http://www.linkedin.com/),
+[ResearchGate](https://www.researchgate.net), **ISNI** (ISO 27729:2012 International Standard Name Identifier) and the
+[Handle](http://www.handle.net) system. The last was implemented into the digital object identifier (DOI),
+specified by the US-standard **ANSI/NISO Z39.84-2005** and managed by the DOI Foundation. Further PIs are Persistent URL (**PURL**),
+Uniform Resource Name (**URN**), Archival Resource Keys (**ARK**), and Extensible Resource Identifier (**XRI**).
+More information is given by Juha Hakala, 2010 [[1]](http://www.persid.org/downloads/PI-intro-2010-09-22.pdf).
+
+
+
+_Taxonomies for author contributions to science_
+
+### CRediT (Contributor Roles Taxonomy)
+
+This taxonomy aims to provide transparency to the contributions of researchers to published work, to enable discoverability
+and to improve attribution, credit, and accountability. There are 14 categories defined for author’s contribution.
+
+
+
+### IGSN (International Geo Sample Number)
+
+Alphanumeric code to provide transparency to the contributions of researchers to scholarly published work,
+to enable discoverability and to improve attribution, credit, and accountability.
+
+
+
+
+## Data journals and publication portals:
+#### (selected overview)
+
+A review of efficient and enhanced publishing, dissemination, sharing and reuse of bio-diversity data are given
+by Chavan and Penev (2011) [[2]](https://doi.org/10.1186/1471-2105-12-S15-S2). Data publication in data journals are
+classified as “pure” publish data papers only and journals classified as “mixed” publish both.
+
+
+
+### [Biodiversity Data Journal](https://bdj.pensoft.net)
+#### (Pensoft)
+
+This journal is community peer-reviewed and Open-Access. It is in accordance with the Data Publishing Policies and
+Guidelines of Pensoft Publishers. Important standards for this Journal: related data must have DOI or other persistent identifier, XML.
+
+
+
+### [CODATA Data Science Journal](https://datascience.codata.org)
+#### (Ubiquity Press)
+
+This open access and peer-reviewed data journal is open for papers on data management,
+(re)use and databases across all research domains, technology and arts.
+
+
+
+### [Earth System Science Data ](https://www.earth-system-science-data.net)
+#### (Copernicus Publications)
+
+International, interdisciplinary journal for the publication of articles on original research data (sets).
+Important standards for this Journal: Dataset with persistent identifier; [OAI-PMH](https://www.openarchives.org/pmh/);
+Metadata in Dublin Core format (oai-dc), full-text XML.
+
+
+
+### [Ecological Archives / Data Papers](https://esapubs.org/archive/)
+#### (Ecologigal Society of America, ESA)
+
+Provides and hosts supplemental material to ESA articles. Data is registered in official Data Registry of the ESA.
+Data are fully peer reviewed, technical review of data and metadata. Data ingest as text format.
+Important standards for this Journal: Metadata following [[3]](https://doi.org/10.2307/2269427).
+
+
+
+### [F1000 Research ](https://f1000research.com)
+#### (F1000 Research Ltd, Science Navigation Group)
+Data articles are citable and authors are credited when data are reused. Important standards for this Journal:
+CC0, no explicit standards but guidelines for different datasets, metadata of date linked to the journal should be,
+when possible, in standardized machine readable formats (DataCite). Mostly DataCite as well as DOI were important
+standards used in these Journals. The most important Persistent Identifier (PI) used is the DOI.
+
+
+
+### [Geoscience Data Journal](https://rmets.onlinelibrary.wiley.com/journal/20496060) (Wiley)
+
+Open Access with scientific peer-review. Important standards for this Journal: Linked data must be stored in an
+approved repository and assigned with DOI.
+
+
+
+### [GigaScience](https://academic.oup.com/gigascience) / [BioMed Central](https://www.biomedcentral.com)
+
+Is an open access, open-data and open peer-review journal concerning research from life and biomedical science.
+
+
+
+### [Hindawi publishing ](https://www.hindawi.com/journals/dpis/)
+#### (Hindawi Publishing Corporation)
+
+Was a peer-reviewed and open access journal with dataset papers in all areas of geoscience. The journal ceased new publications in 2017. Important standards for this journal: Content is archived in Portico, LOCKSS.
+
+
+
+### [Journal of Open Research Software ](https://openresearchsoftware.metajnl.com)
+#### (JORS, Software Sustainability Institute)
+Publish peer-reviewed (meta-)papers describing research software.
+
+
+
+### [Journal of Physical and Chemical Research Data ](https://aip.scitation.org/journal/jpr)
+#### (AIP Publishing LLC)
+
+Published by the American Institute of Physics (AIP) for the National Institute of Standards and Technology (NIST); reviews of measurement techniques, critical data evaluation. Important standards for this Journal: Standard Reference Data Act (Public Law 90-396); Article and supplemented material with DOI.
+
+
+
+### [OpenAgrar](https://www.openagrar.de/content/index.xml)
+
+This repository collects, disseminates and archives publications, including articles, poster, data, books and interviews from different agricultural research institutes in Germany.
+
+
+
+### [Open Data Journal for Agricultural Research](https://odjar.org/index)
+
+Is an open access data journal is a hub for storing, curating and publishing agricultural research data sets.
+
+
+
+### [Publisso](https://www.publisso.de)
+
+This open access publication portal is operated by ZB MED and provides different publication platforms for scientists, such as journals, books, congresses videos and repositories.
+
+
+
+
+
+## Data repositories:
+#### (selected overview)
+
+There are numerous repositories for research data, provided by the private or public domain.
+Objective of all repositories is to store, archive, manage and/or provide data to the scientific community,
+scientists and/or institutions. An overview and recommendations of over 2,000 repositories available are published by re3data.org
+(full scale resource of registered repositories across subject areas).
+
+
+
+### [B2FIND](http://b2find.eudat.eu)
+
+This tool helps to find and harvest metadata from EUDAT data centres and other repositories.
+
+
+
+### [BonaRes Data Portal](https://maps.bonares.de/mapapps/resources/apps/bonares/index.html?lang=en)
+
+Is the web platform that gives access to soil- and agricultural research data. Uploaded data can be found using the spatial,
+temporal and thematic search options.
+
+
+
+### [CGIAR](https://www.cgiar.org)
+
+The CGIAR provides different tools to capturing data and managing experiment and agricultural data, e.g. via
+[Field Book ](https://excellenceinbreeding.org/toolbox/tools/field-book)Registry.
+
+
+
+### [Dryad Digital Repository](https://datadryad.org/stash)
+
+Dryad is a nonprofit membership organization which governs this data repository. It is a curated open resource for data
+underlying scientific publications.
+
+
+
+### [EOSC](https://eosc-portal.eu)
+
+The European Open Science Cloud initiative set-up an infrastructure for research data and a knowledge portal for scientists.
+
+
+
+### [OpenAIRE](https://www.openaire.eu)
+
+This Open-Access infrastructure (EU - [Funding Program Horizon 2020](https://research-and-innovation.ec.europa.eu/funding/funding-opportunities/funding-programmes-and-open-calls/horizon-2020_en))
+explore publications and data sets, align policies, link research and repositories, and train researchers for open science.
+
+
+
+### [PANGAEA](https://www.pangaea.de)
+#### (Data publisher for earth & environmental science)
+
+Is an open access library, data publisher and archive for geo-data in earth- and life sciences.
+Data are easily accessible, citable and are managed free of charge for data provider and data user.
+
+
+
+### [Scholix](http://www.scholix.org)
+#### (Scholarly Link eXchange)
+
+This initiative links and connects data and metadata. It aims to establish an interoperability framework information
+exchange between literature and data and to set-up an open information framework to describe and understand what data
+underpins literature and what literature references data.
+
+
+
+## Conflicts and solutions
+
+While the expression of DOI as URN is possible, conversions from DOI into other systems, such as XRI or ARK, are difficult
+or impossible, respectively. In contrast to URN, DOI goes beyond identifying an electronic manifestation of a resource.
+The DOI-prefix also identifies the location of access.
+
+:::bonares_reference
+
+### References
+
+[1] Hakala, J. (2010). Persistent identifiers: an overview. KIM Technology Watch Report.
+
+[2] Chavan, V. and L. Penev (2011). The data paper: a mechanism to incentivize data publishing in biodiversity science.
+Bmc Bioinformatics 12.
+
+[3] Michener, W. K., J. W. Brunt, J. J. Helly, T. B. Kirchner and S. G. Stafford (1997).
+Nongeospatial metadata for the ecological sciences. Ecological Applications 7(1): 330-342.
+
+:::
\ No newline at end of file
diff --git a/src/creation_of_templates/geo_data_services.md b/src/creation_of_templates/geo_data_services.md
new file mode 100644
index 0000000..96f94e0
--- /dev/null
+++ b/src/creation_of_templates/geo_data_services.md
@@ -0,0 +1,85 @@
+---
+label: Geo-data Services
+order: 40
+---
+# Geo-data Services
+
+Geo-data service provides access to a geo-database by local area network (LAN) or the internet using ArcGIS server
+or open-source GIS servers, i.e., geo server to view, search and queries into database.
+Open Geospatial Consortium (OGC) regulates rules and standards for geo-data services. So called “OGC services” are listed
+in this chapter. They are widely accepted and applied by geo-data providers and users. Requirements, types and structure
+of services are defined in **EN ISOS 19119:2016** and **ISO 19133:2007** (data types, operations and implementation).
+
+
+
+### Overview of existing standards
+
+All OGC standards on web services (OWS) and supporting documents are available to the public at no cost, e.g.:
+
+
+
+### WMS (Web Map Service) ![](/static/img/two_star.png)
+
+WMS offer geo-registered map images in different format (e.g. JPEG, PNG) from distributed geo-database system through GIS servers.
+It is basically a HTTP/HTTPS link, which provides different request types, two of which are required by any WMS server:
+GetCapabilities and GetMap, defines a certain geographic location and layer(s) to be managed. Request types that WMS
+optionally support include: _GetFeatureInfo, DescribeLayer_ and _GetLegendGraphic_ ([OpenGeoSpatial](https://www.ogc.org/standards/wms)).
+Rules and applications of WMS are provided by **EN ISO 19128:2008**.
+
+
+
+### WFS (Web Feature Service) ![](/static/img/two_star.png)
+
+WFS allow any usage that might work with web services to get geographic features from one or more distributed spatial
+information system or a map itself. Similar to WMS (mapping output as an image), WFS deal with create, update, delete
+and query functions of feature instances from regarding database. WFS serve eight general operations:
+_Capabilities, DescribeFeatureType, DescribeFilterModel, Feature, FeatureWithLock, Property, LockFeature_ and _Transaction_.
+Rules and applications of WFS are provided by **EN ISO 19142:2010**.
+
+
+
+### WCAS (Web Catalogue Service) ![](/static/img/two_star.png)
+#### Also known as: CSW, Catalogue Services for the Web
+
+CSW service provides options to publish and searching capabilities of metadata about geospatial data, services, and related
+information objects. Request types that CSW services offers include: _GetCapabilities, DescribeByRecord, GetRecords, GetRecordById,
+GetDomain, Harvest_ and _Transaction_. Requests can encode the parameters in three different ways: GET with URL parameters,
+POST with form-encoded payload and POST with XML payload.
+
+
+
+### WCS (Web Coverage Service) ![](/static/img/two_star.png)
+
+WCS returns the original data with its descriptions along with actual semantics. This service allows access into coverage data for client-side rendering. WCS also offers clients to get information of a certain portions based on constraints and certain criteria, similar to WFS and WMS service.
+
+
+
+### WMTS (Web Map Tile Service) ![](/static/img/two_star.png)
+
+WMTS makes detailed rendering of a raster data or a large volume of vector data in tiles which supports Key-Value-Pair
+(KV, process oriented) encoding interfaces, REST (Representational state transfer) encoding and SOAP encoding.
+
+
+
+### TJS (Table Joining Service) ![](/static/img/two_star.png)
+
+The TJS standard joins attribute data with its associated geospatial framework. Attribute data can be stored in one
+network and mapped with geographic data into another network which contains geometries for the attribute data.
+TJS provides simple web-based services for searching, accessing and using attribute data from different sources which
+can generate database, perform analysis and populate maps.
+
+
+
+### WMC (Web Map Context) ![](/static/img/two_star.png)
+
+The OGC XML file standard WMC describes meta-information of a WMS (e.g. the URL, different layers within the service,
+bounding box rectangle, coordinate system) in XML file, stores and loads XML schema which belongs to it.
+
+
+
+### WPS (Web Processing Service) ![](/static/img/two_star.png)
+
+WPS service defines how to implement a geoprocessing service, geographic calculations or models as a service.
+It offers simple web-based standardized method of finding, accessing and using of geoprocessing services,
+at the same time also direct requests and responses of those services. WPS uses HTTP GET, HTTP POST,
+SOAP and XML as a mechanism for describing the data and for interoperability.
diff --git a/src/creation_of_templates/index.md b/src/creation_of_templates/index.md
new file mode 100644
index 0000000..03514e3
--- /dev/null
+++ b/src/creation_of_templates/index.md
@@ -0,0 +1,20 @@
+---
+label: Data Provision
+icon: download
+expanded: true
+order: 110
+---
+# Data Provision
+
+Structured research data, reasonably described by standardized metadata facilitates its provision and increase its
+visibility. Open metadata, free and widely accepted geo-data protocols and accepted licenses facilitate data queries and
+access for user.
+
+This chapter provides an overview of metadata standards, possibilities for data publication, accepted licenses and
+thesauri and ontologies as applied in soil and agricultural science.
+
+[!ref](/data_provision/metadata.md)
+[!ref](/data_provision/geo_data_services.md)
+[!ref](/data_provision/data_publication.md)
+[!ref](/data_provision/licenses.md)
+[!ref](/data_provision/thesauri_&_ontologies.md)
\ No newline at end of file
diff --git a/src/creation_of_templates/licenses.md b/src/creation_of_templates/licenses.md
new file mode 100644
index 0000000..d496098
--- /dev/null
+++ b/src/creation_of_templates/licenses.md
@@ -0,0 +1,51 @@
+---
+label: Licenses
+order: 20
+---
+
+# Licenses
+
+License information for research data and metadata is important because it informs users what they allowed to do with
+data and metadata. Without an explicit license, reuse is restricted. Licenses should not be created individually but
+existing licenses should be used.
+
+
+
+_Overview of existing standards_
+
+### Creative Commons (CC) ![](/static/img/two_star.png)
+
+[Creative Commons](https://creativecommons.org) is a global nonprofit organization that enables sharing and reuse of
+creativity and knowledge through the provision of free legal tools. Current version is 4.0. The standard license for all
+research data stored in the BonaRes repository is CC-BY that facilitates maximum distribution and usage of data.
+
+
+
+### Datenlizenz Deutschland ([Data License Germany](https://www.govdata.de/lizenzen)) ![](/static/img/one_star.png)
+Was created by federal and state governments in Germany during the work at the Open Data Portal and has been specially
+developed for administrative data. Current version is 2.0.
+
+
+
+### GeoLizenz ![](/static/img/one_star.png)
+This license was developed by the German GeoBusiness Commission (GIW-Kommission), which was founded by the Federal Ministry
+for Economic Affairs and Energy. The license is intended for geo-data, metadata and geo-data services.
+
+
+
+### GNU General Public License ![](/static/img/one_star.png)
+[GNU](https://www.gnu.org/licenses/gpl-3.0.en.html) is intended to guarantee freedom to share and change all versions
+of a program and to make sure it remains free software for all its users.
+
+
+
+### Open Data Commons (ODC) ![](/static/img/one_star.png)
+Open Data Commons is a project of the Open Knowledge Foundation with the aim to provide legal solutions for open data:
+[Open Database License ](https://opendatacommons.org/licenses/odbl/)(ODbL) and [Attribution License](https://opendatacommons.org/licenses/by/).
+
+
+
+### Open Software License (OSL-3.0) ![](/static/img/one_star.png)
+[OSL](https://opensource.org/licenses/OSL-3.0) applies to any original work of authorship whose owner has placed the
+following licensing notice adjacent to the copyright notice for the Original Work:
+“Licensed under the Open Software License version 3.0”.
diff --git a/src/creation_of_templates/metadata.md b/src/creation_of_templates/metadata.md
new file mode 100644
index 0000000..c5bceb2
--- /dev/null
+++ b/src/creation_of_templates/metadata.md
@@ -0,0 +1,140 @@
+---
+label: Metadata
+order: 50
+---
+# Metadata
+
+A key precondition to store and share data and to fulfil the FAIR data principles (see Introduction) is the proper
+description of research data by metadata. When set-up an own interoperable metadata schema for a data repository it is
+very important to use assignable elements of widespread and open metadata standards.
+
+
+
+_Overview of existing standards_
+
+Standards only dealing with metadata for diverse purposes and are published by ISO. Metadata for geographic information
+are regulated in **ISO 19115-1ff** series (Geographic information - Metadata). ISO 19115-1:2014 and -2:2009 contain many code
+lists on identification information, geometry types and other relevant topics.
+
+Requirements for metadata related to geographic information services are defined in **EN ISO 19119:2016**.
+A technical guideline for encoding of metadata using a XML-schema is provided by **ISO/TS 19139-1:2019-03** (XML schema implementation).
+Regulations for metadata are also part of other standards that relate to soil data, for example **INSPIRE DS Soil** or **ISO 28258:2013**.
+
+The German Infrastructure for Spatial Information (GDI-DE) requires the application of ISO 19115, 19119 and 19139
+in the context of INSPIRE for acquisition and support of metadata. For such purposes the Drafting Team Metadata and
+European Commission Joint Research Centre published a technical guideline with INSPIRE implementing rules for metadata [[1]](https://inspire.ec.europa.eu/documents/Metadata/INSPIRE_MD_IR_and_ISO_v1_2_20100616.pdf).
+
+The Digital Curation Centre (DCC) provides a [list](https://www.dcc.ac.uk/guidance/standards/metadata/list) of common metadata standards.
+
+The [BonaRes Metadata Schema](https://tools.bonares.de/doi) [[2]](https://doi.org/10.1016/j.cageo.2019.07.005) ![](/static/img/two_star.png) has been created by combining elements of the two schemes INSPIRE (EU)
+and DataCite (DOI) since few relevant elements within these two standards have been found.
+
+
+
+### INSPIRE (European Union) ![](/static/img/two_star.png)
+
+The INSPIRE directive contains metadata elements on dataset-level that should be applied for documenting metadata for an
+entire dataset or a dataset series. Metadata can also be stored on object-level. This means that metadata can be described
+for each individual spatial object. Due to the product-oriented approach of INSPIRE, metadata provide not only information
+on data quality and validity, but also on conditions for accessibility, use of data, access restriction (including reasons) and charges.
+
+
+
+### DataCite ![](/static/img/two_star.png)
+
+The DataCite was developed to provide easy access to scientific data over internet. It provides domain agnostic services
+which belongs to the concept of a long term or _persistent_ identifier. DataCite is using _Digital Object Identifiers_ (DOIs)
+to register a resource associated with metadata. The objective of DataCite is to increase the acceptance of research data
+as legitimate, citable contributions to the scientific record and to archive data for future study. Besides a wide range
+of metadata elements, DataCite provides the opportunity to acknowledge contributions of disciplinary work. To enable an
+accurate and consistent identification of a resource (e.g. for citation) the metadata scheme offers a list of essential
+metadata properties. The da|ra is the DOI registration agency for social and economic research data.
+The recent Metadata Scheme is 4.4 [[3]](https://schema.datacite.org/meta/kernel-4.4/).
+
+
+
+### Dublin Core Metadata Element Set (Version 1.1) ![](/static/img/one_star.png)
+
+This set is a vocabulary of fifteen properties to describe a resource. It is maintained by the Dublin Core Metadata Initiative
+(DCMI). The Dublin Core metadata elements formally endorsed in **ISO 15836-1:2017 and ISO 15836-2:2019, ANSI/NISO Z39.85-2012**
+and **RFC 5013** [[4]](https://www.rfc-editor.org/rfc/rfc5013.html).
+
+
+
+### DDI
+#### (Data Documentation Initiative)
+
+Open standard (metadata model) to describe social and economic research data and survey data. Basic concept is the description
+of the complete Data Life Cycle with XML.
+
+
+
+### GESIS
+#### (Leibniz-Institute for the Social Sciences)
+
+In line with DDI, presentation of detailed metadata and standards for surveys and interviews, e.g. in the following
+technical reports: Zenk-Möltgen and Habbel 2012 [[5]](https://www.gesis.org/fileadmin/upload/forschung/publikationen/gesis_reihen/gesis_methodenberichte/2012/TechnicalReport_2012-01.pdf),
+Jensen and Schweers 2014 [[6]](https://www.ssoar.info/ssoar/bitstream/handle/document/40297/ssoar-2014-jensen_et_al-Das_erweiterte_Metadatenschema_der_VFU.pdf?sequence=1).
+
+
+
+### METS
+#### (Metadata Encoding & Transmission Standard)
+
+This is a standard for coding and management of metadata from digital or analogue sources of different formats
+(picture, text, audio, video…). Precondition are beside others sections for the presentation of the internal structure
+of a digital object, group related files, technical metadata, and information about the source.
+METS documents can link and integrate different metadata (e.g. from PREMIS, Dublin CORE or MARC).
+
+
+
+### PREMIS
+#### (PREservation Metadata: Implementation Strategies)
+
+Initiative for the development and maintenance of internationally recognized long-term archiving metadata standards.
+PREMIS aims to develop recommendations, suggestions and best practices for implementing preservation metadata,
+further development of the standards, as well as the connection to other standards.
+
+
+
+### Quali-Service (University of Bremen)
+Emerging [data service center ](https://www.qualiservice.org/de/)for qualitative primary data (focus on interviews)
+and provision of reports about metadata standards, e.g. Betancort Cabrera and
+Haake 2014 [[7]](https://media.suub.uni-bremen.de/handle/elib/3020).
+
+
+
+### Conflicts and solutions
+
+### INSPIRE vs. ISO Metadata
+
+The problematic issue of metadata and data is that almost any piece of data can be metadata in a more specific context.
+In the application schema of ISO 28258 any piece of information that can be handled as data should at least be handled as data,
+but can additionally be handled as metadata. According to ISO 28258 information e.g. on projects or soil maps can be described
+as data (in the form of features) or metadata. In line with INSPIRE this information is metadata of a dataset [[8]](https://tools.bonares.de/media/bonares_series/BonaRes-5PGG-8YRP.pdf).
+
+
+
+:::bonares_reference
+
+### References
+[1] JRC (2007, update 2013). "INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO
+19119." from click here
+
+[2] Specka X., Gärtner, P., Hoffmann, C., Svoboda, N., Stecker, M., Einspanier, U., Senkler, K., Zoarder, M.A.M.,
+Heinrich, U. (2019): The BonaRes metadata schema for geospatial soil-agricultural research data - Merging INSPIRE and
+DataCite metadata schemes. Computers and Geosciences 132: 33-41
+
+[3] Group, DataCite Metadata Working (2021). DataCite Metadata Schema Documentation for the Publication and Citation of Research Data (v4.4).
+
+[4] Kunze, J. and T. Baker (2007). IETF RFC 5013. The Dublin Core Metadata Element Set.
+
+[5] Zenk-Möltgen, W., & Habbel, N. (2012). Der GESIS Datenbestandskatalog und sein Metadatenschema: Version 1.8.
+
+[6] Jensen, U., & Schweers, S. (2014). Das erweiterte Metadatenschema der VFU soeb 3.
+
+[7] Betancort Cabrera, N. (2014). Das Qualiservice Metadatenschema: Version 1.1. Qualiservice Technical Reports
+
+[8] Gärtner, P., N. Svoboda, T. Kühnert, M.A.M. Zoarder and U. Heinrich (2017). The BonaRes Metadata Schema.
+BonaRes Data Centre. DOI: 10.20387/BonaRes-5PGG-8YRP
+:::
\ No newline at end of file
diff --git a/src/creation_of_templates/thesauri_&_ontologies.md b/src/creation_of_templates/thesauri_&_ontologies.md
new file mode 100644
index 0000000..3225cc2
--- /dev/null
+++ b/src/creation_of_templates/thesauri_&_ontologies.md
@@ -0,0 +1,307 @@
+---
+label: Thesauri and Ontologies
+order: 10
+---
+
+# Thesauri and Ontologies
+
+The use of controlled vocabularies with standardized, generally accepted and clearly assigned identifiers, definitions
+and semantics are necessary for smooth data integration and to allow human- and machine readable exchange, query and
+reproduction of information. Semantic data annotation by controlled vocabularies is precondition to provide interoperability
+of data repositories. Standardizes ontologies enable integration of data and information to the Semantic Web.
+
+To link data and ensure its reusability it is important that thesauri are published online, using an open license and
+endowed with an URI ([W3C](https://www.w3.org/TR/2014/NOTE-ld-bp-20140109/), Best Practices for Publish Linked Data, 2014).
+General information for development and operate thesauri are described in **ISO 25964 - Information and documentation –
+Thesauri & interoperability with other vocabularies**![](/static/img/two_star.png), that is published in two parts:
+
+- **1:2011 Thesauri for information retrieval**
+This is part one of an international standard for thesauri, that is published in two parts. It provides recommendations
+for the development and maintenance of thesauri intended for information retrieval applications. It is applicable to
+vocabularies about all types of information resources including knowledge bases and portals, bibliographic databases, text,
+etc. It provides a data model and recommended format for the import and export of thesaurus data and can be applied for
+monolingual and multilingual thesauri. Based on the data model it includes also an XML schema for data exchange.
+
+- **2:2013 Interoperability with other vocabularies**
+Provides guidelines for high quality information retrieval across networked resources that have been indexed with different
+vocabularies or Knowledge Organization Systems (KOS). It helps to set up mappings between different concepts
+(classification schema, taxonomies, subject heading schemas, ontologies, name authority lists, terminologies and synonym rings).
+
+
+
+## Overview of controlled vocabularies in agricultural and environmental science
+
+### [AGROVOC](http://aims.fao.org) ![](/static/img/two_star.png)
+
+Is a multilingual vocabulary developed by the FAO. It defines and relates more than 36,000 concepts in 33 languages.
+The thesaurus is updated on a monthly basis. It is published as an RDF/SKOS-XL concept schema and accessible as Linked
+Data via SPARQL-endpoint. The thesaurus is aligned with 16 vocabularies as related to agriculture. Editing is possible for
+registered users through the web-based editing tool VocBench 3. AGROVOC is released under the license CC-BY IGO 3.0 and
+published by the web-based SKOS browser “Skosmos”. The JAVA Command Line application “AgroTagger”![](/static/img/one_star.png)
+assigns and index semantic terms to textual content and as a keyword extractor from a set of web URLs. It allows to index
+web documents identifying main topics and creating RDF triples that link a Web URL to AGROVOC URIs.
+
+
+
+### [GEMET](https://www.eionet.europa.eu/gemet/en/about/) ![](/static/img/two_star.png)
+#### (General Multilingual Environmental Thesaurus)
+
+This thesaurus was developed by the European Environmental Information and Observation Network (EIONET). It summarizes
+different structured vocabularies and aims to define a common terminology for environmental terms in the European context.
+It is available in more than 27 languages and consists of more than 6000 records. At least one GEMET keyword is required
+to be conform to the INSPIRE metadata schema for geospatial data (ISO 19115, ISO 19119, ISO 19139).
+
+
+
+### AgrO ![](/static/img/one_star.png)
+The Agronomy Ontology (AgrO) is develoed by CGIAR and describes agronomic practices, techniques and variables used in
+agronomic experiments. AgrO use traits, ICASA variables, and other existing ontologies. In March 2019 it was in the alpha
+phase and nit released officially.
+
+
+
+### BCO ![](/static/img/one_star.png)
+The application ontology Biological Collections Ontology (BCO) includes semantics relations on biodiversity, museum collections,
+environmental samples, and ecological surveys.
+
+
+
+### [CAB Thesaurus](https://www.cabi.org/cabithesaurus/) ![](/static/img/one_star.png)
+This open access, multi-lingual thesaurus is operated by CAB International (CABI) science-based organization and includes
+almost 3 million terms in world’s science and technical fields. It includes some 250,000 plant, animal and microorganism names.
+
+
+
+### [Crop Ontology](https://cropontology.org) ![](/static/img/one_star.png)
+This ontology includes a large database with ontologies of crops and crop-related terms, structured in the categories
+phenotype, breeding, germplasm and trait. Terms are defined by a unique combination of trait, method used and scale.
+It is open access and open to improve by the crop community.
+
+
+
+### [EUROVOC](https://op.europa.eu/en/web/eu-vocabularies)
+This multilingual thesaurus maintained by the Publications Office of the European Union for indexing of documents of European institutions. It is available in 24 languages.
+
+
+
+### GCMD ![](/static/img/one_star.png)
+#### Global Change Master Directory
+This directory was developed by NASA and can be implemented as thesaurus into a database. Keywords are provided in different
+scientific disciplines such as agriculture, atmosphere and hydrology.
+
+
+
+### ISO 11074:2015 ![](/static/img/one_star.png)
+#### Soil quality, Vocabulary
+This standard summarizes all relevant terms of soil science in a glossary and is available in a trilingual edition.
+It defines a list of terms used in the preparation of other standards in the field of soil quality.
+The terms are classified under the following main headings: general terms, description of soil, sampling and assessment
+of soils, remediation, and soil ecotoxicology.
+
+
+
+### NAL ![](/static/img/one_star.png)
+#### National Agricultural Library
+The United States Department of Agriculture (USDA) produced this agricultural vocabulary. It contains more than 135,000
+terms, is updated annually, bilingual (English, Spanish), and available as Linked Open Data. Provided download formats are XML,
+RDF-[OLS](https://www.ebi.ac.uk/ols/index). It is mainly used for indexing and for improving retrieval of agricultural information.
+
+
+
+### NCBI Taxon ![](/static/img/one_star.png)
+The National Center for Biotechnology Information (NCBI) provides an extensive list of field crops including codes
+
+
+
+### Ontology of Units of Measure and Related Concepts (OM), Version 2.0 ![](/static/img/one_star.png)
+This ontology models concepts and relations for units, quantities, measurements and dimensions including conversion factors.
+It was developed by the Wageningen University and modelled in OWL 2.
+
+
+
+### [QUDT](https://www.qudt.org/2.1/catalog/qudt-catalog.html) ![](/static/img/one_star.png)
+#### Quantities, Units, Dimensions and Data Types Ontologies
+This ontology is under development by the NASA and provides first unified model of quantities, dimensions, units,
+and conversion factors. Each unit has its own URI and can thus be used as unique unit-identifier for data-sets.
+
+
+
+
+## Units Ontology (UO)
+
+
+
+### [AnaEE Thesaurus](https://vocabulaires-ouverts.inrae.fr/2017/03/13/thesaurus-anaee/)
+
+
+
+### [EngMath](http://www.ksl.stanford.edu/knowledge-sharing/papers/engmath.html)
+This ontology was developed for mathematical modeling and is mostly used by engineers.
+
+
+
+### EPPO Plant Protection Thesaurus
+This European thesaurus includes pest-specific information, names (multi-lingual) and codes for plants, animals and microorganisms.
+
+
+
+### GACS
+The GACS project developed this semantic concept scheme which integrates three important agricultural thesauri:
+AGROVOC, CAB and NAL thesauri. GACS was planned to be a hub for all concepts and shared value lists related to agriculture.
+In November 2019 the participants agreed that GACS URIs should not be promoted for use since GACS is not actively being maintained.
+Data is from 2016 and will not be actively maintained in the future.
+
+
+
+### LandVoc
+This vocabulary was created by Land Portal organization and includes a set of 270 concept about land governance.
+LandVoc is mainly derived from AGROVOC but links together other vocabularies.
+
+
+
+### PROV-O
+This [W3C](https://www.w3.org/TR/2014/NOTE-ld-bp-20140109/) ontology provides a set of classes, properties,
+and restrictions that can be used to represent and interchange provenance information generated in different systems
+and under different contexts. It can also be specialized to create new classes and properties to model provenance
+information for different applications and domains.
+
+
+
+### Semantic Sensor Network Ontology
+This ontology was developed by the W3C Semantic Sensor Networks Incubator Group and describes sensors, observations, and
+related concepts [[1]](https://www.w3.org/2005/Incubator/ssn/ssnx/ssn). It provides numerous suggestions on the management
+of sensor data including metadata of sensor description (e.g. accuracy, detection limit).
+
+
+
+
+## Overview of vocabulary portals, look-up services, registries, visualization, and gazetteers
+
+### AgroPortal ![](/static/img/two_star.png)
+The web portal provides access to agricultural ontologies and thesauri. Via a search field terms can be entered and concepts of more than 100 agricultural vocabularies. Registered user can provide new ontologies to this web service.
+
+
+
+### [GODAN](https://vest.agrisemantics.org/about/structure?qt-content_organization_tabs=3#qt-content_organization_tabs) ![](/static/img/two_star.png)
+#### Agrisemantics Map of Data Standards
+This portal provides a global overview of existing vocabularies for the exchange of agricultural data. It is grouped in 14 main categories, such as “Natural Resources, Earth and Environment”.
+
+
+
+### GeoNames
+This geographical database contains more than 11 million names of places.
+
+
+
+### [Ontobee](https://ontobee.org)
+This ontology register includes some 200 ontologies from natural science, including agriculture. It presents ontology term URIs to HTML web pages (user-friendly web browsing) and to RDF source codes for Semantic Web applications.
+
+
+
+### Ontology Lookup Service ([OLS](https://www.ebi.ac.uk/ols/index))
+OLS is a web service interface which allows queries from a register with more than 200 ontologies. The lookup service
+includes more than 5 million terms. Results link to single ontologies, concepts and output formats.
+
+
+
+### Open Tree of Life
+Was funded by the NSF, describes and visualizes the biological taxonomic classification system and can be used to allocate
+taxonomic species names and classes.
+
+
+
+### [Planteome](https://planteome.org)
+The project provides a platform to search and browse plant species, plant traits, phenotypes and gene expressions from different information systems.
+
+
+
+
+## Overview of tools, specifications, initiatives, data models and ontology languages
+
+### SKOS ![](/static/img/two_star.png)
+#### Simple Knowledge Organization System
+SKOS is a [W3C](https://www.w3.org/TR/2014/NOTE-ld-bp-20140109/) recommendation for the representation of thesauri,
+classification etc. or any other controlled vocabulary. It gives guidelines to facilitate publication and use of
+vocabularies as Linked Data. SKOS is part of the Semantic Web standards built upon RDF and RDFS. SKOS was formal
+released in 2009 by W3C as a new standard that connects different KOS and the linked data community.
+It defines classes and properties to present common features of a standard thesaurus.
+
+
+
+### RDF ![](/static/img/two_star.png)
+#### Resource Description Framework
+RDF is a family of W3C specifications that is applied as a general method for conceptual description or modeling of
+information that is implemented in web resources. Via an Application Programming Interface (e.g. RDF API)
+a standardized interface can be implemented e.g. in within web-based data portals.
+
+
+
+### ISO/IEC 13250-2:2006 ![](/static/img/two_star.png)
+#### Information technology – Topic Maps
+This standard regulates the representation and interchange of knowledge, especially for information retrieval.
+Topic Maps enable the linkage of multiple indexes from different sources. The standard defines the abstract structure and
+interpretation of Topic Maps, rules for merging them and a set of fundamental subject identifiers. The purpose of the data
+model is to define the interpretation of the Topic Maps interchange syntax, and to serve as a foundation for the definition
+of supporting standards for canonicalization, querying, constraints, etc.
+
+
+
+### OWL (Web Ontology Language) ![](/static/img/two_star.png)
+Ontology language developed (and updated to OWL 2) by the W3C. It meets the requirements of the Semantic Web.
+Ontologies which were written in OWL 2 (e.g. OM) can be used and exchanged as RDF documents. Relations between agricultural
+terms, a set of 179 custom relations is provided by e.g. **Agrontology** (as used in AGROVOC).
+
+
+
+### VocBench ![](/static/img/two_star.png)
+Is an open source, web-based multilingual vocabulary editing and workflow tool. It was originally developed and released by
+the FAO and the Artificial Intelligence Research Group of the University of Rome Tor Vergata to manage AGROVOC, but now hosts
+a still expanding set of vocabularies.
+
+
+
+### Data Catalog Vocabulary (DCAT) ![](/static/img/one_star.png)
+This RDF specification was designed by W3C to facilitate the interoperability between and search across different data catalogues.
+DCAT does not make any assumptions about the format of the datasets described in a catalogue. It incorporates terms from other
+vocabularies with stable term with appropriate meanings (e.g., foaf:homepage or dct:title).
+
+
+
+### RDFS ![](/static/img/one_star.png)
+#### Resource Description Framework Schema
+This RDF schema can be used for sematic data models and was published by the W3C (1998). It includes several classes with
+certain properties using the RDF extensible representation data model, providing basic elements for the description of ontologies.
+
+
+
+### schema.org
+Is a collaborative activity founded by technology companies (Google, Yahoo, Microsoft), to develop a standardized ontology
+to structure web data, based on existing markup languages. It provides a standardized schema for structured data on the
+internet and defines entities and relationships to be used to describe data sets or web pages. It is used to structure data
+in the research data search tool “Google Dataset Search”.
+
+
+
+## Use cases for applied thesauri in databases
+
+### [AGRIS](https://agris.fao.org/agris-search/index.do)
+#### (International System for Agricultural Science and Technology)
+Is a global public domain database published by the FAO with more than 8 million records on agricultural science and technology.
+The AGRIS Search system allows scientists, researchers and students to perform sophisticated searches using keywords from the
+AGROVOC thesaurus, specific journal titles or names of countries, institutions, and authors. The AGRIS is a RDF-aware system
+and AGRIS database is exposed as RDF.
+
+
+
+## Conflicts and solutions
+The AGROVOC thesaurus is widely accepted and appreciated within the agricultural science community. However, soil terms
+and concepts are often missing or inadequately described or assigned. Terms and concepts are permanently edited and improved by
+the experts (AGROVOC Editors) using the editing tool VocBench3.
+
+:::bonares_reference
+
+### References
+
+[1] Group, W3C Semantic Sensor Network Incubator (2009). Semantic Sensor Network Ontology (http://purl.oclc.org/NET/ssnx/ssn).
+
+:::
\ No newline at end of file
diff --git a/src/german_translation/index.md b/src/german_translation/index.md
new file mode 100644
index 0000000..c2e56f1
--- /dev/null
+++ b/src/german_translation/index.md
@@ -0,0 +1,43 @@
+---
+label: German Translation
+icon: "../static/img/translation_icon.svg"
+expanded: true
+order: 120
+---
+
+# Data management
+
+The topic data management includes methodical standards to structure and quality assure research data as recorded by
+standardized methods. Quality by supervised or unsupervised procedures e.g. data completeness, normal distribution,
+integrity, and removal of outliers, is prerequisite for wellmaintained data storage, -exchange, -processing and
+-evaluation. Descriptive data should be checked on misspellings, synonyms and inconsistencies to enable clear data
+allocation and combination of different data sets.
+
+When research data are collected, tested, described, and maybe pre-processed (e.g. pedotransferfunctions, biological
+models, upscaling) data must be technically prepared to be transferred into the database. At this point internal
+database management becomes relevant. Data (base) management includes e.g. rules on the data structure, languages and
+formats used. These need to meet the requirements on later data applications such as archiving, evaluation, reuse, and
+publishing. Research data management is widely implemented within research institutes in so-called Current Research
+Information Systems (CRIS) and in national or international (inter-)disciplinary data repositories. An example for
+national agricultural data management is the [PIAF](https://www.gil-net.de/Publikationen/131_26.pdf) system (**P**lanning,
+**I**nformation and **A**nalysis for **F**ield trials). An
+international and interdisciplinary open data repository for the wide field of environmental science is the [PANGAEA](https://pangaea.de/).
+
+Internationally accepted Data Management Plans (DMP) and open research data portals may help to plan, manage and publish
+research data. Tools and guidelines are provided by open access platforms and repositories such as [ReDBox](https://www.redboxresearchdata.com.au/) (Australia),
+[OpenAIRE](https://www.openaire.eu/), [CGIAR](https://www.cgiar.org/), [EUDAT](https://eudat.eu/), [EOSC](https://eosc-portal.eu/), and [INSPIRE](https://inspire.ec.europa.eu/).
+
+This chapter provides an overview of standards with general requirements on data quality, -structure -formats, and
+–types as well as geographic reference systems, units and dimensions.
+
+[!ref](/data_management/general_conventions.md)
+[!ref](/data_management/data_quality.md)
+[!ref](/data_management/data_transformation.md)
+[!ref](/data_management/data_exchange.md)
+[!ref](/data_management/data_archiving.md)
+
+:::bonares_reference
+
+## References
+
+:::
\ No newline at end of file
diff --git a/src/glossary/data_archiving.md b/src/glossary/data_archiving.md
new file mode 100644
index 0000000..54da6e7
--- /dev/null
+++ b/src/glossary/data_archiving.md
@@ -0,0 +1,41 @@
+---
+label: Data Archiving
+order: 10
+---
+
+# Data Archiving
+
+Research data which are replaced by new data and no longer actively used need to be stored permanently on separate storage devices with long durability. To enable long-term search and access to archived data standard digital archival systems should be used.
+
+
+
+_Overview of existing standards_
+
+### DIN 31644:2012-04 - Digital Archives ![](/static/img/two_star.png)
+
+This standard describes criteria for trustworthy digital archives in general and pre-conditions for the establishment and
+operation of digital archives. The German standard contains information on archival packages, data identification (e.g. DOI),
+and descriptive, technical and structural metadata. Users of this standard are encouraged to work through the task list
+within its takeover project. For practical assistance, a control list is annexed.
+
+The project [nestor](https://www.langzeitarchivierung.de/Webs/nestor/DE/Home/home_node.html) (=Network of Expertise in Long-Term Storage of Digital Resources) provides an archiving seal based on DIN 31644.
+
+
+
+### ISO 14721:2012 - Open archival information system, OAIS ![](/static/img/one_star.png)
+
+Originally developed by NASA and other space companies, OAIS provides frameworks for archival concepts, long-term digital
+information preservation, terminologies and concepts for describing and comparing archive architectures.
+
+
+
+### ISO 16363:2012 - Audit and certification of trustworthy digital repositories
+
+The ISO sets out comprehensive metrics for what an archive can be used based on OAIS.
+Primary Trustworthy Digital Repository Authorization Body (ISO-PTAB).
+
+
+
+### ISO 16919:2014 Space data and information transfer systems
+
+This standard specifies the requirements for bodies providing audit and certification of candidate trustworthy digital repositories.
diff --git a/src/glossary/index.md b/src/glossary/index.md
new file mode 100644
index 0000000..2ace03e
--- /dev/null
+++ b/src/glossary/index.md
@@ -0,0 +1,43 @@
+---
+label: Data Management
+icon: "../static/img/glossary.png"
+expanded: true
+order: 120
+---
+
+# Data management
+
+The topic data management includes methodical standards to structure and quality assure research data as recorded by
+standardized methods. Quality by supervised or unsupervised procedures e.g. data completeness, normal distribution,
+integrity, and removal of outliers, is prerequisite for wellmaintained data storage, -exchange, -processing and
+-evaluation. Descriptive data should be checked on misspellings, synonyms and inconsistencies to enable clear data
+allocation and combination of different data sets.
+
+When research data are collected, tested, described, and maybe pre-processed (e.g. pedotransferfunctions, biological
+models, upscaling) data must be technically prepared to be transferred into the database. At this point internal
+database management becomes relevant. Data (base) management includes e.g. rules on the data structure, languages and
+formats used. These need to meet the requirements on later data applications such as archiving, evaluation, reuse, and
+publishing. Research data management is widely implemented within research institutes in so-called Current Research
+Information Systems (CRIS) and in national or international (inter-)disciplinary data repositories. An example for
+national agricultural data management is the [PIAF](https://www.gil-net.de/Publikationen/131_26.pdf) system (**P**lanning,
+**I**nformation and **A**nalysis for **F**ield trials). An
+international and interdisciplinary open data repository for the wide field of environmental science is the [PANGAEA](https://pangaea.de/).
+
+Internationally accepted Data Management Plans (DMP) and open research data portals may help to plan, manage and publish
+research data. Tools and guidelines are provided by open access platforms and repositories such as [ReDBox](https://www.redboxresearchdata.com.au/) (Australia),
+[OpenAIRE](https://www.openaire.eu/), [CGIAR](https://www.cgiar.org/), [EUDAT](https://eudat.eu/), [EOSC](https://eosc-portal.eu/), and [INSPIRE](https://inspire.ec.europa.eu/).
+
+This chapter provides an overview of standards with general requirements on data quality, -structure -formats, and
+–types as well as geographic reference systems, units and dimensions.
+
+[!ref](/data_management/general_conventions.md)
+[!ref](/data_management/data_quality.md)
+[!ref](/data_management/data_transformation.md)
+[!ref](/data_management/data_exchange.md)
+[!ref](/data_management/data_archiving.md)
+
+:::bonares_reference
+
+## References
+
+:::
\ No newline at end of file
diff --git a/src/help/Mentioned_Standards.md b/src/help/Mentioned_Standards.md
new file mode 100644
index 0000000..955fec7
--- /dev/null
+++ b/src/help/Mentioned_Standards.md
@@ -0,0 +1,388 @@
+---
+label: Mentioned Standards
+order: 10
+---
+
+# Mentioned Standards
+
+**ANSI/NISO Z39.85-2012**: The Dublin Core Metadata Element Set
+
+**ANSI/NISO Z.39.84-2005**: Syntax for the Digital Object Identifier
+
+**ASTM E1910 / E 1910M - 15**: Standard Test Method for Agricultural pH Control Agents, Measurement of pH Change and Buffering Capacity
+
+**DIN 1301-1:2010** - Einheiten - Teil 1: Einheitennamen, Einheitenzeichen
+
+**DIN 1313:1998-12**: Quantities
+
+**DIN 1319-1:1995-01**: Fundamentals of Metrology. Part 1: Basic Terminology
+
+**DIN 1319 1ff** Fundamentals of Metrology (Parts 1-4)
+
+**DIN 4220:2008-11**: Bodenkundliche Standortbeurteilung - Kennzeichnung, Klassifizierung und Ableitung von Bodenkennwerten
+
+**DIN 7807:1995-02**: Agricultural drive wheel tractor tyres in radial construction - Service description (load index - speed symbol) marked tyres
+
+**DIN 8113:2009-02**: Weigh-in-Motion of Road Vehicles
+
+**DIN 11389:1988-04**: Tractors and agricultural machinery - Combines - Definitions, Characteristics, Performance
+
+**DIN 13303-1:1982-05**: Stochastics; probability theory, common fundamental concepts of mathematical and of descriptive statistics; concepts, signs and symbols
+
+**DIN 13303-2:1982-11**: Stochastics - mathematical statistics; concepts, signs and symbols.
+
+**DIN 18121-2:2012-02**: Soil, investigation and testing – Water content – Part 2: Determination by rapid methods
+
+**DIN 18123:2011-04**: Soil, investigation and testing – Determination of grain-size distribution
+
+**DIN 18128:2002-12**: Soil - Investigation and testing - Determination of ignition loss
+
+**DIN 18916:2002-08**: Vegetation technology in landscaping - Plants and plant care
+
+**DIN 18917:2002-08**: Vegetation technology in landscaping — Turf and seeding
+
+**DIN 19745:2006-10**: Soil quality – Principles of the determination of the water content by Time Domain Reflectometry (TDR) and Time Domain Transmissometry (TDT)
+
+**DIN 19746:2005-06**: Soil quality - Determination of mineral nitrogen (nitrat and ammonium) in soil profiles (Nmin laboratory method)
+
+**DIN 19747:2009-07**: Investigation of solids – Pre-treatment, preparation and processing of samples for chemical, biological and physical investigations
+
+**DIN 31644:2012-04**: Information and documentation – Criteria for trustworthy digital archives
+
+**DIN 32645:2008-11**: Chemical analysis – Decision limit, detection limit and determination limit under repeatability conditions – Terms, methods, evaluation
+
+**DIN 32646:2003-12**: Chemical analysis - Limit of detection and limit of determination (quantitation) as processing parameters - Estimation in an interlaboratory test under reproducibility conditions; Terms, meaning, proceeding
+
+**DIN 38402-1:2011-09**: German standard methods for the examination of water, waste water and sludge – General information
+
+**DIN 53804-1:2002-04**: Statistical evaluation - Part 1: Continuous characteristics
+
+**DIN 66115:1983-02**: Particle size analysis - Sedimentation analysis in the gravitational field - pipette method
+
+**DIN 66270:1998**: Information technology — Software document evaluation — Quality characteristics
+
+**DIN 70020-5:1986-12**: Automotive engineering - tyres and wheels - concepts and measuring conditions
+
+**DIN EN 25663:1993** Water quality - Determination of Kjeldahl nitrogen - Method after mineralization with selenium
+
+**DIN EN ISO 3166-1_2014-10**.pdf
+
+**DIN ISO 11843-1:2004** Capability of detection - Terms and definitions
+
+**DIN SPEC 35810:2014-11**: Stakeholder Engagement - Guidelines for decision making processes dealing with climate change
+
+**EN 709:1997**: Agricultural and forestry machinery – Pedestrian controlled tractors with mounted rotary cultivators, motor hoes, motor hoes with drive wheel(s) – Safety;
+
+**EN 12526:1998**: Castors and wheels – Vocabulary, recommended symbols and multilingual dictionary
+
+**EN 12527:1998**: Castors and wheels — Test methods and apparatus
+
+**EN 15934:2012**: Sludge, treated biowaste, soil and waste – Calculation of dry matter fraction after determination of dry residue or water content
+
+**EN 15936:2012**: Sludge, treated biowaste, soil and waste – Determination of total organic carbon (TOC) by dry combustion
+
+**EN 16760:2015**: Bio-based products – Life Cycle Assessment
+
+**EN ISO 520:2010**: Cereals and pulses – Determination of the mass of 1 000 grains
+
+**EN ISO 6709:2009**: Standard representation of geographic point location by coordinates
+
+**EN ISO 9000:2015**: Quality management systems – Fundamentals and vocabulary
+
+**EN ISO 9001:2015**: Quality management systems – Requirements
+
+**EN ISO 9004:2009**: Managing for the sustained success of an organization – A quality management approach
+
+**EN ISO 10012:2003**: Measurement management systems – Requirements for measurement processes and measuring equipment
+
+**EN ISO 14001:2015**: Environmental management systems – Requirements with guidance for use
+
+**EN ISO 14021:2016**: Environmental labels and declarations – Self-declared environmental claims (Type II environmental labelling)
+
+**EN ISO 14031:2013**: Environmental management - Environmental performance evaluation - Guidelines
+
+**EN ISO 14044:2006**: Environmental management – Life cycle assessment – Requirements and guidelines
+
+**EN ISO 14045:2012**: Environmental management – Eco-efficiency assessment of product systems – Principles, requirements and guidelines
+
+**EN ISO 19101-1:2014**: Geographic information – Reference model - Part 1: Fundamentals
+
+**EN ISO 19105:2005**: Geographic information – Conformance and testing
+
+**EN ISO 19106:2006**: Geographic information – Profiles
+
+**EN ISO 19107:2005**: Geographic information – Spatial schema
+
+**EN ISO 19108:2005**: Geographic information - Temporal schema
+
+**EN ISO 19111-2:2012**: Geographic information – Spatial referencing by coordinates – Part 2: Extension for parametric values
+
+**EN ISO 19111:2007**: Geographic information – Spatial referencing by coordinates
+
+**EN ISO 19112:2005**: Geographic information – Spatial referencing by geographic identifiers
+
+**EN ISO 19115-1:2014**: Geographic information - Metadata - Part 1: Fundamentals
+
+**EN ISO 19115-2:2010**: Geographic information – Metadata – Part 2: Extensions for imagery and gridded data
+
+**EN ISO 19116:2006**: Geographic information – Positioning services
+
+**EN ISO 19118:2011**: Geographic information – Encoding
+
+**EN ISO 19119:2016**: Geographic information – Services
+
+**EN ISO 19123:2007**: Geographic information – Schema for coverage geometry and functions
+
+**EN ISO 19125-2:2006**: Geographic information – Simple feature access – Part 2: SQL option.
+
+**EN ISO 19128:2008**: Geographic information – Web map server interface
+
+**EN ISO 19131:2008**: Geographic information – Data product specifications
+
+**EN ISO 19133:2007**: Geographic information – Location-based services – Tracking and navigation.
+
+**EN ISO 19135:2015**: Geographic information – Procedures for item registration
+
+**EN ISO 19136:2009**: Geographic information – Geography Markup Language (GML)
+
+**EN ISO 19142:2010**: Geographic information – Web Feature Service
+
+**EN ISO 19143:2012**: Geographic information – Filter encoding
+
+**EN ISO 19156:2013**: Geographic information – Observations and measurements
+
+**EN ISO 19157:2013**: Geographic information – Data quality
+
+**EN ISO 50001:2011**: Energy management systems - Requirements with guidance for use
+
+**EN ISO 80000-1:2013**: Quantities and units – Part 1: General
+
+**ISO 500-1:2014**: Agricultural tractors - Rear-mounted power take-off types 1, 2, 3 and 4 - Part 1: General specifications, safety requirements, dimensions for master shield and clearance zone
+
+**ISO 520:2010**: Cereals and pulses – Determination of the mass of 1 000 grains
+
+**ISO 2057:1981**: Agricultural tractors Remote control hydraulic cylinders for trailed implements
+
+**ISO 2332:2009**: Agricultural tractors and machinery - Connection of implements via three-point linkage - Clearance zone around implement
+
+**ISO 3534-1:2006**: Statistics – Vocabulary and symbols – Part 1: General statistical terms and terms used in probability
+
+**ISO 3534-2:2006**: Statistics – Vocabulary and symbols – Part 2: Applied statistics
+
+**ISO 3600:2015**: Tractors, machinery for agriculture and forestry, powered lawn and garden equipment - Operator’s manuals - Content and format.
+
+**ISO 4002**: Equipment for sowing and planting (Parts 1-2)
+
+**ISO 4004:1983**: Agricultural tractors and machinery - Track widths
+
+**ISO 4197:1989**: Equipment for working the soil - Hoe blades - Fixing dimensions
+
+**ISO 4226:2007**: Air quality – General aspects – Units of measurement
+
+**ISO 4254**: Agricultural machinery –Safety (Parts 1-12)
+
+**ISO 5527:2015**: Cereals – Vocabulary
+
+**ISO 5663:1984**: Water quality - Determination of Kjeldahl nitrogen - Method after mineralization with selenium
+
+**ISO 5678:1993**: Agricultural machinery; equipment for working the soil; S-tines: main dimensions and clearance zones
+
+**ISO 5679:1979**: Equipment for working soil - Disks -Classification - Main fixing dimensions and specifications
+
+**ISO 5680:1979**: Equipment for working soil - Tines and shovels for cultivators - Main fixing dimensions
+
+**ISO 6107-1:2004** - Water quality – Vocabulary
+
+**ISO 6689-1:1997**: Equipment for harvesting - Combines and functional components - Part 1: Vocabulary
+
+**ISO 6880:1983**: Machinery for agriculture; Trailed units of shallow tillage equipment; Main dimensions and attachment points
+
+**ISO 7168-1:1999**: Air quality – Exchange of data – Part 1: General data format
+
+**ISO 7256:1984**: Sowing equipment - Test methods (Part 1 - 2)
+
+**ISO 8524:1986**: Equipment for distributing granulated pesticides or herbicides -Test method
+
+**ISO 8601:2004**: Data elements and interchange formats – Information interchange – Representation of dates and times
+
+**ISO 8909-1:1994**: Forage harvesters - Part 1: Vocabulary
+
+**ISO 8910:1993**: Machinery and equipment for working the soil - Mouldboard plough working elements- Vocabulary
+
+**ISO 8945:1989**: Equipment for working the soil - Rotary cultivator blades - Fixing dimensions
+
+**ISO 8947:1993**: Agricultural machinery - equipment for working the soil - S-tines - test method
+
+**ISO 9000:2015**: Quality management systems – Fundamentals and vocabulary
+
+**ISO 9001:2015**: Quality management systems – Requirements
+
+**ISO 9004:2009**: Managing for the sustained success of an organization – A quality management approach
+
+**ISO 9169:2006**: Air quality –Definition and determination of performance characteristics of an automatic measuring system
+
+**ISO 10005:2005**: Quality management systems – Guidelines for quality plans
+
+**ISO 10006:2003**: Quality management systems - Guidelines for quality management in projects
+
+**ISO 10007:2003**: Quality management systems - Guidelines for configuration management (ISO 10007:2003)
+
+**ISO 10012:2003**: Measurement management systems – Requirements for measurement processes and measuring equipment
+
+**ISO 10381**: Soil quality - Sampling (Part 1-6)
+
+**ISO 10390:2005** - Soil quality - Determination of pH
+
+**ISO 10693:1995**: Soil quality – Determination of carbonate content – Volumetric method
+
+**ISO 11063:2012**: Soil quality – Method to directly extract DNA from soil samples
+
+**ISO 11074:2015**: Soil quality – Vocabulary
+
+**ISO 11260:1994**: Soil quality – Determination of effective cation exchange capacity and base saturation level using barium chloride solution.
+
+**ISO 11261:1995**: Soil quality - Determination of total nitrogen - Modified Kjeldahl method
+
+**ISO 11272:1998**: Soil quality – Determination of dry bulk density
+
+**ISO 11274:1998**: Soil quality – Determination of the water-retention characteristic – Laboratory methods
+
+**ISO 11276:1995**: Soil quality – Determination of pore water pressure –Tensiometer method
+
+**ISO 11277:1998**: Soil quality – Determination of particle size distribution in mineral soil material – Method by sieving and sedimentation
+
+**ISO 11461:2001**: Soil quality – Determination of soil water content as a volume fraction using coring sleeves – Gravimetric method
+
+**ISO 11466_1995**: Soil quality - Extraction of trace elements soluble in aqua regia
+
+**ISO 11783-1:2007**: Tractors and machinery for agriculture and forestry — Serial control and communications data network - Part 1: General standard for mobile data communication
+
+**ISO 11786:1995**: Agricultural tractors and machinery - Tractor-mounted sensor interface - Specifications
+
+**ISO 12782-1:2012**: Soil quality - Parameters for geochemical modelling of leaching and speciation of constituents in soils and materials – Part 1: Extraction of amorphous iron oxides and hydroxides with ascorbic acid
+
+**ISO 12782-2:2012**: Soil quality – Parameters for geochemical modelling of leaching and speciation of constituents in soils and materials – Part 2: Extraction of crystalline iron oxides and hydroxides with dithionite
+
+**ISO 12782-3:2012**: Soil quality – Parameters for geochemical modelling of leaching and speciation of constituents in soils and materials – Part 3: Extraction of aluminium oxides and hydroxides with ammonium oxalate/oxalic acid
+
+**ISO 12782-4:2012-09**: Soil quality – Parameters for geochemical modelling of leaching and speciation of constituents in soils and materials – Part 4: Extraction of humic substances from solid samples
+
+**ISO 12782-5:2012**: Soil quality – Parameters for geochemical modelling of leaching and speciation of constituents in soils and materials – Part 5: Extraction of humic substances from aqueous samples
+
+**ISO 13065:2015**: Sustainability criteria for bioenergy
+
+**ISO 13878:1998**: Soil quality -- Determination of total nitrogen content by dry combustion ("elemental analysis")
+
+**ISO 14001:2015**: Environmental management systems – Requirements with guidance for use
+
+**ISO 14021:2016**: Environmental labels and declarations – Self-declared environmental claims (Type II environmental labelling)
+
+**ISO 14031:2013**: Environmental management - Environmental performance evaluation - Guidelines
+
+**ISO 14040:2006**: Environmental management - Life cycle assessment - Principles and framework.
+
+**ISO 14044:2006**: Environmental management – Life cycle assessment – Requirements and guidelines
+
+**ISO 14045:2012**: Environmental management – Eco-efficiency assessment of product systems – Principles, requirements and guidelines
+
+**ISO 14063:2006**: Environmental management – Environmental communication – Guidelines and examples
+
+**ISO 14240-2_2011**: Soil quality – Determination of soil microbial biomass – Part 2: Fumigation-extraction method.
+
+**ISO 14269-1:1997**: Tractors and self-propelled machines for agriculture and forestry - Operator enclosure environment - Part 1: Vocabulary
+
+**ISO 14688**: Geotechnical investigation and testing – Identification and classification of soil (1-3)
+
+**ISO 14721:2012**: Space data and information transfer systems - Open archival information system (OAIS) - Reference model
+
+**ISO 15178:2000**: Soil quality—Determination of total sulfur by dry combustion
+
+**ISO 15685:2012**: Soil quality – Determination of potential nitrification and inhibition of nitrification – Rapid test by ammonium oxidation
+
+**ISO 15709:2002**: Soil quality – Soil water and the unsaturated zone – Definitions, symbols and theory
+
+**ISO 15903:2002 (E)**: Soil quality— Format for recording soil and site information
+
+**ISO 16231:2013**: Self-propelled agricultural machinery – Assessment of stability (Part 1-2)
+
+**ISO 16269series**: Statistical interpretation of data
+
+**ISO 17628:2015**: Geotechnical investigation and testing – Geothermal testing – Determination of thermal conductivity of soil and rock using a borehole heat exchanger
+
+**ISO 17892-2:2014**: Geotechnical investigation and testing – Laboratory testing of soil – Part 2: Determination of bulk density.
+
+**ISO 17892-3:2015**: Geotechnical investigation and testing – Laboratory testing of soil – Part 3: Determination of particle density
+
+**ISO 17892-4:2014**: Geotechnical investigation and testing – Laboratory testing of soil – Part 4: Determination of particle size distribution
+
+**ISO 17892-5:2014**: Geotechnical investigation and testing – Laboratory testing of soil – Part 5: Incremental loading oedometer test
+
+**ISO 17892-6:2014**: Geotechnical investigation and testing – Laboratory testing of soil – Part 6: Fall cone test
+
+**ISO 17962:2015**: Agricultural machinery – Equipment for sowing – Minimization of the environmental effects of fan exhaust from pneumatic systems
+
+**ISO 19103:2015(E)**: Geographic information — Conceptual schema language
+
+**ISO 19115-2:2009**: Geographic information – Metadata – Part 2: Extensions for imagery and gridded data
+
+**ISO 19157:2013**: Geographic information – Data quality
+
+**ISO 20988_2007**: Air quality – Guidelines for estimating measurement uncertainty
+
+**ISO 22475-1:2006**: Geotechnical investigation and testing – Sampling methods and groundwater measurements – Part 1: Technical principles for execution
+
+**ISO 22476-2:2005**: Geotechnical investigation and testing – Field testing – Part 2: Dynamic probing
+
+**ISO 23611**: Soil quality — Sampling of soil invertebrates (Parts 1-6)
+
+**ISO 25177:2008**: Soil quality – Field soil description
+
+**ISO 26000:2010**: Guidance on social responsibility
+
+**ISO 26322-1:2008**: Tractors for agriculture and forestry - Safety - Part 1: Standard tractors
+
+**ISO 28258:2013**: Soil quality – Digital exchange of soil-related data
+
+**ISO/DIS 5681:2014**: Equipment for crop protection - Vocabulary
+
+**ISO/DIS 18400:2015** Soil quaility - Sampling
+
+**ISO/DIS 19109:2013**: Geographic information – Rules for application schema
+
+**ISO/DIS 19110:2013**: Geographic information – Methodology for feature cataloguing
+
+**ISO/DIS 19119:2015**: Geographic information – Services
+
+**ISO/IEC 8859-1:1998**: Information technology - 8-bit single-byte coded graphic character sets - Part 1: Latin alphabet No. 1
+
+**ISO/IEC 10646:2014**: Information technology - Universal Coded Character Set (UCS)
+
+**ISO/IEC 11404:2007**: Information technology — GeneralPurpose Datatypes (GPD)
+
+**ISO/IEC 13250-2:2006**: Information technology - Topic Maps - Part 2: Data model
+
+**ISO/IEC 17025:2005**: General requirements for the competence of testing and calibration laboratories
+
+**ISO/IEC 19501:2005**: Information technology - Open Distributed Processing - Unified Modeling Language (UML) Version 1.4.2
+
+**ISO/TR 14047:2012**: Environmental management - Life cycle assessment - Illustrative examples on how to apply ISO 14044 to impact assessment situations
+
+**ISO/TR 19120:2001**: Geographic information - Functional standards
+
+**ISO/TR 19121:2000**: Geographic information - Imagery and gridded data
+
+**ISO/TS 19139:2007**: Geographic information - Metadata -XML schema implementation
+
+**VDI 3786**: Environmental meteorology - Meteorological measurements (Parts 1-4)
+
+**VDI 3957:2014**: Biological measuring techniques for the determination and evaluation of effects of air pollutants on plants (biomonitoring) - Fundamentals and aims
+
+**VDI 4070-1:2016-02**: Sustainable management in small and medium-sized enterprises - Guidance notes for sustainable management
+
+**VDI 4605:2016-02** - Evaluation of sustainability
+
+**VDI 4800-1:2016-01**: Resource efficiency - Methodological principles and strategies
+
+**VDI 4800-2:2016-03**: Resource efficiency -Evaluation of the use of raw materials.
+
+**VDI 6101:2014-07**: Machine operation with regard to the trafficability of soils used for agriculture
diff --git a/src/help/code_lists.md b/src/help/code_lists.md
new file mode 100644
index 0000000..83d163d
--- /dev/null
+++ b/src/help/code_lists.md
@@ -0,0 +1,1887 @@
+---
+label: Code Lists
+order: 20
+---
+
+# Code Lists
+
+Code lists are useful tools for expressing longer lists of potential values and help to organize and harmonize databases.
+Whenever a universal accepted code exists for a certain parameter, it is recommended extend the database with a code column.
+
+
+
+## Soil survey
+
+In the Tables 11-16 the most important code lists for field soil survey, description and classification, as parts of
+national and international standards, are listed:
+
+### Table 10
+_Overview of code lists on soil data survey_
+
+
+