diff --git a/.github/workflows/doc-deploy.yml b/.github/workflows/doc-deploy.yml
new file mode 100644
index 00000000..3be8a595
--- /dev/null
+++ b/.github/workflows/doc-deploy.yml
@@ -0,0 +1,57 @@
+# HMS Networks Solution Center
+# Docusaurus Deploy Action for Maven-based Ewon ETK Projects,
+# Adapted for the Ignition Ewon Connector Project
+#
+# Version: 1.1
+#
+# This action is configured to automatically run when a push
+# is made to either the `main` or `gh-pages-staging` branch,
+# or when a run is manually triggered.
+name: Docusaurus Deploy to GitHub Pages
+
+on:
+ push:
+ branches:
+ - main
+ - gh-pages-staging
+ workflow_dispatch:
+
+jobs:
+ deploy:
+ name: Docusaurus Deploy to GitHub Pages
+ runs-on: ubuntu-latest
+ defaults:
+ run:
+ shell: bash
+ working-directory: web-docs
+ steps:
+ - uses: actions/checkout@v3
+
+ - name: Setup Node.js
+ uses: actions/setup-node@v3
+ with:
+ node-version: 18
+ cache: yarn
+ cache-dependency-path: web-docs/yarn.lock
+
+ - name: Install Dependencies
+ run: yarn install --frozen-lockfile
+
+ - name: Build Website
+ run: yarn build
+
+ # Popular action to deploy to GitHub Pages:
+ # Docs: https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-docusaurus
+ - name: Deploy to GitHub Pages
+ uses: peaceiris/actions-gh-pages@v3
+ with:
+ github_token: ${{ secrets.GITHUB_TOKEN }}
+ # Build output to publish to the `gh-pages` branch:
+ publish_dir: web-docs/build
+ # The following lines assign commit authorship to the official
+ # GH-Actions bot for deploys to `gh-pages` branch:
+ # https://github.com/actions/checkout/issues/13#issuecomment-724415212
+ # The GH actions bot is used by default if you didn't specify the two fields.
+ # You can swap them out with your own user credentials.
+ user_name: github-actions[bot]
+ user_email: 41898282+github-actions[bot]@users.noreply.github.com
\ No newline at end of file
diff --git a/.github/workflows/doc-test-deploy.yml b/.github/workflows/doc-test-deploy.yml
new file mode 100644
index 00000000..3540912c
--- /dev/null
+++ b/.github/workflows/doc-test-deploy.yml
@@ -0,0 +1,40 @@
+# HMS Networks Solution Center
+# Test Docusaurus Deploy Action for Maven-based Ewon ETK Projects,
+# Adapted for the Ignition Ewon Connector Project
+#
+# Version: 1.0
+#
+# This action is configured to automatically run when a pull request
+# is opened for the `main` branch.
+name: Test Docusaurus Build
+
+on:
+ pull_request:
+ branches:
+ - main
+
+jobs:
+ test-deploy:
+ name: Test Docusaurus Build
+ runs-on: ubuntu-latest
+ defaults:
+ run:
+ shell: bash
+ working-directory: web-docs
+ steps:
+ - uses: actions/checkout@v3
+
+ - name: Setup Node.js
+ uses: actions/setup-node@v3
+ with:
+ node-version: 18
+ cache: yarn
+ cache-dependency-path: web-docs/yarn.lock
+
+ - name: Install Dependencies
+ working-directory: ./web-docs
+ run: yarn install --frozen-lockfile
+
+ - name: Test Build Website
+ working-directory: ./web-docs
+ run: yarn build
\ No newline at end of file
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 00000000..9943967a
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,132 @@
+# Ignition Ewon® Connector Project Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+ and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+ overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+ advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+ address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement using the GitHub
+report feature and selecting "Report to repository admins."
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
+at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 00000000..8b858203
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,140 @@
+# Ignition Ewon® Connector Contribution Guidelines
+
+Thank you for your interest in contributing to the project.
+
+All types of contributions are valued and encouraged, though there are a few guidelines which must be followed to make the contribution process easy and consistent. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them.
+
+If you like the project, but don't have time to contribute, there are other easy ways to show your support and appreciation, such as:
+- Star the project
+ - Refer to this project in another project
+ - Mention or share the project at local meetups and tell your colleagues
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Asking Questions](#asking-questions)
+- [How to Contribute](#how-to-contribute)
+ - [Reporting Bugs and Errors](#reporting-bugs-and-errors)
+ - [Suggesting Features or Enhancements](#suggesting-features-or-enhancements)
+ - [Making Modifications or Updates](#making-modifications-or-updates)
+ - [Documentation](#documentation)
+ - [Source Code](#source-code)
+ - [Committing and Merging Modifications and Updates](#committing-and-merging-modifications-and-updates)
+ - [Commit Scope](#commit-scope)
+ - [Commit Messages](#commit-messages)
+ - [Pull Requests](#pull-requests)
+
+## Code of Conduct
+
+This project and everyone who participates in it is governed by the project's [Code of Conduct](https://github.com/hms-networks/IgnitionEwonConnector/blob/main/CODE_OF_CONDUCT.md).
+
+By participating, you are expected to uphold this code. Please report unacceptable behavior to the project maintainer(s).
+
+## Asking Questions
+
+Before asking a question, it is best to search for existing [Issues](https://github.com/hms-networks/IgnitionEwonConnector/issues) or [Discussions](https://github.com/hms-networks/IgnitionEwonConnector/discussions) that may help. In case you've found a suitable issue or discussion and still need clarification, you may comment directly on the issue or discussion. It is also advisable to search the internet for answers.
+
+If you then still have a question or need clarification, you may create a [new discussion](https://github.com/hms-networks/IgnitionEwonConnector/discussions/new) or [new issue](https://github.com/hms-networks/IgnitionEwonConnector/issues/new) and provide as much context and detail as possible.
+
+## How To Contribute
+
+> ### Legal Notice
+> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content, and that the content you contribute may be provided under the project license.
+
+### Reporting Bugs and Errors
+
+We use GitHub issues to track bugs and errors. If you run into an issue with the project, please create a [new issue](https://github.com/hms-networks/IgnitionEwonConnector/issues/new) with the following in consideration:
+
+- Explain the behavior you would expect and the actual behavior.
+- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. If possible, please isolate the problem and create a test case.
+
+Once you have submitted an issue on GitHub, we will label it and follow-up accordingly.
+
+### Suggesting Features or Enhancements
+
+We use GitHub issues to track feature and enhancement requests. If you'd like to suggest a feature or enhancement, please create a [new issue](https://github.com/hms-networks/IgnitionEwonConnector/issues/new) with the following in consideration:
+
+- Make sure that you are using the latest version.
+- Make sure that you are using the latest Ewon firmware.
+ - Check for updates at [https://www.ewon.biz/technical-support/pages/firmware](https://www.ewon.biz/technical-support/pages/firmware).
+- Read the [Documentation](https://hms-networks.github.io/sc-java-maven-starter-project/docs) carefully to find out if the functionality is already covered.
+- Perform a search for existing [Issues](https://github.com/hms-networks/IgnitionEwonConnector/issues) or [Discussions](https://github.com/hms-networks/IgnitionEwonConnector/discussions) to see if the feature or enhancement has already been suggested.
+ - If the feature or enhancement has already been suggested, add a comment to the existing issue or discussion instead of opening a new one.
+- Make sure the feature or enhancement is with the scope and aims of the project. New features shall be useful to the majority of users, not a small subset.
+ - If a feature or enhancement targets a minority of users, it is advised to consider writing an add-on or library.
+
+### Making Modifications or Updates
+
+The development environment for this project uses the standard Ewon Java development environment, which is [Eclipse](https://www.eclipse.org/). Alternative IDEs can be used but may not be fully compatible with the Ewon Java Toolkit and thus are not guaranteed nor officially supported by HMS.
+
+Documentation and additional information about the Ewon Java development environment is available in the Ewon Java Toolkit User Guide \(J2SE\) at [https://developer.ewon.biz/content/java-0#dev-documents](https://developer.ewon.biz/content/java-0#dev-documents).
+
+#### Documentation
+
+Changes made to the documentation in this project must be made in an individual commit, or accompany the commit with the relevant source code changes.
+
+Documentation for this project shall be written in present passive voice and is governed by the project's [Code of Conduct](https://github.com/hms-networks/IgnitionEwonConnector/blob/main/CODE_OF_CONDUCT.md).
+
+#### Source Code
+
+Changes made to the source code in this project must be organized into individual commits, each with an individual objective.
+
+Source code in this project adheres to the [Google Java Style Guide](https://google.github.io/styleguide/javaguide.html), and any changes must follow the same format. Detailed information about the Google Java Style Guide can be found at [https://google.github.io/styleguide/javaguide.html](https://google.github.io/styleguide/javaguide.html).
+
+Source code changes which do not adhere to the [Google Java Style Guide](https://google.github.io/styleguide/javaguide.html) will be rejected automatically during the pull request phase.
+
+### Committing and Merging Modifications and Updates
+
+#### Commit Scope
+
+Each commit to this project should have very limited scope. All changes in each commit should have a common theme, and you should be able to describe the scope of the change as a single statement. _Hint: If you can not describe the commit without using the word "and" or creating a list, the commit should be broken up._
+
+To ensure a clean and productive Git history, commits which do not follow those guidelines should be reorganized, otherwise they may be rejected during the pull request phase.
+
+#### Commit Messages
+
+Each commit must contain a message describing the change(s) made. The commit message must meet the following guidelines:
+
+1. Subject (First Line)
+ 1. Must not be more than 50 characters in length
+ 2. Must describe commit change-set concisely
+ 3. Must capitalize first character
+ 4. Must not end with a period
+ 5. Must be followed by a blank line (unless body omitted)
+2. Body
+ 1. Must not be more than 72 characters in length, per line
+ 2. Must describe commit change-set thoroughly
+ 3. Must use proper capitalization, grammar, and punctuation
+ 4. Must use blank lines to separate paragraphs
+
+```
+Subject line
+
+More detailed explanatory text, if necessary. Wrap to 72 characters
+or less. The blank line between the subject line and commit body is
+critical (unless commit body is omitted).
+
+Additional paragraphs can be added after another blank line. Bullet
+points and other rich text can be included as well.
+
+1. Example Change
+2. Example Addition
+3. Example Bug Fix
+```
+
+#### Pull Requests
+
+All code committed to this project must follow the pull request procedure before it can be merged to the main or master branch. The pull request procedure ensures that all changes have been reviewed by a project maintainer, and tested to function properly.
+
+In addition to any automated testing which may be performed for pull requests, all modified or newly-introduced code must be thoroughly tested prior to creating a pull request.
+
+Once a pull request has been created, the following must be performed:
+
+1. Designate pull request assignee
+ - Under most circumstances, the person creating the pull request shall be designated as the assignee. Should another person become responsible for the pull request, that person shall be designated as the assignee.
+2. Add content labels
+ - Pull requests and other GitHub content can be labeled to document the type of content addressed. These labels can be found and assigned in the pull request sidebar.
+3. Add linked issues
+ - If the pull request resolves or otherwise addresses an issue documented using GitHub Issues, the issue should be linked to the pull request. Linked issues can be found and assigned in the pull request sidebar.
+4. Add pull request reviewers
+ - Pull requests must be reviewed by at least one, but preferably two, reviewers or code-owners. These reviewers should be chosen based on project familiarity, code language, and dependencies. In some scenarios, a code-owner may automatically be assigned to a pull request.
\ No newline at end of file
diff --git a/README.md b/README.md
new file mode 100644
index 00000000..66ff45e9
--- /dev/null
+++ b/README.md
@@ -0,0 +1,10 @@
+# Ignition Ewon® Connector Module
+
+## [Description](#table-of-contents)
+
+Synchronize Ewon Flexy data to Ignition's Tag Historian using the Ignition Ewon® Connector Module.
+
+## [Documentation](#table-of-contents)
+
+Documentation for the Ignition Ewon Connector is available in a user-friendly format (via GitHub Pages) on the
+[Ignition Ewon Connector Homepage](https://hms-networks.github.io/IgnitionEwonConnector/).
diff --git a/readme.md b/readme.md
deleted file mode 100644
index a9afc401..00000000
--- a/readme.md
+++ /dev/null
@@ -1,281 +0,0 @@
-
-# Ignition Ewon® Connector
-
-## [NOTICE]
-
-The Ignition Ewon Connector is currently undergoing development for Version 2.0.0.
-During this time, documentation and source code may be relocated, unavailable, or incomplete.
-
-## [Table of Contents](#table-of-contents)
-
-1. [Description](#description)
-2. [Version](#version)
-3. [Support](#support)
-4. [Features](#features)
-5. [Download](#download)
-6. [Installation](#installation)
-7. [Ewon Setup](#ewon-setup)
-8. [Connector Setup](#connector-setup)
-9. [Connector Usage](#connector-usage)
-10. [Troubleshooting](#troubleshooting)
-11. [FAQs](#faqs)
-
-
-## [Description](#table-of-contents)
-
-Synchronize Ewon Flexy data to Ignition's Tag Historian.
-
-[Back to top](#table-of-contents)
-
-## [Version](#table-of-contents)
-
-This module version is compatible with Ignition 8. For an Ignition 7.9 compatible module go to [Ignition-7.9-main](https://github.com/hms-networks/IgnitionEwonConnector/tree/Ignition-7.9-main) branch. The Ignition 7.9 module is no longer supported and does not receive updates.
-
-[Back to top](#table-of-contents)
-
-## [Support](#table-of-contents)
-
-This application is supported by HMS Networks' North American offices.
-
-For support please visit our [Support Portal](https://support.hms-networks.com/hc/en-us).
-
-[Back to top](#table-of-contents)
-
-## [Features](#table-of-contents)
-
-* Read Functionality
- * Historical (via DataMailbox) (default option)
- * Updated up to once per minute
- * Realtime (via M2Web)
- * Updated up to once per second
- * Can be enabled per-tag, per-Ewon or system-wide
-* Write Functionality (via M2Web)
- * Modify Ewon tag values from Ignition
-
-[Back to top](#table-of-contents)
-
-## [Download](#table-of-contents)
-
-The module can be downloaded from the [releases page](https://github.com/hms-networks/IgnitionEwonConnector/releases).
-
-To run and install the connector, you need to download the latest asset named `EwonConnector-X_Y-A.B.C.zip` where X_Y and A.B.C are the Ignition and module version numbers.
-
-
-
-## [Installation](#table-of-contents)
-
-1. On the Gateway Webpage, select `Config` > `SYSTEM` > `Modules` to open the Module Configuration page.
-
-
-
-2. Scroll to the bottom on the list, find the blue arrow, and click the `Install or Upgrade a Module` link.
-
-
-
-3. Click `Choose File`, select a .modl file that you have previously downloaded.
-
-
-
-4. Click Install.
-
- * When the page reloads you can now see the module you installed in the list of modules.
-
-### Upgrading
-
-Upgrading the module to a newer version can be done by following the [Installation](#installation) steps above. Once installed, restart Ignition for the changes to fully take effect.
-
-[Back to top](#table-of-contents)
-
-## [Ewon Setup](#table-of-contents)
-
-When setting up an Ewon, follow all standard Ewon Flexy documentation and Install guides. [https://websupport.ewon.biz/support](https://websupport.ewon.biz/support "https://websupport.ewon.biz/support")
-
-In addition to the standard documentation, follow these additional steps.
-
-### Link Ewon to Talk2M
-Open the Ewon webserver and navigate to the VPN Wizard page (At the top right of the page click `Wizards`, then on the right hand menu bar select `VPN`). Select `Configure Talk2M connectivity` and follow the prompts to connect the Ewon to Talk2M.
-
-
-
-### Setup Historical Logging for Tags
-
-Open the Ewon webserver and navigate to the `Values` page (On the left hand menu click `Tags` > `Values`). Change the `MODE` to `SETUP`. For each tag that requires logged data, double click the tag to open the `Tag configuration` menu. Scroll down to the `Historical Logging` section and check the `Historical Logging Enabled` checkbox. Enable either deadband or interval logging.
-
->**Deadband Logging**
->
->The Logging Deadband field triggers logging when the tags value changes by a particular amount. For example, a logging deadband of 2 means that a tag will be logged when the value changes by 2 or more. A negative value in the logging deadband field disables logging on value change.
->
->**Interval Logging**
->
->The Logging Interval field triggers time based logging. For example, a logging interval of 60 means that the tag will be logged every 60 seconds. A logging interval of 0 disables time based logging.
-
-Once configured, click `Update Tag` on the bottom right of the page.
-
-
-
-### Enable Historical Data In DataMailbox
-
-Open the Ewon webserver and navigate to the `Data Management` page ( On the left hand menu click `Setup` > `System` > `Main` > `Data Management`). Check the `Historical Data` checkbox and set the `DataMailbox upload interval` to a reasonable number for your application. The `DataMailbox upload interval` sets how often the Flexy will send batches of historical data to DataMailbox and does not affect the frequency at which tag values are logged. When done, click `Update` at the bottom of the page.
-
-
-
-[Back to top](#table-of-contents)
-
-## [Connector Setup](#table-of-contents)
-
-With the module successfully installed, a new `Ewon Connector` page will be added to your Ignition Gateway webpages. Navigate to this page by selecting `Config` > `TAGS` > `Ewon Connector`.
-
-
-
-
-* **Main**
- * **Name** - Unique name of the tag provider created in Ignition.
- * **Enabled** - Option to turn on/off the Ewon Connector functionality.
- * **Tag Names Contain Periods** - Check this if any Ewon tag names contain periods. If any tag names of the connected Ewons contain periods ".", tag names on the connected Ewons may not contain the underscore "_" character. HMS suggests not using periods in tag names when using Ignition.
- * **Poll Rate in Minutes** - Interval for how often data will be pulled from DataMailbox.
- * **Realtime Poll Rate in Seconds** - Interval for how often data will be pulled from an Ewon when realtime reads are activated.
-
-* **Talk2M Account Information**
- * **Account** - Your Talk2M account name.
- * **Username** - Your Talk2M user name.
- * **Password** - Your Talk2M password.
- * **Change Password?** - Check this box to change the password stored in Ignition.
- * **Talk2M Token** - Your Talk2M token generated using eCatcher.
- * **Talk2M Developer ID** - Your Talk2M Developer ID. Include all dashes.
- * If you do not have a Talk2M Developer ID, you may request one here: [https://developer.ewon.biz/registration](https://developer.ewon.biz/registration "https://developer.ewon.biz/registration").
-
-* **Ewon Device Information** - All Ewons must have at least once common user account to enable realtime and write functionality. The username and password for this account must be identical for all linked Ewons.
- * **Ewon Username** - Common Ewon username.
- * **Ewon Password** - Common Ewon password.
- * **Change Password?** - Check this box to change the password stored in Ignition.
-
-* **History**
- * **History Enabled** - Option to turn off historical logging.
- * **Target History Provider** - Ignition History Provider used to log Ewon data.
-
-* **Advanced**
- * **Read all values in realtime** - Option to always read values in realtime.
- * **Note:** This disables DataMailbox reads. Values logged on the Ewon are not logged in Ignition when this option is enabled.
-
-### Saving Changes
-
-Once all the configuration information has been entered, click `Save Changes`, then restart Ignition.
-
-### Generating a Talk2M Token
-
-To learn more about Talk2M tokens and how to generate them, please refer to Section 4.6 of the DMWeb API reference guide found at: [DMWeb API Reference Guide](https://developer.ewon.biz/system/files_force/rg-0005-00-en-reference-guide-for-dmweb-api.pdf).
-
-[Back to top](#table-of-contents)
-
-## [Connector Usage](#table-of-contents)
-
-Tags will be created automatically in Ignition on startup. Tags will be visible under the provider name assigned during the configuration process. Each Ewon tied to the Talk2M account will be a unique tag directory.
-
-
-
-### **Allowed Tag Names**
-
-The tags synchronized by the connector must adhere to the following rules.
-
-By default, and with the `Tag Names Contain Periods` option disabled, tags must begin with an alphanumeric or underscore. Additional characters in tag names must be an alphanumeric, underscore, space, or any of the following: `' - : ( )`.
-
-With the `Tag Names Contain Periods` option enabled, tags must begin with an alphanumeric or period. Additional characters in tag names must be an alphanumeric, period, space, or any of the following: `' - : ( )`. Note that this option does not support tag names that contain underscores.
-
-### **Reading Values**
-
-The tags created by the connector are native Ignition tags and are updated cyclically by the connector based on the polling rates set during the [Setup](#setup) step.
-
-The `Tag Browser` tool in Ignition Designer can be used to read tag values.
-
-### **Writing Values**
-
-Ewon tag values can be written from Ignition. When attempting to write a tag value, be sure that the the communication mode is set to `Comm Read/Write` in the Ignition Designer `Project` menu.
-
-The `Tag Browser` tool in Ignition Designer can be used to write tag values.
-
-After a tag value is written in Ignition, the displayed value my revert back to its previous state. This is because new DataMailbox values were received. DataMailbox values will always lag the live tag value. This behavior can be avoided by temporarily enabling realtime mode for the tag/Ewon being written to.
-
-### **Realtime Values**
-
-The realtime value functionality allows Ignition to read live tag values from an Ewon up to once per second.
-
-This functionality can be enabled in three ways.
-
-**1. Individual Tag**
-
- * Open Designer and navigate to the `Tag Browser`
- * Expand the `All Providers` directory.
- * Expand the directory associated with your Ewon Connector Tag Provider.
- * Expand the directory associated with the Ewon you want to read a live tag value from.
- * Expand the tag name to show the tag's properties.
- * Find the `Realtime` property and enable it.
-
-**2. Individual Ewon**
-
- * Open Designer and navigate to the `Tag Browser`
- * Expand the `All Providers` directory.
- * Expand the directory associated with your Ewon Connector Tag Provider.
- * Expand the directory associated with the Ewon you want to read live tag values from.
- * Expand the `_config` directory.
- * Find the `AllRealtime` tag and enable it.
-
-**3. All Ewons**
-
- * Navigate to the Ewon Connector Configuration webpage discussed in the [Setup](#setup) section.
- * Enable the `Read all values in realtime` option.
- * Click `Save Changes`, then restart Ignition.
-
-_Note: The realtime functionality counts against your Talk2M account's monthly bandwidth._
-
-### **Deleting Tags**
-
-Tags can be deleted by right clicking the tag in the `Tag Browser` then selecting `Delete`. If the tag still exists on the Ewon or in DataMailbox the tag will be recreated in Ignition on the next DataMailbox update.
-
-[Back to top](#table-of-contents)
-
-## [Troubleshooting](#table-of-contents)
-
-### Troubleshooting Topics
-
-* [Tags do not appear in Ignition](#Tags-do-not-appear-in-Ignition)
-* [Changes on the Ewon Connector page do not take effect](#Changes-on-the-Ewon-Connector-page-do-not-take-effect)
-
-### Tags do not appear in Ignition
-
-There are several reasons tags may not be populated into Ignition. Please follow the following steps in order.
-
-1. Verify that all steps in the [Ewon Setup](#ewon-setup) section were followed.
-2. If the system has just been configured, wait one hour for data to be registered in DataMailbox.
-3. Verify your Talk2M credentials are correctly entered into the Ewon Connector settings in Ignition.
- * If your credentials were incorrectly entered, the Ignition logs will indicate a Authentication Error. Check the logs on the Ignition webserver by clicking `Status` > `Logs`. If your credentials are incorrect, you will see log entries in this format.
-
-
-
- * If you see this log error, check your Talk2M Account information entered on the `Ewon Connector` configuration page. _Note: Any changes done on this page require a restart of the connector module or Ignition. You can restart the module by navigating to `Config` > `Modules` and clicking `restart` next to the module._
-4. If tag values are still not populated in Ignition, please contact [support](#support).
-
-### Changes on the Ewon Connector page do not take effect
-
-Any changes done on this page require a restart of the connector module or Ignition. You can restart the module by navigating to `Config` > `Modules` and clicking `restart` next to the module.
-
-[Back to top](#table-of-contents)
-
-## [FAQs](#table-of-contents)
-
-* [How do I check my Talk2M data usage?](#How-do-I-check-my-Talk2M-data-usage?)
-* [If Ignition is not running will my data still be logged?](#If-Ignition-is-not-running-will-my-data-still-be-logged?)
-
-### How do I check my Talk2M data usage?
-
-Your Talk2M data usage can be accessed through [eCatcher](https://ewon.biz/cloud-services/talk2m/ecatcher "https://ewon.biz/cloud-services/talk2m/ecatcher").
-
-1. Open eCatcher and login.
-2. On the left hand menu bar click `Account`.
-3. Once in the account properties click `Reports` near the top of the page.
-4. From here you will be able to download the current or past monthly connection log reports.
-
-### If Ignition is not running will my data still be logged?
-
-If Ignition is offline, data will still be logged by the Flexy and stored in DataMailbox. The amount of data points stored in DataMailbox depends on your [account type](https://ewon.biz/cloud-services/talk2m/plan-pricing "https://ewon.biz/cloud-services/talk2m/plan-pricing"). Once Ignition is online again, all logged points will be fetched from DataMailbox by Ignition.
-
-[Back to top](#table-of-contents)
diff --git a/web-docs/.gitignore b/web-docs/.gitignore
new file mode 100644
index 00000000..50b2292e
--- /dev/null
+++ b/web-docs/.gitignore
@@ -0,0 +1,20 @@
+# Dependencies
+node_modules
+
+# Production
+build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
diff --git a/web-docs/README.md b/web-docs/README.md
new file mode 100644
index 00000000..670e618d
--- /dev/null
+++ b/web-docs/README.md
@@ -0,0 +1,48 @@
+# Documentation Website
+
+This documentation website is built using [Docusaurus 2](https://docusaurus.io/), a modern static
+website generator.
+
+### Installation
+
+Before you can develop, build, or deploy the documentation website, you must install the
+dependencies:
+
+```shell
+$ yarn
+```
+
+### Local Development
+
+```shell
+$ yarn start
+```
+
+This command starts a local development server and opens up a browser window. Most changes are
+reflected live without having to restart the server.
+
+### Build
+
+```shell
+$ yarn build
+```
+
+This command generates static content into the `build` directory and can be served using any static
+contents hosting service.
+
+### Deployment
+
+Using SSH:
+
+```shell
+$ USE_SSH=true yarn deploy
+```
+
+Not using SSH:
+
+```shell
+$ GIT_USER= yarn deploy
+```
+
+If you are using GitHub pages for hosting, this command is a convenient way to build the website and
+push to the `gh-pages` branch.
\ No newline at end of file
diff --git a/web-docs/ScDocusaurusConfig.js b/web-docs/ScDocusaurusConfig.js
new file mode 100644
index 00000000..ccefea8a
--- /dev/null
+++ b/web-docs/ScDocusaurusConfig.js
@@ -0,0 +1,27 @@
+// CONFIGURATION ZONE - YOU CAN EDIT THESE LINES
+const ScDocusaurusConfig = {
+ repoOwnerName: 'hms-networks',
+ repoName: 'IgnitionEwonConnector',
+ title: 'Ignition Ewon® Connector',
+ description: 'Synchronize Ewon Flexy data to Ignition\'s Tag Historian using the Ignition Ewon® Connector Module.',
+ meta: 'Homepage for the HMS Networks Ignition Ewon® Connector Module.',
+ minIgnitionVersion: '8.1.1',
+ minIgnitionVersionShort: '8.1',
+};
+
+// EXPORT ZONE - DON'T TOUCH BELOW THIS LINE
+module.exports = {
+ ...ScDocusaurusConfig,
+ repoUrl: 'https://github.com/' + ScDocusaurusConfig.repoOwnerName + '/' + ScDocusaurusConfig.repoName,
+ repoArchiveUrl: 'https://github.com/' + ScDocusaurusConfig.repoOwnerName + '/' + ScDocusaurusConfig.repoName + '/archive/refs/heads/main.zip',
+ repoLatestReleaseUrl: 'https://github.com/' + ScDocusaurusConfig.repoOwnerName + '/' + ScDocusaurusConfig.repoName + '/releases/latest',
+ repoNewIssueUrl: 'https://github.com/' + ScDocusaurusConfig.repoOwnerName + '/' + ScDocusaurusConfig.repoName + '/issues/new',
+};
+
+
+
+
+
+
+
+
diff --git a/web-docs/babel.config.js b/web-docs/babel.config.js
new file mode 100644
index 00000000..e00595da
--- /dev/null
+++ b/web-docs/babel.config.js
@@ -0,0 +1,3 @@
+module.exports = {
+ presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
+};
diff --git a/web-docs/docs/01-INTRODUCTION.mdx b/web-docs/docs/01-INTRODUCTION.mdx
new file mode 100644
index 00000000..21343811
--- /dev/null
+++ b/web-docs/docs/01-INTRODUCTION.mdx
@@ -0,0 +1,42 @@
+---
+id: introduction
+title: Introduction
+sidebar_label: Introduction
+slug: /
+---
+
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+import FeaturesPartial from '@site/docs/_partial/_features.mdx';
+
+## Description
+
+<>The {ScDocusaurusConfig.title} is an Ignition 8.1 Module for synchronizing data from Ewon Flexy devices to
+Ignition's Tag Historian using the Ewon Talk2M APIs (DataMailbox and M2Web).>
+
+:::note
+
+For an Ignition 7.9 compatible version of this module, please see
+the [Ignition 7.9 Branch (Ignition-7.9-main)](https://github.com/hms-networks/IgnitionEwonConnector/tree/Ignition-7.9-main).
+
+The Ignition 7.9 version of this module is no longer being actively developed, maintained, or supported.
+
+:::
+
+## Getting Started
+
+To get started, please refer to the [Quick Start Guide](03-QUICK_START_GUIDE.mdx). This guide
+provides instructions for installing and configuring the Module, as well as, a brief overview of
+the features and functionality provided by the Module.
+
+<>Additional information about the {ScDocusaurusConfig.title} can be found on the various pages available in the menu to
+your left (above on mobile/small devices).>
+
+## Features
+
+
+
+## License
+
+This project is licensed under the terms of the Apache 2.0 license. More information about the
+license and the full text of the license, can be found on the [LICENSE](07-legal/03-LICENSE.mdx)
+page.
diff --git a/CHANGELOG.md b/web-docs/docs/02-CHANGELOG.mdx
similarity index 92%
rename from CHANGELOG.md
rename to web-docs/docs/02-CHANGELOG.mdx
index ef2f2ace..cb2a6e55 100644
--- a/CHANGELOG.md
+++ b/web-docs/docs/02-CHANGELOG.mdx
@@ -1,132 +1,102 @@
-# Ewon Ignition 8 Connector Changelog
-
-## v1.2.1
-
-### Major Changes
-
-* Tag provider name customization was removed to ensure consistent and stable connector functionality
- * Fixed an issue that caused the per-tag realtime override option to be missing
-
-### Minor Changes
-
-* Updated GSON dependency version
-
-## v1.2.0
-
-### Major Changes
-
-* Updated to Ignition 8.1.1 SDK
-* Fixed an issue that caused the AllRealtime tag value to be lost
-* Fixed an issue that caused tag deletion to become disabled
-* Update to HTTP POST requests for DataMailbox and M2Web APIs
-* Update to new Talk2M token authentication for DataMailbox API
-
-### Minor Changes
-
-* Clarify files to download for releases
-* Updated the settings page to automatically restart the connector when applying changes
-
-## v1.1.12
-
-### Major Changes
-
-* Ewon tag descriptions are now synced to Ignition tag documentation and tooltip
-
-## v1.1.11
-
-### Major Changes
-
-* Fixed an issue that caused realtime update errors on tags with underscores
-
-## v.1.1.10
-
-### Major Changes
-
-* Tags are now highlighted and returned to original value if a write fails
-* Applicable tags are now marked as stale when realtime updating fails
-
-### Minor Changes
-
-* Added option to disable strict checking for allowed tag name characters
-* Updated user-friendly logging output
-* Fixed an issue with realtime tag provider shutdown
-* Fixed an issue with realtime poll rate value validation
-
-## v1.1.9
-
-### Major Changes
-
-* Module now listed in the Ignition Showcase
-
-### Minor Changes
-
-* Ewon tag names are verified for compatibility with Ignition
-* Module ID has changed
-* Bugfix: The connector no longer faults when initially installed and no credentials are entered
-
-## v1.1.8
-
-### Major Changes
-
-* Realtime values are now available on a per Ewon basis
-
-### Minor Changes
-
-* Created new readme
-* Updated Configuration Webpage
-* SecurityFix: Removed user credentials from Ignition log files
-
-## v1.1.7
-
-### Major Changes
-
-### Minor Changes
-
-* Bugfix: Enabled writing to boolean tags on the eWON
-* Bugfix: Fixed precision loss when reading large number via realtime
-* Bugfix: Correctly handle reading an empty string via realtime
-
-## v1.1.6
-
-### Major Changes
-
-* Module is now signed
-
-### Minor Changes
-
-* Realtime string tags can handle " character
-* Module gracefully handles tags that dont exist on the ewon but exist in datamailbox
-
-## v1.1.5
-
-### Major Changes
-
-* None
-
-### Minor Changes
-
-* Included CHANGELOG.md in release
-* Removed logging of "Updating Live Values"
-* Updated license for module
-
-## v1.1.4
-
-### Major Changes
-
-* None
-
-### Minor Changes
-
-* Tags can now be removed and created again without restarting the module
-* Logging of "Updating Live Values" level changed to "Trace"
-
-## v1.1.3
-### Major Changes
-* Realtime reads from the Flexy
-* Ignition to Flexy writes
-* Support for tag deletion
-* Configuration parameters are now URL friendly
-* Support for String tag values
-
-### Minor Changes
-* Support for periods in tag names
+---
+id: change-log
+title: Change Log
+sidebar_label: Change Log
+toc_max_heading_level: 2
+---
+
+## v1.2.1
+### Major Changes
+* Tag provider name customization was removed to ensure consistent and stable connector functionality
+ * Fixed an issue that caused the per-tag realtime override option to be missing
+### Minor Changes
+* Updated GSON dependency version
+
+## v1.2.0
+### Major Changes
+* Updated to Ignition 8.1.1 SDK
+* Fixed an issue that caused the AllRealtime tag value to be lost
+* Fixed an issue that caused tag deletion to become disabled
+* Update to HTTP POST requests for DataMailbox and M2Web APIs
+* Update to new Talk2M token authentication for DataMailbox API
+### Minor Changes
+* Clarify files to download for releases
+* Updated the settings page to automatically restart the connector when applying changes
+
+## v1.1.12
+### Major Changes
+* Ewon tag descriptions are now synced to Ignition tag documentation and tooltip
+### Minor Changes
+* None
+
+## v1.1.11
+### Major Changes
+* Fixed an issue that caused realtime update errors on tags with underscores
+### Minor Changes
+* None
+
+## v.1.1.10
+### Major Changes
+* Tags are now highlighted and returned to original value if a write fails
+* Applicable tags are now marked as stale when realtime updating fails
+### Minor Changes
+* Added option to disable strict checking for allowed tag name characters
+* Updated user-friendly logging output
+* Fixed an issue with realtime tag provider shutdown
+* Fixed an issue with realtime poll rate value validation
+
+## v1.1.9
+### Major Changes
+* Module now listed in the Ignition Showcase
+### Minor Changes
+* Ewon tag names are verified for compatibility with Ignition
+* Module ID has changed
+* Bugfix: The connector no longer faults when initially installed and no credentials are entered
+
+## v1.1.8
+### Major Changes
+* Realtime values are now available on a per Ewon basis
+### Minor Changes
+* Created new readme
+* Updated Configuration Webpage
+* SecurityFix: Removed user credentials from Ignition log files
+
+## v1.1.7
+### Major Changes
+* None
+### Minor Changes
+* Bugfix: Enabled writing to boolean tags on the eWON
+* Bugfix: Fixed precision loss when reading large number via realtime
+* Bugfix: Correctly handle reading an empty string via realtime
+
+## v1.1.6
+### Major Changes
+* Module is now signed
+### Minor Changes
+* Realtime string tags can handle " character
+* Module gracefully handles tags that dont exist on the ewon but exist in datamailbox
+
+## v1.1.5
+### Major Changes
+* None
+### Minor Changes
+* Included CHANGELOG.md in release
+* Removed logging of "Updating Live Values"
+* Updated license for module
+
+## v1.1.4
+### Major Changes
+* None
+### Minor Changes
+* Tags can now be removed and created again without restarting the module
+* Logging of "Updating Live Values" level changed to "Trace"
+
+## v1.1.3
+### Major Changes
+* Realtime reads from the Flexy
+* Ignition to Flexy writes
+* Support for tag deletion
+* Configuration parameters are now URL friendly
+* Support for String tag values
+### Minor Changes
+* Support for periods in tag names
\ No newline at end of file
diff --git a/web-docs/docs/03-QUICK_START_GUIDE.mdx b/web-docs/docs/03-QUICK_START_GUIDE.mdx
new file mode 100644
index 00000000..cbcb27e5
--- /dev/null
+++ b/web-docs/docs/03-QUICK_START_GUIDE.mdx
@@ -0,0 +1,39 @@
+---
+id: quick-start-guide
+title: Quick Start Guide
+sidebar_label: Quick Start Guide
+toc_max_heading_level: 2
+---
+
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+import DownloadPartial from './_partial/_download.mdx';
+import InstallationOrUpgradePartial from './_partial/_installation_or_upgrade.mdx';
+import ConfigurationPartial from './_partial/_configuration.mdx';
+
+## Overview
+
+<>This document (quick start guide) will walk you through the steps to install and configure the
+{ScDocusaurusConfig.title} Module.>
+
+## Download
+
+
+
+## Installation
+
+### a. First Time Installation or Upgrade
+
+The following steps are required for a new installation of the module or an upgrade to a newer version.
+
+
+
+### b. First Time Installation Only
+
+The following steps are only required for a new installation of the module.
+
+If you have not already done so, follow the steps [above](#a-first-time-installation-or-upgrade) to install the module.
+
+
+
+
+
diff --git a/web-docs/docs/04-setup/01-DOWNLOAD.mdx b/web-docs/docs/04-setup/01-DOWNLOAD.mdx
new file mode 100644
index 00000000..a6248132
--- /dev/null
+++ b/web-docs/docs/04-setup/01-DOWNLOAD.mdx
@@ -0,0 +1,9 @@
+---
+id: download
+title: Download
+sidebar_label: Download
+---
+
+import DownloadPartial from '../_partial/_download.mdx';
+
+
diff --git a/web-docs/docs/04-setup/02-INSTALLATION_UPGRADE.mdx b/web-docs/docs/04-setup/02-INSTALLATION_UPGRADE.mdx
new file mode 100644
index 00000000..30e46c6a
--- /dev/null
+++ b/web-docs/docs/04-setup/02-INSTALLATION_UPGRADE.mdx
@@ -0,0 +1,32 @@
+---
+id: installation-and-upgrade
+title: Installation and Upgrade
+sidebar_label: Installation and Upgrade
+toc_max_heading_level: 2
+---
+
+import InstallationOrUpgradePartial from '../_partial/_installation_or_upgrade.mdx';
+import ConfigurationPartial from '../_partial/_configuration.mdx';
+
+### a. First Time Installation or Upgrade
+
+The following steps are required for a new installation of the module or an upgrade to a newer version.
+
+
+
+### b. First Time Installation Only
+
+The following steps are only required for a new installation of the module.
+If you have not already done so, follow the steps [above](#a-first-time-installation-or-upgrade) to install the module.
+
+:::note
+
+These first time installation only steps are the same as the configuration steps found on
+the [configuration](./03-CONFIGURATION.mdx) page.
+
+:::
+
+
+
+
+
diff --git a/web-docs/docs/04-setup/03-CONFIGURATION.mdx b/web-docs/docs/04-setup/03-CONFIGURATION.mdx
new file mode 100644
index 00000000..ec12dc09
--- /dev/null
+++ b/web-docs/docs/04-setup/03-CONFIGURATION.mdx
@@ -0,0 +1,16 @@
+---
+id: configuration
+title: Configuration
+sidebar_label: Configuration
+---
+
+import ConfigurationPartial from '../_partial/_configuration.mdx';
+
+
+
+
+
+
+
+
+
diff --git a/web-docs/docs/04-setup/_category_.json b/web-docs/docs/04-setup/_category_.json
new file mode 100644
index 00000000..b155ebfb
--- /dev/null
+++ b/web-docs/docs/04-setup/_category_.json
@@ -0,0 +1,6 @@
+{
+ "label": "Setup",
+ "className": "Setup",
+ "collapsed": false,
+ "collapsible": true
+}
\ No newline at end of file
diff --git a/web-docs/docs/05-usage/01-FEATURES.mdx b/web-docs/docs/05-usage/01-FEATURES.mdx
new file mode 100644
index 00000000..1241ded5
--- /dev/null
+++ b/web-docs/docs/05-usage/01-FEATURES.mdx
@@ -0,0 +1,9 @@
+---
+id: features
+title: Features
+sidebar_label: Features
+---
+
+import FeaturesPartial from '@site/docs/_partial/_features.mdx';
+
+
\ No newline at end of file
diff --git a/web-docs/docs/05-usage/02-SYSTEM_REQUIREMENTS.mdx b/web-docs/docs/05-usage/02-SYSTEM_REQUIREMENTS.mdx
new file mode 100644
index 00000000..367ca46c
--- /dev/null
+++ b/web-docs/docs/05-usage/02-SYSTEM_REQUIREMENTS.mdx
@@ -0,0 +1,21 @@
+---
+id: system-requirements
+title: System Requirements
+sidebar_label: System Requirements
+---
+
+import SysReqIgnitionPartial from '@site/docs/_partial/_sys_req_ignition.mdx';
+import SysReqHardwarePartial from '@site/docs/_partial/_sys_req_hardware.mdx';
+
+## Required Ignition Version
+
+
+
+## Required Hardware
+
+
+
+
+
+
+
diff --git a/web-docs/docs/05-usage/03-ALLOWED_TAG_NAMES.mdx b/web-docs/docs/05-usage/03-ALLOWED_TAG_NAMES.mdx
new file mode 100644
index 00000000..b4049a60
--- /dev/null
+++ b/web-docs/docs/05-usage/03-ALLOWED_TAG_NAMES.mdx
@@ -0,0 +1,18 @@
+---
+id: allowed-tag-names
+title: Allowed Tag Names
+sidebar_label: Allowed Tag Names
+---
+
+The tags synchronized by the connector must adhere to the following rules.
+
+By default, and with the `Disable Tag Name Checking` option unselected, tags must begin with an alphanumeric or
+underscore. Additional characters must be an alphanumeric, underscore, space, or any of the following: `' - : ( )`.
+
+If the `Disable Tag Name Checking` option is unselected, the connector will attempt to convert any illegal characters
+in tag names to underscores.
+
+
+
+
+
diff --git a/web-docs/docs/05-usage/04-READING_TAGS.mdx b/web-docs/docs/05-usage/04-READING_TAGS.mdx
new file mode 100644
index 00000000..093539f3
--- /dev/null
+++ b/web-docs/docs/05-usage/04-READING_TAGS.mdx
@@ -0,0 +1,63 @@
+---
+id: reading-tags
+title: Reading Tags
+sidebar_label: Reading Tags
+---
+
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+import AccessingTagsPartial from '@site/docs/_partial/_accessing_tags.mdx';
+
+### Realtime (Live) Values
+
+Realtime (live) tag data functionality is supported by the connector, allowing for the reading of tag values in
+realtime. This functionality may be enabled connector-wide, per Ewon Flexy, or per tag.
+
+#### Connector-Wide
+
+To enable realtime (live) tag data functionality connector-wide, set the `Read all values in realtime` field to `true`
+in the connector configuration.
+
+1. From the Ignition Gateway webpage, navigate to the `Config` section.
+2. Select the `Ewon Connector` option from the left-hand menu.
+3. Enable the `Read all values in realtime` option.
+4. Click the `Save Changes` button, then restart Ignition.
+
+#### Per Ewon Flexy
+
+To enable realtime (live) tag data functionality per Ewon Flexy, set the `_STATUS/ForceRealtimeData` tag to `true` in
+each Ewon Flexy's tag folder.
+
+1. From the Ignition Designer, navigate to the `Tag Browser` tool.
+2. Expand the `All Providers` directory.
+3. Expand the `Ewon` directory (associated with the Ewon Connector).
+4. Expand the Ewon Flexy's directory.
+5. Expand the `_STATUS` tag folder.
+6. Set the `_STATUS/ForceRealtimeData` tag to `true`.
+
+:::note
+
+If you are not in read/write mode, you will need to switch to read/write mode to set the tag value.
+
+:::
+
+#### Per Tag
+
+To enable realtime (live) tag data functionality per tag, set the `ForceRealtimeData` property to `true` in the tag's
+properties.
+
+1. From the Ignition Designer, navigate to the `Tag Browser` tool.
+2. Expand the `All Providers` directory.
+3. Expand the `Ewon` directory (associated with the Ewon Connector).
+4. Expand the Ewon Flexy's directory.
+5. Select the tag and expand it to view its properties.
+6. Set the `ForceRealtimeData` property to `true`.
+
+:::note
+
+If you are not in read/write mode, you will need to switch to read/write mode to set the tag value.
+
+:::
+
+### Where to Access Tags
+
+
\ No newline at end of file
diff --git a/web-docs/docs/05-usage/05-WRITING_TAGS.mdx b/web-docs/docs/05-usage/05-WRITING_TAGS.mdx
new file mode 100644
index 00000000..3dbabc25
--- /dev/null
+++ b/web-docs/docs/05-usage/05-WRITING_TAGS.mdx
@@ -0,0 +1,26 @@
+---
+id: writing-tags
+title: Writing Tags
+sidebar_label: Writing Tags
+---
+
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+import AccessingTagsPartial from '@site/docs/_partial/_accessing_tags.mdx';
+
+Writing tag values is supported by the connector, allowing for the modification of tag values on the Ewon Flexy. This
+functionality is automatically enabled for all tags.
+
+:::info
+
+After writing a tag value, the displayed value may revert to the previous value. This is due to new historical (
+DataMailbox) tag data being received, which will always lag behind the realtime (live) value. To avoid this behavior,
+you may enable realtime (live) tag data functionality for the tag (or Ewon Flexy, if desired).
+
+For more information, see the [Realtime (Live) Values](04-READING_TAGS.mdx#realtime-live-values) section of the
+[Reading Tags](04-READING_TAGS.mdx) page.
+
+:::
+
+### Where to Access Tags
+
+
\ No newline at end of file
diff --git a/web-docs/docs/05-usage/06-DELETING_TAGS.mdx b/web-docs/docs/05-usage/06-DELETING_TAGS.mdx
new file mode 100644
index 00000000..b5059b37
--- /dev/null
+++ b/web-docs/docs/05-usage/06-DELETING_TAGS.mdx
@@ -0,0 +1,15 @@
+---
+id: deleting-tags
+title: Deleting Tags
+sidebar_label: Deleting Tags
+---
+
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+import AccessingTagsPartial from '@site/docs/_partial/_accessing_tags.mdx';
+
+Tags can be deleted by right-clicking the tag in the `Tag Browser` then selecting `Delete`. If the tag still exists on
+the Ewon or in DataMailbox the tag will be recreated in Ignition on the next DataMailbox update.
+
+### Where to Access Tags
+
+
\ No newline at end of file
diff --git a/web-docs/docs/05-usage/_category_.json b/web-docs/docs/05-usage/_category_.json
new file mode 100644
index 00000000..56107946
--- /dev/null
+++ b/web-docs/docs/05-usage/_category_.json
@@ -0,0 +1,6 @@
+{
+ "label": "Usage",
+ "className": "usage",
+ "collapsed": false,
+ "collapsible": true
+}
\ No newline at end of file
diff --git a/web-docs/docs/06-help/01-FAQ.mdx b/web-docs/docs/06-help/01-FAQ.mdx
new file mode 100644
index 00000000..2b17aae1
--- /dev/null
+++ b/web-docs/docs/06-help/01-FAQ.mdx
@@ -0,0 +1,58 @@
+---
+id: faq
+title: Frequently Asked Questions
+sidebar_label: Frequently Asked Questions
+---
+
+import AccessingTagsPartial from '@site/docs/_partial/_accessing_tags.mdx';
+
+## 1. How can I check my Talk2M data usage?
+
+Your Talk2M data usage can be checked through the [eCatcher](https://ewon.biz/cloud-services/talk2m/ecatcher) software.
+
+1. Open eCatcher and log in to your Talk2M account.
+2. Click the **Account** option in the left-hand menu.
+3. In the **Account Properties** menu, click **Reports** near the top of the page.
+4. In the **Reports** menu, you may download current or past monthly reports for your Talk2M account.
+
+## 2. If Ignition is not running, will my data still be logged?
+
+If Ignition is not running, or is offline, data will still be logged by the Flexy and stored in DataMailbox. Once
+Ignition is running again, all logged historical data points will be fetched from DataMailbox by Ignition, unless the
+device or tag is configured for realtime (live) data only.
+
+:::note
+
+The number of data points stored in DataMailbox is limited, and depends on the Talk2M account type. For information
+about Talk2M account types, please refer to the [Talk2M Pricing](https://ewon.biz/cloud-services/talk2m/plan-pricing)
+page.
+
+:::
+
+## 3. Where can I find my tags in Ignition?
+
+
+
+:::tip
+
+If the module has just started up or loaded recently, it may take a few minutes for initial metadata to be cached before
+tags will be available in Ignition.
+
+:::
+
+## 4. What happened to the Ignition 7.9 version of this module?
+
+The Ignition 7.9 version of this module is no longer being actively developed, maintained, or supported.
+To access and learn more about the previous, Ignition 7.9 compatible version of this module, please see the
+[Ignition 7.9 Branch (Ignition-7.9-main)](https://github.com/hms-networks/IgnitionEwonConnector/tree/Ignition-7.9-main).
+
+## 5. Where did the 'Tag Names Contain Periods' setting go?
+
+The 'Tag Names Contain Periods' setting has been removed from the module as of version 2.0.0.
+Previously, this setting was used to determine whether the module should attempt to convert periods in tag names, which
+are not valid in Ignition, to underscore(s) instead.
+
+As of version 2.0.0, this functionality has been merged with the 'Disable Tag Name Checking' setting.
+By default, the 'Disable Tag Name Checking' setting is disabled, which means that the module will attempt to convert
+any illegal tag names to valid tag names by replacing illegal characters with underscores.
+If you wish to disable this functionality, you may enable the 'Disable Tag Name Checking' setting.
diff --git a/web-docs/docs/06-help/02-TROUBLESHOOTING.mdx b/web-docs/docs/06-help/02-TROUBLESHOOTING.mdx
new file mode 100644
index 00000000..0536e713
--- /dev/null
+++ b/web-docs/docs/06-help/02-TROUBLESHOOTING.mdx
@@ -0,0 +1,80 @@
+---
+id: troubleshooting
+title: Troubleshooting
+sidebar_label: Troubleshooting
+---
+
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+import RestartingModulePartial from '../_partial/_restarting_module.mdx';
+
+## Disclaimer
+
+<>The information provided in this section is intended to assist with troubleshooting common issues
+that may be encountered when using the {ScDocusaurusConfig.title}. This information is provided
+as-is, and is not intended to be a comprehensive troubleshooting guide.>
+
+If you are unable to resolve an issue using the information provided in this section, please
+visit the [Support](03-SUPPORT.mdx) page for additional support options.
+
+## 1. Tags do not appear in Ignition
+
+### Symptom
+
+All, or some, of the expected tags do not appear in Ignition.
+
+### Cause
+
+There are several reasons tags may not be populated into Ignition. The most common reasons are:
+
+- The system has just been configured, and data has not yet been registered in DataMailbox.
+- The Talk2M credentials are incorrectly entered into the Ewon Connector settings in Ignition.
+- The Ewon Connector module is not running.
+
+### Solution
+
+To resolve this issue, try the following:
+
+1. Ensure that the module has been installed and configured correctly.
+ * For more information, please refer to the
+ [Installation](../04-setup/02-INSTALLATION_UPGRADE.mdx) and [Configuration](../04-setup/03-CONFIGURATION.mdx)
+ pages.
+2. If the system has just been configured, wait for an upload interval (usually 1 hour) for data to be registered in
+ DataMailbox.
+3. Verify that the [configured credentials](../04-setup/03-CONFIGURATION.mdx) are correct.
+ * The Ignition logs will indicate an Authentication Error if the credentials are incorrect.
+ Check the logs on the Ignition webserver by clicking `Status` > `Logs`. If your credentials are incorrect, you
+ will see log entries in this format.
+
+
+
+ * If you see this log error, check your configured Talk2M Account information. For more information, please refer to
+ the [Configuration](../04-setup/03-CONFIGURATION.mdx) page.
+
+ :::note
+
+ <>Any changes made to the configuration of the {ScDocusaurusConfig.title} require a restart of the module or
+ Ignition.
+ >
+
+
+ :::
+
+### 2. Changes on the Ewon Connector page do not take effect
+
+### Symptom
+
+Configuration changes made on the Ewon Connector page do not take effect or result in an error.
+
+### Cause
+
+<>The {ScDocusaurusConfig.title} may have not been restarted after configuration changes were made, which is preventing
+the changes from taking effect, or in some cases, causing an error.
+>
+
+If the configuration is changed, the module must be restarted for the changes to take effect.
+If the module is not restarted, the changes will not take effect, or may partially take effect, which can result in an
+error.
+
+### Solution
+
+
\ No newline at end of file
diff --git a/web-docs/docs/06-help/03-SUPPORT.mdx b/web-docs/docs/06-help/03-SUPPORT.mdx
new file mode 100644
index 00000000..65c11fb8
--- /dev/null
+++ b/web-docs/docs/06-help/03-SUPPORT.mdx
@@ -0,0 +1,21 @@
+---
+id: support
+title: Support
+sidebar_label: Support
+---
+
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+
+<>The {ScDocusaurusConfig.title} is supported by the HMS Networks North American
+Offices.>
+
+## GitHub Issues
+
+<>For concerns regarding the functionality and features of the {ScDocusaurusConfig.title},
+please create an issue using the "Issues" tab on
+the GitHub repository page>.
+
+## HMS Networks Support Portal
+
+For all other inquiries, please use the
+[HMS Networks Support Portal](https://support.hms-networks.com/hc/en-us).
\ No newline at end of file
diff --git a/web-docs/docs/06-help/_category_.json b/web-docs/docs/06-help/_category_.json
new file mode 100644
index 00000000..0fe51308
--- /dev/null
+++ b/web-docs/docs/06-help/_category_.json
@@ -0,0 +1,6 @@
+{
+ "label": "Help",
+ "className": "Help",
+ "collapsed": false,
+ "collapsible": true
+}
\ No newline at end of file
diff --git a/web-docs/docs/07-legal/01-TERMS_OF_USE.mdx b/web-docs/docs/07-legal/01-TERMS_OF_USE.mdx
new file mode 100644
index 00000000..bd53381d
--- /dev/null
+++ b/web-docs/docs/07-legal/01-TERMS_OF_USE.mdx
@@ -0,0 +1,83 @@
+---
+id: terms-of-use
+title: Terms of Use
+sidebar_label: Terms of Use
+---
+
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+
+<>By using the {ScDocusaurusConfig.title}, you are agreeing to the following terms of
+use.>
+
+## 1. Conduct and Behavior
+
+We expect all users of our products and services to conduct themselves in a professional and
+respectful manner.
+
+You agree to follow the [Code of Conduct](02-CODE_OF_CONDUCT.mdx) for this project.
+
+You agree not to use the project for any purpose that is unlawful or prohibited by these Terms of
+Use, or any other purpose not reasonably intended by HMS, including, but not limited to, the
+following:
+
+1. _In any way that breaches any applicable local, national, or international law or regulation._
+2. _In any way that is unlawful or fraudulent, or has any unlawful or fraudulent purpose or effect._
+3. _To transmit, or procure the sending of, any unsolicited or unauthorized advertising or
+ promotional material or any
+ other form of similar solicitation (spam)._
+4. _To knowingly transmit any data, send or upload any material that contains viruses, Trojan
+ horses, worms, time-bombs,
+ keystroke loggers, spyware, adware, or any other harmful programs or similar computer code
+ designed to adversely
+ affect the operation of any computer software or hardware._
+5. _To transmit, or procure the sending of, any data, send or upload any material that is
+ defamatory, obscene, indecent,
+ hateful, discriminatory, or inflammatory._
+6. _To transmit, or procure the sending of, any data, send or upload any material that is
+ threatening, abusive, or
+ invades another's privacy, or causes annoyance, inconvenience, or needless anxiety._
+7. _To transmit, or procure the sending of, any data, send or upload any material that is likely to
+ deceive any person._
+8. _To transmit, or procure the sending of, any data, send or upload any material that infringes any
+ patent, trademark,
+ trade secret, copyright, or other intellectual property rights of any other person._
+
+## 2. Warranty Disclaimer
+
+We strive to provide the best products and services we can, and to provide clear, concise
+documentation for our users. However, we cannot guarantee that our products, services, or
+documentation are free from defects.
+
+THE PROJECT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.
+HMS DOES NOT REPRESENT OR WARRANT THAT:
+(A) THE FUNCTIONS OF THE PROJECT WILL MEET YOUR REQUIREMENTS OR EXPECTATIONS,
+(B) THE OPERATION OF THE PROJECT WILL BE UNINTERRUPTED OR ERROR-FREE, OR
+(C) DEFECTS IN THE PROJECT CAN OR WILL BE CORRECTED.
+
+## 3. Third-Party Content
+
+This project may contain links to third-party websites, applications, or other content.
+
+The content of any linked third-party content is not controlled by HMS, and HMS is not responsible
+for the content of any linked third-party content. HMS does not endorse, approve, or sponsor any
+linked third-party content, or the information, products, or services contained therein.
+
+The use of any linked third-party content is at your own risk, and you will be subject to the terms
+and conditions, and privacy policies applicable to such third-party content.
+
+## 4. Trademarks
+
+Anybus®, Ewon®, Talk2M® and Ixxat® are internationally registered trademarks of HMS Industrial
+Networks, covering the European Union, USA and other countries.
+
+Intesis® is a registered trademark of HMS Industrial Networks in the European Union and is
+trademarked ™ in the rest of the world.
+
+Hardware Meets Software™ is trademarked globally by HMS. Other third-party logotypes, trademarks,
+product or service names mentioned are the property of their respective companies and are included
+on HMS websites purely for information purposes.
+
+## 5. Trademark Protection
+
+Any company logo or trademark is the property of the respective company. Brands and names are
+mentioned purely for information purposes.
\ No newline at end of file
diff --git a/web-docs/docs/07-legal/02-CODE_OF_CONDUCT.mdx b/web-docs/docs/07-legal/02-CODE_OF_CONDUCT.mdx
new file mode 100644
index 00000000..af459993
--- /dev/null
+++ b/web-docs/docs/07-legal/02-CODE_OF_CONDUCT.mdx
@@ -0,0 +1,9 @@
+---
+id: code-of-conduct
+title: Code of Conduct
+sidebar_label: Code of Conduct
+---
+
+import CodeOfConduct from '../../../CODE_OF_CONDUCT.md';
+
+
\ No newline at end of file
diff --git a/web-docs/docs/07-legal/03-LICENSE.mdx b/web-docs/docs/07-legal/03-LICENSE.mdx
new file mode 100644
index 00000000..2c8b33da
--- /dev/null
+++ b/web-docs/docs/07-legal/03-LICENSE.mdx
@@ -0,0 +1,10 @@
+---
+id: license
+title: License
+sidebar_label: License
+---
+
+import CodeBlock from '@theme/CodeBlock';
+import License from '!!raw-loader!../../../LICENSE';
+
+{License}
\ No newline at end of file
diff --git a/web-docs/docs/07-legal/_category_.json b/web-docs/docs/07-legal/_category_.json
new file mode 100644
index 00000000..38e1c84b
--- /dev/null
+++ b/web-docs/docs/07-legal/_category_.json
@@ -0,0 +1,6 @@
+{
+ "label": "Legal",
+ "className": "legal",
+ "collapsed": true,
+ "collapsible": true
+}
\ No newline at end of file
diff --git a/web-docs/docs/08-developer/01-DEVELOPMENT_ENVIRONMENT.mdx b/web-docs/docs/08-developer/01-DEVELOPMENT_ENVIRONMENT.mdx
new file mode 100644
index 00000000..017973bc
--- /dev/null
+++ b/web-docs/docs/08-developer/01-DEVELOPMENT_ENVIRONMENT.mdx
@@ -0,0 +1,52 @@
+---
+id: development-environment
+title: Development Environment Information
+sidebar_label: Development Environment Information
+---
+
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+import SysReqIgnitionPartial from '@site/docs/_partial/_sys_req_ignition.mdx';
+import SysReqHardwarePartial from '@site/docs/_partial/_sys_req_hardware.mdx';
+
+## IDEs
+
+This project uses the Maven build system to automatically download libraries and dependencies, and
+to ensure consistent build behavior. As such, this project can be imported into any IDE that
+supports the Maven build system.
+
+## Command-Line
+
+Maven includes extensive support for the command-line interface (CLI). For more information about
+Maven command-line interface support, please refer
+to [https://maven.apache.org/run.html](https://maven.apache.org/run.html).
+
+## Requirements
+
+### Required Ignition Version
+
+
+
+#### Java and Maven Versions
+
+Ignition 8.1 and later requires the Java 11 JDK for module development. Any supported version(s) of Maven for Java 11
+may be used.
+
+### Required Hardware
+
+
+
+## Contributing
+
+Detailed information about contributing to this project can be found in
+the [Contribution Guidelines](03-CONTRIBUTION_GUIDELINES.mdx).
+
+## Support Notice
+
+The development environment information provided in this document is provided for informational purposes only. The
+development environment is provided by Inductive Automation on GitHub via examples and archetypes, and is subject to
+change at any time. HMS Networks is not responsible for the development environment, and does not provide support for
+the development environment.
+
+For more information about the development environment, please refer to
+the [inductiveautomation/ignition-sdk-examples](https://github.com/inductiveautomation/ignition-sdk-examples)
+repository on GitHub.
diff --git a/web-docs/docs/08-developer/02-LIBRARIES_DEPENDENCIES.mdx b/web-docs/docs/08-developer/02-LIBRARIES_DEPENDENCIES.mdx
new file mode 100644
index 00000000..a7dd71e8
--- /dev/null
+++ b/web-docs/docs/08-developer/02-LIBRARIES_DEPENDENCIES.mdx
@@ -0,0 +1,49 @@
+---
+id: libraries-and-dependencies
+title: Libraries and Dependencies
+sidebar_label: Libraries and Dependencies
+---
+
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+
+## Libraries and Dependencies
+
+<>The {ScDocusaurusConfig.title} comes pre-bundled with all of its required libraries and dependencies. When developing,
+these libraries will automatically be downloaded and managed by the Maven build system.>
+
+### Adding Libraries and Dependencies
+
+As required, you can include additional libraries or dependencies using the Maven build system. To
+include a new library or dependency, add a new `` block in
+the `` section of your `pom.xml`. For example,
+
+```xml
+
+
+ ...
+
+ commons-lang
+ commons-lang
+ 2.6
+
+ ...
+
+```
+
+:::caution
+
+<>Additional libraries or dependencies must support Java 11, and shall not conflict with Ignition, the
+{ScDocusaurusConfig.title}, or its libraries and dependencies.>
+
+:::
+
+### Current Libraries and Dependencies
+
+<>The following libraries and dependencies are currently included in the {ScDocusaurusConfig.title}:>
+
+| Library/Dependency | License |
+|------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| [Apache HttpClient5](https://hc.apache.org/httpcomponents-client-5.0.x/index.html) | [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0) |
+| [Google Gson](https://github.com/google/gson) | [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0) |
+| [OpenCSV](http://opencsv.sourceforge.net/) | [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0) |
+
diff --git a/web-docs/docs/08-developer/03-CONTRIBUTION_GUIDELINES.mdx b/web-docs/docs/08-developer/03-CONTRIBUTION_GUIDELINES.mdx
new file mode 100644
index 00000000..f0a93df0
--- /dev/null
+++ b/web-docs/docs/08-developer/03-CONTRIBUTION_GUIDELINES.mdx
@@ -0,0 +1,8 @@
+---
+id: contribution-guidelines
+title: Contribution Guidelines
+sidebar_label: Contribution Guidelines
+---
+import ContributionGuidelines from '../../../CONTRIBUTING.md';
+
+
\ No newline at end of file
diff --git a/web-docs/docs/08-developer/_category_.json b/web-docs/docs/08-developer/_category_.json
new file mode 100644
index 00000000..c6f6a857
--- /dev/null
+++ b/web-docs/docs/08-developer/_category_.json
@@ -0,0 +1,6 @@
+{
+ "label": "Developer",
+ "className": "developer",
+ "collapsed": true,
+ "collapsible": true
+}
\ No newline at end of file
diff --git a/web-docs/docs/_partial/_accessing_tags.mdx b/web-docs/docs/_partial/_accessing_tags.mdx
new file mode 100644
index 00000000..ec412d52
--- /dev/null
+++ b/web-docs/docs/_partial/_accessing_tags.mdx
@@ -0,0 +1,4 @@
+The tags created by the connector are native Ignition tags and are updated cyclically by the connector based on the
+polling rates set during [configuration](../04-setup/03-CONFIGURATION.mdx) of the module.
+
+The `Tag Browser` tool in Ignition Designer can be used to read and write tag values.
\ No newline at end of file
diff --git a/web-docs/docs/_partial/_configuration.mdx b/web-docs/docs/_partial/_configuration.mdx
new file mode 100644
index 00000000..bbc6158c
--- /dev/null
+++ b/web-docs/docs/_partial/_configuration.mdx
@@ -0,0 +1,191 @@
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+import GreenCheckMark from '@site/static/img/green-check-icon-cc0v1.webp';
+import EwonWebPageHome from '@site/static/img/ewon-web-page-home.webp';
+import EwonWebPageVpnWizardBtn from '@site/static/img/ewon-web-page-vpn-wizard-btn.webp';
+import EwonWebPageVpnWizard from '@site/static/img/ewon-web-page-vpn-wizard.webp';
+import EwonTagConfigPageHistLogging from '@site/static/img/ewon-tag-config-page-hist-logging.webp';
+import EwonWebPageDataMgmt from '@site/static/img/ewon-web-page-data-mgmt.webp';
+import IgnitionWebPageConnectorConfig from '@site/static/img/ignition-web-page-connector-config.webp';
+import ConfigurationIgnitionPageDetailsPartial from '../_partial/_configuration_ignition_page_details.mdx';
+
+#### Ewon Configuration
+
+When setting up an Ewon, follow all standard Ewon Flexy documentation and installation
+guides.
+Documentation, installation guides, and more for the Ewon Flexy can be found
+at [https://websupport.ewon.biz/support](https://websupport.ewon.biz/support).
+
+<>In addition to the standard Ewon Flexy documentation, follow these additional steps to prepare the Ewon for use with
+the {ScDocusaurusConfig.title}.>
+
+##### I. Link Ewon to Talk2M
+
+###### Step 1
+
+Open the Ewon web page.
+
+
+
+###### Step 2
+
+Navigate to the VPN Wizard page by clicking `Wizards` at the top right of the page, and select `VPN`.
+
+
+
+###### Step 3
+
+Select the `Configure Talk2M connectivity` option.
+
+
+
+###### Step 4
+
+Follow the prompts to connect the Ewon to Talk2M.
+
+###### Step 5
+
+Once the VPN Wizard is complete, you may proceed to the [next section](#ii-setup-historical-logging-for-tags).
+
+
+
+##### II. Setup Historical Logging for Tags
+
+###### Step 1
+
+Open the Ewon web page.
+
+
+
+###### Step 2
+
+Navigate to the `Values` page (On the left-hand menu, click `Tags` > `Values`).
+
+###### Step 3
+
+Change the `MODE` to `Setup`.
+
+###### Step 4
+
+For each tag that requires logged data, double-click the tag to open the `Tag configuration` menu.
+
+###### Step 4a
+
+Scroll down to the `Historical Logging` section and check the `Historical Logging Enabled` checkbox.
+
+###### Step 4b
+
+In the same `Historical Logging` section, enable either deadband or interval logging.
+
+:::info Deadband Logging
+
+The Logging Deadband field triggers logging when the tag's value changes by a particular amount.
+For example, a logging deadband of 2 means that a tag will be logged when the value changes by 2 or more.
+A negative value in the logging deadband field disables logging on value change.
+
+:::
+:::info Interval Logging
+
+The Logging Interval field triggers time-based logging.
+For example, a logging interval of 60 means that the tag will be logged every 60 seconds.
+A logging interval of zero (0) disables time-based logging.
+
+:::
+
+###### Step 4c
+
+Once configured, click `Update Tag` on the bottom right of the page.
+
+
+
+###### Step 5
+
+Once all tags have been configured, you may proceed to the [next section](#iii-enable-historical-data-in-datamailbox).
+
+
+
+:::tip
+
+You may change the `MODE` back to `View` to see the tag values once you are done configuring the tags.
+
+:::
+
+##### III. Enable Historical Data In DataMailbox
+
+###### Step 1
+
+Open the Ewon web page.
+
+
+
+###### Step 2
+
+Navigate to the `Data Management` page (On the left-hand menu, click `Setup` > `System` > `Main` > `Data Management`).
+
+
+
+###### Step 3
+
+Check the `Historical Data` checkbox.
+
+###### Step 4
+
+Set the `DataMailbox upload interval` to a reasonable number for your application.
+
+:::info
+
+The `DataMailbox upload interval` sets how often the Flexy will send batches of historical data to DataMailbox and does
+not affect the frequency at which tag values are logged.
+
+:::
+
+###### Step 5
+
+Click `Update` at the bottom of the page to save the changes.
+
+###### Step 6
+
+Once the changes have been saved, you may proceed to the [next section](#connector-configuration).
+
+
+
+#### Connector Configuration
+
+##### Step 1
+
+Open the Ignition Gateway web page.
+
+##### Step 2
+
+Navigate to the `Config` page (On the left-hand menu, click `Config`).
+
+##### Step 3
+
+Under the `Tags` section, click `Ewon Connector`.
+
+:::tip
+
+If the `Ewon Connector` page is not visible, verify that the Ewon Connector module has been installed correctly.
+
+:::
+
+
+
+##### Step 4
+
+Populate the fields on the `Ewon Connector` page.
+
+
+
+##### Step 5
+
+Click `Save Changes` at the bottom of the page to save the changes.
+
+##### Step 6
+
+Restart Ignition.
+
+##### Step 7
+
+<>Once Ignition has restarted, you may begin using the {ScDocusaurusConfig.title} module.>
+
+
\ No newline at end of file
diff --git a/web-docs/docs/_partial/_configuration_ignition_page_details.mdx b/web-docs/docs/_partial/_configuration_ignition_page_details.mdx
new file mode 100644
index 00000000..0997d7b3
--- /dev/null
+++ b/web-docs/docs/_partial/_configuration_ignition_page_details.mdx
@@ -0,0 +1,190 @@
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+
+* **General**
+ * **Enabled** - Option to enable or disable the module.
+ :::info
+ When this option is disabled, the module will not run, but can remain installed and configured.
+
+ This option is useful for temporarily disabling the module without losing the configuration, or for maintenance
+ purposes.
+ :::
+
+ * **Poll Rate in Minutes** - Option to configure the poll rate for historical data via DataMailbox
+ :::info
+ This option allows for the configuration of how often the module polls for historical data via DataMailbox.
+
+ The default value is 1 minute, but this can be increased (in minute intervals) to reduce DataMailbox usage.
+ :::
+
+ * **Realtime Poll Rate in Seconds** - Option to configure the poll rate for realtime data via M2Web (where
+ applicable)
+ :::info
+ This option allows for the configuration of how often the module polls for realtime data from an Ewon via M2Web.
+
+ The default value is 10 seconds, but this can be increased or decreased (in second intervals) to reduce Ewon and
+ M2Web usage.
+ :::
+
+ * **Metadata Update Rate in Minutes** - Option to configure the poll rate for Ewon/tag metadata updates
+ :::info
+ This option allows for the configuration of how often the module polls for Ewon/tag metadata. This includes
+ new Ewon devices, new tags, and updated tag metadata such as descriptions and data types.
+
+ The default value is 30 minutes, but this can be increased or decreased (in minute intervals) to reduce
+ Ewon and M2Web usage.
+
+ Regardless of the value configured, the module will perform an initial metadata update upon startup.
+ Until this initial metadata update is complete, the module will not poll for tag data.
+ :::
+
+* **Talk2M Account Information**
+ * **Account** - Option to configure the Talk2M account to use for the module
+ :::info
+ This option allows for the configuration of the Talk2M account name which will be used for the module.
+ :::
+
+ * **Username** - Option to configure the Talk2M username to use for the module
+ :::info
+ This option allows for the configuration of the Talk2M username which will be used for the module.
+ :::
+
+ * **Change Password?** - Option to enable the password field for the Talk2M account
+ :::info
+ This option enables the password field for the Talk2M account.
+ This field is disabled by default to prevent unexpected or accidental password changes.
+ :::
+
+ * **Password** - Option to configure the Talk2M password to use for the module
+ :::info
+ This option allows for the configuration of the Talk2M password which will be used for the module.
+ This field is disabled by default to prevent unexpected or accidental password changes, and must be enabled
+ by selecting the `Change Password?` option above.
+ :::
+
+ * **Talk2M Token** - Option to configure the Talk2M token to use for the module
+ :::info
+ This option allows for the configuration of the Talk2M token which will be used for the module.
+
+ Talk2M tokens can be generated using eCatcher.
+ To learn more about Talk2M tokens and how to generate them, please refer to Section 4.6 of the DMWeb API reference
+ guide found
+ at: [DMWeb API Reference Guide](https://developer.ewon.biz/system/files_force/rg-0005-00-en-reference-guide-for-dmweb-api.pdf)
+ :::
+
+ * **Talk2M Developer ID** - Option to configure the Talk2M developer ID to use for the module
+ :::info
+ This option allows for the configuration of the Talk2M developer ID which will be used for the module.
+
+ Talk2M developer IDs must be requested from HMS.
+ If you do not have a Talk2M Developer ID, you may request one
+ here: [https://developer.ewon.biz/registration](https://developer.ewon.biz/registration).
+ :::
+
+* **Ewon Device Information**
+ * **Ewon Username** - Option to configure the Ewon device username to use for the module
+ :::info
+ This option allows for the configuration of the Ewon device username which will be used for the module. This
+ username must be identical for all linked Ewons.
+
+ All linked Ewons must have at least one common user account to enable realtime and write functionality via M2Web.
+ The username and password can be any valid combination, but must be consistent across all linked Ewons.
+ :::
+
+ * **Change Password?** - Option to enable the password field for the Ewon device
+ :::info
+ This option enables the password field for the Ewon device.
+ This field is disabled by default to prevent unexpected or accidental password changes.
+ :::
+
+ * **Ewon Password** - Option to configure the Ewon device password to use for the module
+ :::info
+ This option allows for the configuration of the Ewon device password which will be used for the module.
+ This field is disabled by default to prevent unexpected or accidental password changes, and must be enabled
+ by selecting the `Change Password?` option above. This password must be identical for all linked Ewons.
+
+ All linked Ewons must have at least one common user account to enable realtime and write functionality via M2Web.
+ The username and password can be any valid combination, but must be consistent across all linked Ewons.
+ :::
+
+
+* **History**
+ * **History Enabled** - Option to enable DataMailbox historical data logging to a history provider.
+ :::info
+ When this option is enabled, the connector will log historical data to the history provider specified in the
+ `Target History Provider` field.
+
+ When this option is disabled, the connector will only log historical data to the tag provider.
+ :::
+
+ * **Target History Provider** - Option to select the history provider to log historical data to.
+ :::info
+ When the `History Enabled` option is enabled, the connector will log historical data to the history provider
+ specified in this field.
+ :::
+
+* **Advanced**
+ * **Debug Enabled** - Option to enable debug logging.
+ :::info
+ When this option is enabled, the connector will log additional information to the Ignition console.
+ This option is useful for troubleshooting, and includes information such as:
+ * HTTP request IDs and status updates (i.e., HTTP request started, HTTP request finished)
+ * Consistent warning logs (i.e., offline Ewon warnings not suppressed after the first warning)
+ * General connector state information (i.e., start and finish of polling cycles)
+
+ Unless you are troubleshooting, it is recommended to leave this option disabled.
+ Debug logging may impact performance.
+ :::
+
+ * **Combine Live Data:** Option to combine live data with historical data.
+ :::info
+ When this option is enabled, tags that are read in realtime will be combined with historical data, if available.
+ This option has no effect when the `Read all values in realtime` option is enabled.
+
+ The connector will only combine historical data with realtime data if the historical data was already read from
+ DataMailbox.
+ For example, when some tags (not all) are configured to be read in realtime, a DataMailbox transaction will be
+ performed to read the historical data for the tags that are not configured to be read in realtime.
+ If historical data is also included for the tags that are read in realtime, the
+ connector will combine that historical data with the realtime data
+ (instead of omitting the historical data).
+ :::
+
+ * **Read all values in realtime** - Option to always read all tag values in realtime.
+ :::info
+ When this option is enabled, all tags will be read in realtime.
+
+ This option disables DataMailbox reads.
+ Historical values logged on the Ewon will not be logged in Ignition.
+ :::
+
+ * **Tag Write Buffer Length (ms)** - Option to configure tag write buffering (and the associated buffer length).
+ :::info
+ When this option is configured to -1 or any value below the minimum of 100, tag write buffering is not enabled,
+ and tag writes are sent to the Ewon immediately.
+ When this option is configured to a value above the minimum of 100, tag writes will be buffered for the specified
+ length of time before sending them to the Ewon.
+
+ Each time a tag is written, it is added to a buffer.
+ If it is the first tag in the buffer, a timer is started.
+ Otherwise, it is added to the existing buffer.
+ When the buffer length timer has elapsed, all buffered tag writes are sent to each Ewon in a single request.
+ :::
+
+ * **Sort Tags by Group** - Option to enable tag sorting by group.
+ :::info
+ When this option is enabled, tags are sorted into folders for each Ewon, based on their tag groups.
+
+ For each Ewon, a folder is created for each tag group combination and tags are placed in their respective group
+ folder.
+ If a tag is not in a group, it is placed in the root Ewon tag folder.
+ If a tag is in multiple groups, it is placed in the folder with a name that is the concatenation of all groups.
+ For example, if a tag is in the groups `A` and `C`, it will be placed in the folder `AC`.
+ :::
+
+ * **Disable Tag Name Checking** - Option to disable tag name checking.
+ :::info
+ When this option is enabled, tag names are not checked for invalid characters.
+
+ By default, tag names are checked for invalid characters.
+ If a tag name contains an invalid character, it is replaced with an underscore (`_`).
+ :::
\ No newline at end of file
diff --git a/web-docs/docs/_partial/_download.mdx b/web-docs/docs/_partial/_download.mdx
new file mode 100644
index 00000000..b89e426c
--- /dev/null
+++ b/web-docs/docs/_partial/_download.mdx
@@ -0,0 +1,9 @@
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+
+<>The {ScDocusaurusConfig.title} Module can be downloaded by clicking the 'Download' button in the menu above (top-left
+corner for mobile and small devices).>
+
+To run and install the connector, you need to download the latest asset named `EwonConnector-X_Y-A.B.C.zip` where X_Y
+and A.B.C are the Ignition and module version numbers.
+
+
\ No newline at end of file
diff --git a/web-docs/docs/_partial/_features.mdx b/web-docs/docs/_partial/_features.mdx
new file mode 100644
index 00000000..5b9b4cd2
--- /dev/null
+++ b/web-docs/docs/_partial/_features.mdx
@@ -0,0 +1,39 @@
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+
+### Synchronize Ewon Flexy Tag Data to Ignition's Tag Historian
+
+- Historical data via the Ewon DataMailbox API (default)
+- Realtime (live) data via the Ewon M2Web API
+- Flexible configuration options
+ - Enable realtime updates for all tags, per-Ewon, or per-tag
+ - Enable organization of tags into folders by their tag group(s)
+ - Combine realtime tag data with historical data (if present in DataMailbox)
+ - Configurable historical and realtime update rates (up to 1 minute for historical, 1 second for realtime)
+
+### Write Tag Data to Ewon Flexy Tags
+
+- Tag data can be written to Ewon Flexy tags via the Ewon M2Web API
+- No additional configuration required
+- Configurable write buffering for improved performance
+
+### Simple, Scalable Configuration
+
+- Configuration is done via a simple, user-friendly web interface
+- One connector and configuration for all Ewon Flexy devices
+
+:::note
+
+<>The {ScDocusaurusConfig.title} supports one (1) Talk2M account at a time. Any number of Ewon Flexy devices may be
+used with the connector, but they must all be registered to the same Talk2M account.
+>
+
+:::
+
+### Take Advantage of Ignition's Powerful Features
+
+- With Ewon Flexy tag data in Ignition, you can take advantage of Ignition's powerful features
+ - Alarming
+ - Reporting
+ - Scripting
+ - Perspective
+ - And [more](https://inductiveautomation.com/ignition/)!
\ No newline at end of file
diff --git a/web-docs/docs/_partial/_installation_or_upgrade.mdx b/web-docs/docs/_partial/_installation_or_upgrade.mdx
new file mode 100644
index 00000000..3d6bab8c
--- /dev/null
+++ b/web-docs/docs/_partial/_installation_or_upgrade.mdx
@@ -0,0 +1,31 @@
+import GreenCheckMark from '@site/static/img/green-check-icon-cc0v1.webp';
+
+#### Step 1
+
+On the Gateway Webpage, select `Config` > `SYSTEM` > `Modules` to open the Module Configuration page.
+
+
+
+#### Step 2
+
+Scroll to the bottom on the list, find the blue arrow, and click the `Install or Upgrade a Module` link.
+
+
+
+#### Step 3
+
+Click `Choose File`, select a .modl file that you have previously downloaded.
+
+
+
+#### Step 4
+
+Click Install.
+
+* When the page reloads, you can now see the module you installed in the list of modules.
+
+#### Step 5
+
+Restart Ignition for the changes to fully take effect.
+
+
\ No newline at end of file
diff --git a/web-docs/docs/_partial/_restarting_module.mdx b/web-docs/docs/_partial/_restarting_module.mdx
new file mode 100644
index 00000000..28468865
--- /dev/null
+++ b/web-docs/docs/_partial/_restarting_module.mdx
@@ -0,0 +1 @@
+Restart the module by navigating to `Config` > `Modules` and clicking `restart` next to the module.
\ No newline at end of file
diff --git a/web-docs/docs/_partial/_sys_req_hardware.mdx b/web-docs/docs/_partial/_sys_req_hardware.mdx
new file mode 100644
index 00000000..67e163ec
--- /dev/null
+++ b/web-docs/docs/_partial/_sys_req_hardware.mdx
@@ -0,0 +1,37 @@
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+
+<>The {ScDocusaurusConfig.title} has been designed to take advantage of the Ignition server's available hardware
+resources. Multi-threading and asynchronous processing allow the connector to simultaneously handle multiple requests at
+a time. >
+
+#### Minimum Hardware Requirements
+
+CPU: 2 cores
+RAM: 4 GB
+
+:::caution
+
+The minimum hardware requirements are suitable for a small number of devices and tags. If you are planning to connect
+many devices or tags, you should consider increasing the hardware resources available to Ignition and its modules.
+
+These requirements match those of Ignition, with additional memory (RAM) required for the connector to run.
+
+:::
+
+#### Recommended Hardware Requirements
+
+CPU: 4 cores
+RAM: 8 GB
+
+:::tip
+
+The recommended hardware requirements are suitable for most installations. If you are planning to connect a large number
+devices and/or tags, you should consider increasing the hardware resources available to Ignition and its modules.
+
+There is no upper limit on the number of devices and tags that can be connected to the connector, but the hardware
+resources available to Ignition will limit the number of devices and tags that can be connected. If you experience
+a degradation in performance, it is recommended to increase the hardware resources available to Ignition and its
+modules. This may include increasing the number of CPU cores, increasing the amount of RAM, or increasing the amount of
+storage space available to Ignition.
+
+:::
diff --git a/web-docs/docs/_partial/_sys_req_ignition.mdx b/web-docs/docs/_partial/_sys_req_ignition.mdx
new file mode 100644
index 00000000..4bf67f55
--- /dev/null
+++ b/web-docs/docs/_partial/_sys_req_ignition.mdx
@@ -0,0 +1,18 @@
+import ScDocusaurusConfig from "@site/ScDocusaurusConfig.js";
+
+<>The {ScDocusaurusConfig.title} module has been designed to work with Ignition {ScDocusaurusConfig.minIgnitionVersion}
+ and newer.>