mxc-foundation · jeffstahlnecker · Jun 30, 2021 · Jun 30, 2021 · Jun 30, 2021 · Jun 30, 2021
diff --git a/i18n/de/docusaurus-plugin-content-blog/2019-05-30-welcome.md b/i18n/de/docusaurus-plugin-content-blog/2019-05-30-welcome.md
@@ -2,10 +2,12 @@
 slug: welcome
 title: Welcome
 author: Jeff Stahlnecker
-author_title: Front End Engineer @ Facebook
+author_title: Head of Development at MXC Foundation
 author_url: https://github.com/jeffstahlnecker
 author_image_url: https://avatars.githubusercontent.com/u/45363541?v=4
-tags: [welcome, intro]
+tags:
+  - welcome
+  - intro
 ---
 
 It's the beginning. Since I returned to the community following the Miner Health release, I've been saying that we'll impove transparency in development at MXC. This site is the beginning of this transparency. More content will be added here.
diff --git a/i18n/de/docusaurus-plugin-content-blog/2021-05-30-welcome.md b/i18n/de/docusaurus-plugin-content-blog/2021-05-30-welcome.md
@@ -0,0 +1,13 @@
+---
+slug: welcome
+title: Welcome
+author: Jeff Stahlnecker
+author_title: Head of Development at MXC Foundation
+author_url: https://github.com/jeffstahlnecker
+author_image_url: https://avatars.githubusercontent.com/u/45363541?v=4
+tags:
+  - welcome
+  - intro
+---
+
+It's the beginning. Since I returned to the community following the Miner Health release, I've been saying that we'll impove transparency in development at MXC. This site is the beginning of this transparency. More content will be added here.
diff --git a/i18n/de/docusaurus-plugin-content-blog/2021-07-05-tech-update.md b/i18n/de/docusaurus-plugin-content-blog/2021-07-05-tech-update.md
@@ -0,0 +1,36 @@
+---
+slug: 2021-07-05-tech-update
+title: Tech Update - July 5, 2021
+author: Jeff Stahlnecker
+author_title: Head of Development @ MXC Foundation
+author_url: https://github.com/jeffstahlnecker
+author_image_url: https://avatars.githubusercontent.com/u/45363541?v=4
+tags:
+  - tech update
+  - datadash
+  - supernode
+  - dhx
+---
+
+Welcome to the very first MXC tech update!
+
+This week the tech team has been extremely busy. Throughout the past sprint we've focused on closing any and all ongoing projects. That brought us back to a few "low hanging" items that will add some EPIC value to our users -- especially those interested in connecting LoRa devices.
+
+## Device Provisioning
+Our very own backend engineer Lixuan took a deep dive to test the device provisioning system built by Ian to ensure that it was ready to be added with our live code. She solved a number of conflicts (device provisioning has been *ready* since January!), then ran it through a round of rigorous testing. This was done in collaboration with MatchX embedded software engineer Ian. They did some great work, and you'll see device provisioning going live early this week. In the meantime, you can check out the technical documentation here: [Device Provisioning FAQ](/docs/tutorials/devices/provisioning)
+
+As part of our focus on devices during the past two weeks, Lixuan also solved an issue which kept users from adding new devices on a supernode. We should be in ship-shape, and ready for some developer interaction. Feel free to send us your feedback! :)
+
+## Foundation for DHX Simulator Improvement
+The DataDash DHX Simulator has been a long-standing issue. While it works, it's a little buggy, and once in a while spits out something unexpected. Our backend developer Pavel decided enough is enough, and jumped in to solve the challenge of the buggy simulator. To accomplish this he brought together the required information from a ton of different sources and built an API for the DataDash team to integrate. For those developers out there, I'll update this post with a link to the API as soon as it is live.
+
+## Improved Technical Support
+We've been working hard to improve the technical support services provided by both MXC and MatchX. Our Tech Support Engineer Latifah has been hard at work building a ticketing system, integrating Discord, writing an internal support knowledgebase, while naturally also responding to your support requests. She's done an excellent job, and has set a strong foundation for reliable support moving forward.
+
+## Cleaning up the DataDash
+Over the past two weeks our DataDash team has focused primarily on solving some pesky issues with the app. We also added support for DHX in the in-app address book. Just another feature to make life a little easier for you.
+
+## Contributing to DataHighway
+Team members Luke, Ayush and Christian updated the DataHighway blockchain to add multisig functionality. They also made a number of improvements, and fixed issues with the Harbour testnet. You can review the full release notes [here](https://github.com/DataHighway-DHX/node/releases/tag/v3.0.5).
+
+That's the newest from Tech, and I'll be sure to update this post with that API link as soon as it goes live. 
diff --git a/i18n/de/docusaurus-plugin-content-blog/2021-07-20-tech-update.md b/i18n/de/docusaurus-plugin-content-blog/2021-07-20-tech-update.md
@@ -0,0 +1,66 @@
+---
+slug: 2021-07-20-tech-update
+title: Tech Update - July 20, 2021
+author: Jeff Stahlnecker
+author_title: Head of Development @ MXC Foundation
+author_url: https://github.com/jeffstahlnecker
+author_image_url: https://avatars.githubusercontent.com/u/45363541?v=4
+tags:
+  - tech update
+  - datadash
+  - dhx
+  - mxc controller
+  - device provisioning
+---
+
+It's hard to believe it's been another two weeks --- and we've been EXTREMELY busy polishing up some pretty epic features.
+
+### All About Device Provisioning
+It took us quite some time to get the [device provisioning](/docs/tutorials/devices/provisioning) developer preview ready. A bit longer than expected. Device provisioning interacts with a number of supernode systems on a regular basis, meaning that each of these interactions had to be thoroughly tested. During that process we found some items that could cause issues when the system scales, so we went ahead and took the time to resolve those before pushing out the feature. I'm excited to say that the device provisioning developer preview is now live and ready for action. If you want to get a manufacturer ID and begin testing the system, email support@mxc.org.
+
+In the meantime, Ian is actively working on providing a sample lora device source code to make it easier for manufacturers (and tinkerers) to get started.
+
+### DataDash Goes Dark (for beta testers)
+That's right! We're working hard on getting dark mode out there for all of you night owls. If you want to get a sneak peek at dark mode and provide some epic feedback for us, you can join the live beta by using the command `!role ios` or `!role android` in our [Discord Community](https://mxc.news/discord). This will get you access to the dedicated beta channel for your phone, which provides you with the information you need to get signed up.
+
+:::caution
+
+Beta releases have bugs. By joining the beta, you will experience these bugs. If you find an issue, always report it directly to us in our [GitHub Repo](https://github.com/mxc-foundation/supernode-app/issues/new?assignees=&labels=bug%2Ctriage&template=bug_report.yml&title=%5BBug%5D%3A+).
+
+:::
+
+### Tech Support Continues to Amaze
+Ok I just had to say this one. Yes it sounds markety, and I know not everyone is always amazed, but I'm very happy with it. Within a few weeks our new Tech Support Engineer Latifah has gone from "first day with LoRa" to actively troubleshooting miners, certifying issues, finding solutions for said issues, and of course ensuring that each member of our community receives top of the line technical support.
+
+Keep in mind, the only way to get "official" technical support is to email support@mxc.org or by using the `/support` command in our [Discord Server](https://mxc.news/discord).
+
+### MXC Controller - the news on the Web App
+For those of you digging into the nitty-gritty of the LoRa/LPWAN infrastructure, I'm sure you've noticed a few issues with the current web app. We know about those, and we're working on rolling out a new web app to solve all of these issues. Because we've decided to move from React to a Flutter based web app, it will take us just a bit of time to get started.
+
+This week we started cross-training our React developer Nam to start working with Flutter. While he's been studying, he also worked with the Flutter team to outline the base architecture of the application so that we can finalize the overall design in our upcoming sprint.
+
+The MXC Controller will be available as beta during development. This will provide you with early access to key pages, while keeping you informed that it's beta, and will probably have a few bugs.
+
+:::caution
+
+Beta releases will have bugs. Just pointing that out again.
+
+:::
+
+Our first release will include:
+* Base architecture
+* Sign-in / Register
+* Device Management/Configuration pages
+
+I'll keep you updated on the status of this as we move forward, and of course I'll share the GitHub repo when the development begins.
+
+
+### Continuing our Contribution to DataHighway
+We haven't forgotten DataHighway and we still strongly believe in the future of this project. Blockchain developers Luke and Ayush have been hard at work to both improve the DataHighway, and bring governance on chain. There's been some progress made in that direction, however we're being über careful. As we progress further with the development, we'll start contributing to the documentation as well to ensure it's easier for others to participate.
+
+### Community Contributions
+This documentation is fluid, and anyone can work to help improve it. If you see something that you know about, and feel confident writing an article about, feel free to fork the repo, make the changes, and submit a pull request.
+
+Now I know that not everyone is familiar with GitHub. In that case, let me know on Discord and I'll open up a channel for us to chat. Either I'll teach you what you need to know to participate directly on GitHub, or you can just send me the article you believe should be in the documentation.
+
+That's been this week's news update --- uh yeah ok wrong channel. ;)
diff --git a/i18n/de/docusaurus-plugin-content-blog/2021-07-5-tech-update.md b/i18n/de/docusaurus-plugin-content-blog/2021-07-5-tech-update.md
@@ -0,0 +1,36 @@
+---
+slug: 2021-07-05-tech-update
+title: Tech Update - July 5, 2021
+author: Jeff Stahlnecker
+author_title: Head of Development @ MXC Foundation
+author_url: https://github.com/jeffstahlnecker
+author_image_url: https://avatars.githubusercontent.com/u/45363541?v=4
+tags:
+  - tech update
+  - datadash
+  - supernode
+  - dhx
+---
+
+Welcome to the very first MXC tech update!
+
+This week the tech team has been extremely busy. Throughout the past sprint we've focused on closing any and all ongoing projects. That brought us back to a few "low hanging" items that will add some EPIC value to our users -- especially those interested in connecting LoRa devices.
+
+## Device Provisioning
+Our very own backend engineer Lixuan took a deep dive to test the device provisioning system built by Ian to ensure that it was ready to be added with our live code. She solved a number of conflicts (device provisioning has been *ready* since January!), then ran it through a round of rigorous testing. This was done in collaboration with MatchX embedded software engineer Ian. They did some great work, and you'll see device provisioning going live early this week. In the meantime, you can check out the technical documentation here: [Device Provisioning FAQ](/docs/tutorials/devices/provisioning)
+
+As part of our focus on devices during the past two weeks, Lixuan also solved an issue which kept users from adding new devices on a supernode. We should be in ship-shape, and ready for some developer interaction. Feel free to send us your feedback! :)
+
+## Foundation for DHX Simulator Improvement
+The DataDash DHX Simulator has been a long-standing issue. While it works, it's a little buggy, and once in a while spits out something unexpected. Our backend developer Pavel decided enough is enough, and jumped in to solve the challenge of the buggy simulator. To accomplish this he brought together the required information from a ton of different sources and built an API for the DataDash team to integrate. For those developers out there, I'll update this post with a link to the API as soon as it is live.
+
+## Improved Technical Support
+We've been working hard to improve the technical support services provided by both MXC and MatchX. Our Tech Support Engineer Latifah has been hard at work building a ticketing system, integrating Discord, writing an internal support knowledgebase, while naturally also responding to your support requests. She's done an excellent job, and has set a strong foundation for reliable support moving forward.
+
+## Cleaning up the DataDash
+Over the past two weeks our DataDash team has focused primarily on solving some pesky issues with the app. We also added support for DHX in the in-app address book. Just another feature to make life a little easier for you.
+
+## Contributing to DataHighway
+Team members Luke, Ayush and Christian updated the DataHighway blockchain to add multisig functionality. They also made a number of improvements, and fixed issues with the Harbour testnet. You can review the full release notes [here](https://github.com/DataHighway-DHX/node/releases/tag/v3.0.5).
+
+That's the newest from Tech, and I'll be sure to update this post with that API link as soon as it goes live. 
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/tutorials/datadash/_category_.json b/i18n/de/docusaurus-plugin-content-docs/current/tutorials/datadash/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "DataDash",
+  "position": 6
+}
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/tutorials/datadash/beta.md b/i18n/de/docusaurus-plugin-content-docs/current/tutorials/datadash/beta.md
@@ -0,0 +1,20 @@
+---
+sidebar_position: 2
+title: DataDash Beta Testing
+---
+
+# DataDash Ongoing Beta
+At the moment we have an open beta DataDash group for both iOS and Android. We consider this a semi-closed beta because we require participants to join our beta discord channels. This is key for discussions among participants, and provides us with an easy way to interact with beta participants.
+
+
+To participate as a beta tester follow the following steps:
+1. Join our [Discord Community](https://mxc.news/discord)
+1. Use the #bot-talk channel to send one of the following commands:
+    * `!role ios`
+    * `!role android`
+1. You will then see a new channel in the `development` category. Follow the steps outlined at the top of the channel to join your selected test group.
+
+## DataDash Closed Beta
+Before a major release, we will do a call for closed beta participants. This will have a limited number of available seats per operating system, and will only be available to current beta testers who actively submit feedback.
+
+Closed betas will provide users access to new and unreleased features that require a major backend change. Because of this, each participant will receive a test account on a "fake" supernode to work with.
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/tutorials/datadash/bugs.md b/i18n/de/docusaurus-plugin-content-docs/current/tutorials/datadash/bugs.md
@@ -0,0 +1,19 @@
+---
+sidebar_position: 2
+title: Reporting Bugs
+---
+
+# How to report DataDash Bugs
+
+The DataDash app codebase is [Publicly available on GitHub](https://github.com/mxc-foundation/supernode-app). Therefore the best way to submit a DataDash bug, is directly as a [GitHub issue](https://github.com/mxc-foundation/supernode-app/issues).
+
+Please include the following information in your bug report:
+
+* What is the problem?
+* What is the expected behavior?
+* Mark the issue with the appropriate labels:
+  * `bug`
+  * `ios` or `android`
+* Provide any additional information, screenshots, or videos you believe might be helpful.
+
+**GitHub Issues are public! Do not share any personal or identifiable information. If you believe the issue is specific to you, it should be submitted as a support ticket to [support@mxc.org](mailto:support.mxc.org).**
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/tutorials/datadash/intro.md b/i18n/de/docusaurus-plugin-content-docs/current/tutorials/datadash/intro.md
@@ -0,0 +1,35 @@
+---
+sidebar_position: 1
+title: Intro
+---
+
+# Introducing the DataDash App
+
+Our DataDash app has the following core functionality:
+* LPWAN Functionality
+  * M2 Pro Miner
+    * Register
+    * Manage Miner Health
+  * MXProtocol enabled devices (coming soon)
+    * Register
+    * View live data frames
+    * Generate MQTT credentials (for external data management tools)
+* Token Management
+  * MXC M2M Wallet
+  * DHX Wallet
+  * BTC Wallet (Withdrawals Only)
+
+
+## Downloading the DataDash App
+
+You can get the DataDash app at the following locations:
+
+**Android**
+* [Google Play Store](https://play.google.com/store/apps/details?id=com.mxc.smartcity)
+* [APK Download](https://datadash.oss-accelerate.aliyuncs.com/app-prod-release.apk)
+
+**iOS**
+* [App Store](https://apps.apple.com/us/app/datadash-app/id1509218470)
+
+## Participating with DataDash Development
+Our DataDash app is [open on GitHub](https://github.com/mxc-foundation/supernode-app) and anyone is welcome to participate in its improvement. To participate, clone the repo, and then tackle a [GitHub issue](https://github.com/mxc-foundation/supernode-app/issues). When you think you've solved it, submit a pull request for our team to review. Before getting started, take a look at the rules [here](https://github.com/mxc-foundation/supernode-app/blob/master/RETHINK.md).
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/tutorials/devices/integrations.md b/i18n/de/docusaurus-plugin-content-docs/current/tutorials/devices/integrations.md
@@ -1,15 +1,13 @@
 ---
-sidebar_position: 3 
+sidebar_position: 3
 title: Integrations
 ---
 
 # Device Integrations
 
 By default supernode provides MQTT broker service for users to subscribe or pushlish events on their devices.
 
-Users can subscribe to MQTT broker under topics in the servers after authentication. Before that, you need to make sure
-you have mosquitto package installed. Use the package manager apt to install these dependencies on the Ubuntu 18.04 LTS
-server:
+Users can subscribe to MQTT broker under topics in the servers after authentication. Before that, you need to make sure you have mosquitto package installed. Use the package manager apt to install these dependencies on the Ubuntu 18.04 LTS server:
 
 ```
 sudo apt-add-repository ppa:mosquitto-dev/mosquitto-ppa
@@ -161,7 +159,7 @@ Response
 Call
 
 ```shell
-curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Grpc-Metadata-Authorization: Bearer {{ .SUPERNODE_JWT }}' -d '{ "organizationId": "{{ .ORG_ID }}"}' 'https://{{ .SUPERNODE_URL }}/api/mosquitto-auth/login'
+curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Grpc-Metadata-Authorization: Bearer {{ .SUPERNODE_JWT }}' -d '{ "organizationId": "{{ .ORG_ID }}", "ttlInSeconds": "{{ .TIME_TO_LIVE_IN_SECONDS }}"}' 'https://{{ .SUPERNODE_URL }}/api/mosquitto-auth/login'
 ```
 
 Response
@@ -220,5 +218,4 @@ The message format should be as follow:
 - `confirmed`: whether the payload must be sent as confirmed data down or not
 - `fPort`: FPort to use (must be > 0)
 - `data`: base64 encoded data (plaintext, will be encrypted by Network Server)
-- `object`: decoded object (when application codec has been configured), when providing the 'object', you can omit '
-  data'
+- `object`: decoded object (when application codec has been configured), when providing the 'object', you can omit ' data'