Currently the QR code in the live demo is showing fuzzy.

This can be fixed with CSS: img{image-rendering: pixelated;}

A lot of dev ask if arianeejs works on nodejs (server side).

Add in the doc that it works for both

At current, <style> tags are mixed into markdown file, separate them to CSS files

• This will improve readability and maintainability

An entity "Arianee SAS" is referenced without introduction at https://docs.arianee.org/docs/howToProceed

What is this entity?

Also, please say the name of the entity which publishes docs.arianee.org and arianee.org here:

Please use the full, legal name of the entity. Bonus points if you will mention the corporation registration number and jurisdiction.

Also, update the WHOIS registration to match.

Too many blockchain projects register their company in weird ways, or not at all. In contrast, we are a professional organization and we should have a MUCH higher standard than blockchain projects. Our benchmark should be companies that have existed 50 years or more.

This will help guide this review. But more importantly it will help attract high-quality contribution to the document.

Recommendation:

This documentation is for contributors to applications released by the Arianee project (published under https://github.com/Arianee/) and third-party applications that work with Arianee.

For example, to edit the Arianee Economy page, the link is: https://github.com/Arianee/docs/edit/master/docs/AriaEconomy.md

[Uploading... image.png ]

Update and change to reflect the new Arianee Docs

OPTION 2
On the page https://docs.arianee.org/docs/ArianeeJS

The line is shown:

<script src="https://unpkg.com/@arianee/arianeejs@latest/browser/bundle.js">

This line of code is an unacceptable risk. On the modern web, best practice is to use sub-resource integrity for all external links.

Potential fixes:

1. Link to a specific version, include SRI, update documentation with the new URI+SRI each time the library is updated
2. Add a note in the documentation about the risk of not including SRI

I recommend the latter for now. After the API is very stable then we can switch to the former.

git grep '' | cat docs/ArianeeAsset-i18n.md:
docs/ArianeeAsset-i18n.md: docs/ArianeeAsset.md:
docs/ArianeeAsset.md: docs/ArianeeBrandIdentity-i18n.md:
docs/ArianeeBrandIdentity-i18n.md: docs/ArianeeEvent-i18n.md:
docs/ArianeeEvent-i18n.md: docs/ArianeeIdentity-i18n.md:
docs/ArianeeIdentity-i18n.md: docs/ArianeeIdentity.md:
docs/ArianeeIdentity.md: docs/ArianeeJS.md:
docs/ArianeeJS.md: docs/ArianeeJS.md:
docs/ArianeeJS.md: docs/ArianeeJS.md:
docs/ArianeeJS.md: docs/ArianeeJS.md:
docs/ArianeeJS.md: docs/ArianeeJS.md:
docs/ArianeeJS.md: docs/ArianeeJS.md:
docs/ArianeeJS.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSCertificate.md:
docs/ArianeeJSCertificate.md: docs/ArianeeJSEconomy.md:
docs/ArianeeJSEconomy.md: docs/ArianeeJSEconomy.md:
docs/ArianeeJSEconomy.md: docs/ArianeeJSEconomy.md:
docs/ArianeeJSEconomy.md: docs/ArianeeJSEconomy.md:
docs/ArianeeJSEconomy.md: docs/ArianeeJSEconomy.md:
docs/ArianeeJSEconomy.md: docs/ArianeeJSEconomy.md:
docs/ArianeeJSEconomy.md: docs/ArianeeJSEconomy.md:
docs/ArianeeJSEconomy.md: docs/ArianeeJSEconomy.md:
docs/ArianeeJSEconomy.md: docs/ArianeeJSEconomy.md:
docs/ArianeeJSEconomy.md: docs/ArianeeJSEconomy.md:
docs/ArianeeJSEconomy.md: docs/ArianeeJSEconomy.md:
docs/ArianeeJSEconomy.md: docs/ArianeeJSWallet.md:
docs/ArianeeJSWallet.md: docs/ArianeeJSWallet.md:
docs/ArianeeJSWallet.md: docs/ArianeeJSWallet.md:
docs/ArianeeJSWallet.md: docs/ArianeeJSWallet.md:
docs/ArianeeJSWallet.md: docs/ArianeeJSWallet.md:
docs/ArianeeJSWallet.md: docs/ArianeeJSWallet.md:
docs/ArianeeJSWallet.md: docs/ArianeeJSWallet.md:
docs/ArianeeJSWallet.md: docs/ArianeeJSWallet.md:
docs/ArianeeJSWallet.md: docs/ArianeeJSWallet.md:
docs/ArianeeJSWallet.md: docs/ArianeeJSWallet.md:
docs/ArianeeJSWallet.md: docs/ArianeeProductCertificate-i18n.md:
docs/ArianeeProductCertificate-i18n.md: docs/arianeeJS-SDK/README.md:
docs/arianeeJS-SDK/README.md: docs/arianeeJS-SDK/README.md:
docs/arianeeJS-SDK/README.md: docs/arianeeJS-SDK/README.md:
docs/arianeeJS-SDK/README.md: docs/arianeeJS-SDK/README.md:
docs/arianeeJS-SDK/README.md: docs/arianeeJS-SDK/README.md:
docs/arianeeJS-SDK/README.md: docs/arianeeJS-SDK/README.md:
docs/arianeeJS-SDK/README.md: website/README.md:
website/README.md: website/README.md:
website/README.md: website/README.md:
website/README.md: website/README.md:
website/README.md: website/README.md:
website/README.md: website/README.md:
website/README.md:```

These should all have a language specified.

• Establish when words should be in title case or sentence case.
  • Currently there are inconsistencies for example on the left of each page, "KYB Process" is title case but "Staking policy" is sentence case.
• Choose between ARIA and Aria, both are currently used.
• Choose between Arianee .Wallet, Arianee Wallet, arianee wallet and Wallet, each is currently used.
• Choose between arianeeJS and ArianeeJS, both are currently used.

• docs/intro.md => docs/introduction.md
• docs/arianeeproject.md => docs/arianee-project.md
• docs/AriaEconomy => docs/arianee-enocomy.md
• In general lowercase, hyphenated words

Also, this should be part of the style guide.

After a PR on Docs, it should deploy docs to productions.

Command line that I currently use :
GIT_USER=gnarco CURRENT_BRANCH=master USE_SSH=true npm run publish-gh-pages

Update README to show which website this repo represents.