ProxeusApp · loleg · Aug 31, 2023 · Dec 16, 2022 · Dec 16, 2022 · Dec 16, 2022
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
@@ -0,0 +1,13 @@
+version: 2
+updates:
+  # Maintain dependencies for Go
+  - package-ecosystem: "gomod"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+  # Maintain dependencies for JS
+  - package-ecosystem: "npm"
+    directory: "/ui/"
+    schedule:
+      interval: "weekly"
diff --git a/Dockerfile b/Dockerfile
@@ -1,4 +1,4 @@
-FROM debian:stable
+FROM debian:stable-slim
 
 RUN apt-get update && apt-get install -y \
         ca-certificates \

diff --git a/docs/_coverpage.md b/docs/_coverpage.md
@@ -1,8 +1,11 @@
 ![logo](_media/proxeus_logo.svg)
 
-# <small>1.0.0</small>
-> Blockchain-enabled documents and workflows
+> Your data. Your blockchain. Your business.
 
-Proxeus combines a powerful document automation tool with the wide-ranging blockchain functionalities, enabling users to digitize and monetize their IP.
+### Open source form builder, workflow designer, and document validation. 
+
+Proxeus combines a versatile document automation tool with enterprise<br> blockchain functionalities, enabling users to more easily digitize their IP.
+
+**[Getting Started](quickstart.md)**
+[Community Forum](https://github.com/ProxeusApp/community/discussions)
 
-[Getting Started](quickstart.md) 
diff --git a/docs/_navbar.md b/docs/_navbar.md
@@ -1,4 +1,4 @@
-* [Quick start](quickstart.md)
-* [Configure](configure.md)
-* [Deploy](components.md)
-* [Source Code](source_code.md)
+* [Association](about.md)
+* [Handbook](handbook.md)
+* [Quickstart](quickstart.md)
+* [Architecture](components.md)
diff --git a/docs/_sidebar.md b/docs/_sidebar.md
@@ -1,8 +1,9 @@
-- ![logo](_media/proxeus_logo.svg)
+- [![logo](_media/proxeus_logo.svg)](https://proxeus.org)
 
 - Getting started
 
     - [Quick start](quickstart.md)
+    - [User handbook](handbook.md)
 
 - Build and Run
 

diff --git a/docs/about.md b/docs/about.md
@@ -0,0 +1,223 @@
+# About the Proxeus Association
+
+The association is the governing body responsible for the maintenance and development of the Proxeus software. We also aim to encourage innovation and evangelize the project by launching and supporting community initiatives as well as creating synergies and partnerships with relevant community projects. 
+
+Governance
+----------
+
+The Association is working to give the project a decentralized structure to allow our members to propose guidance on the software. Our mission is to make the Proxeus software the 'WordPress' of the blockchain - in other words, to democratize access, and lower the costs of deployment of small blockchain applications.
+
+Some of the benefits of getting involved with the Association, is the ability to contribute both to day-to-day decisions and plans further out on the roadmap. The easiest way to do this now is to join us on [Open Collective](https://opencollective.com/proxeus).
+
+See also the [Contributing](contributing) section, and visit our [Community Forum](https://github.com/ProxeusApp/community/discussions) if you have any questions about the project - or write to us at association@proxeus.org
+
+Statutes
+--------
+
+Proxeus Association is a non-profit association governed by the present statutes and, secondly, by Articles 60 et seq. of the Swiss Civil Code. It is politically neutral, and non-denominational.
+
+OVERVIEW
+--------
+
+### Article 2
+
+-   Legal Seat: The Association's headquarters are located in Berne, Canton of Berne.
+
+-   Duration: The Association shall be of unlimited duration.
+
+GOALS
+-----
+
+### Article 3
+
+The Proxeus software is a powerful workflow engine with blockchain capabilities designed to cover a large spectrum of applications. It is made available as open source code and maintained by a community of users.
+
+-   The Association shall pursue the following goals:
+
+-   set up a governance mechanism for the Proxeus project;
+
+-   allocate resources to maintainers and developers of the Proxeus open source software; and
+
+-   foster innovation and evangelize the project by launching and supporting community initiatives, as well as by creating synergies and partnering with relevant community- driven projects.
+
+RESOURCES
+---------
+
+### Article 4
+
+The Association's resources are derived from:
+
+-   donations and legacies;
+
+-   sponsorship;
+
+-   public subsidies;
+
+-   membership fees;
+
+-   any other resources authorized by the law.
+
+-   The funds shall be used in accordance with the goals of the Association.
+
+MEMBERS
+-------
+
+### Article 5
+
+Members of the Association: Initially, the founders shall be the only members of the Association. The General Assembly may define further types of membership and how new members of the Association are accepted.
+
+Membership Fee: Initially, there shall be no membership fees for members of the Association. Later, it is up to the General Assembly to resolve on the introduction of membership fees and to determine the amount owed by the members.
+
+Termination of Membership:
+
+Membership terminates:
+
+-   By written resignation thereby notifying the Executive Board (Art. 14) at least three (3) months before the end of the financial year;
+
+-   By exclusion ordered by the Executive Board for just cause (e.g. non-payment of membership fees or damaging the interests of the Association) with no right of appeal to the General Assembly.
+
+-   Upon death / bankruptcy / liquidation of a member. In all cases of termination, the membership fee (if applicable) for the current year remains due. Members who have resigned or who are excluded have no rights to any part of the Association's assets. No financial liability of Members: Only the Association's assets may be used for obligations/commitments contracted in its name. Members have no personal liability whatsoever.
+
+ORGANS
+------
+
+### Article 6
+
+The Association shall include the following organs:
+
+-   General Assembly
+
+-   Executive Board
+
+GENERAL ASSEMBLY
+----------------
+
+### Article 7
+
+Composition: The General Assembly is the Association's supreme authority. It is composed of all members.
+
+Meetings: The General Assembly shall hold an Ordinary Meeting once each year. It may also hold Extraordinary Meetings whenever necessary, at the request of the Executive Board or at least of one-fifth of its members.
+
+Invitation to Meetings: The Executive Board shall inform the members in writing of the date and place of the General Assembly at least six (6) weeks in advance (email or announcement on the website of Proxeus is sufficient). A detailed notification (email is sufficient), including the proposed agenda, shall be sent to each member at least ten (10) days prior to the date of the meeting. Requests of members to include topics in the agenda must be submitted to the Executive Board prior to the General Assembly.
+
+No Minimal Attendance Requirement: The General Assembly shall be considered valid regardless of the number of members present.
+
+### Article 8
+
+Responsibilities of the General Assembly: The General Assembly:
+
+Appoints the members of the Executive Board and elects, at a minimum, the President, the Secretary and the Treasurer;
+
+-   Notes the contents of the reports and financial statements for the year and votes on their adoption;
+
+-   Approves the annual budget;
+
+-   Supervises the activity of other organs, which it may dismiss, stating the grounds therefore;
+
+-   Appoints an auditor for the Organization's accounts (if needed);
+
+-   Handling of any exclusion processes;
+
+-   Decides on any modification of statutes; and
+
+-   Decides on the dissolution of the Association.
+
+### Article 9
+
+President of the General Assembly: The General Assembly is presided over by the President. In absence of the President, the General Assembly is presided over by the Vice President or any other member of the Executive Board as determined by the General Assembly.
+
+Proposal of President: The President must be proposed by the Executive Board and acts as both President as well as President of the Executive Board.
+
+### Article 10
+
+Resolutions: Decisions of the General Assembly shall be taken by a majority vote of the members present. In case of deadlock, the President, or in his absence the presiding member, shall have the casting vote.
+
+Resolutions to Amend the Statutes: Decisions concerning the amendment of the Statutes and the dissolution of the Association must be approved by a two-third majority of the members present.
+
+### Article 11
+
+Voting in the General Assembly: Votes are shown by hands or by electronic means made available by the Executive Board, which do not require physical presence of the member at the General Assembly. If at least the majority of the members request it, voting may take place secretly.
+
+### Article 12
+
+Agenda of Ordinary Meeting: The agenda of the Ordinary Meeting of the General Assembly must include:
+
+-   Approval of the Minutes of the previous General Assembly;
+
+-   Approval of the Executive Board's annual Activity Report;
+
+-   Approval of the statement of the Treasurer
+
+-   Setting of membership fees (if membership fees are introduced);
+
+-   Approval of the budget;
+
+-   Approval of reports and accounts;
+
+-   Election of Executive Board members; and
+
+-   Miscellaneous business.
+
+EXECUTIVE BOARD
+---------------
+
+### Article 13
+
+Responsibilities of the Executive Board: The Executive Board is authorized to carry out all acts that further the purposes of the Association which have not been allocated to the General Assembly. It has the most extensive powers to manage the Association's day-to-day affairs.
+
+Composition of Executive Board: The Executive Board will be composed of a minimum of two (2) and a maximum of five (5) members and will be elected by the General Assembly for a one-year period. Seeking re-election is permissible. The Executive Board is self-constituted. Quorum: The Executive Board has a quorum when at least two (2) members are present. Upon motion of the President or on request of a member of the Executive Board, the Executive Board will convene.
+
+Vacancies: If an Executive Board position is vacated the Executive Board will fill the resulting vacancy. The appointment shall be approved by the General Assembly at their next meeting. Responsibility of President: The President of the Association also presides the Executive Board.
+
+### Article 14
+
+Compensation: The Executive Board members may be reasonably compensated for their work on the Executive Board with a fixed annual compensation. The General Assembly determines the compensation for the Executive Board members, if any. Expenses (actual expenses and travel costs proven by digital receipts) incurred by the Executive Board members shall be reimbursed by the Association.
+
+### Article 15
+
+Function of Executive Board: The functions of the Executive Board are:
+
+-   to take the appropriate measures to achieve the goals of the Association;
+
+-   to convene the Ordinary and Extraordinary Meetings of the General Assembly;
+
+-   to take decisions with regard to the policies for the admission of new members as well as the resignation and possible expulsion of members;
+
+-   to ensure that Statutes are applied, to draft rules of procedure, and to administer the assets of the Association.
+
+### Article 16
+
+Legal requirement to elect Auditors: The Auditors have to be elected by the General Assembly. Following the legal rules in Switzerland, the Association must have its accounting audited in the event that two of the criteria listed below are exceeded:
+
+1.  Balance sheet total of CHF 10 million
+
+2.  Turnover of CHF 20 million
+
+3.  50 full time employees on yearly average
+
+Voluntary election of Auditors: The General Assembly may, with a two-thirds majority, request the election of an auditor for a limited audit of the accounting even if the above criteria are not met. Responsibilities of Auditors: The auditor shall check the operating and annual accounts prepared by the Executive Board and present a written and detailed report to the General Assembly.
+
+VARIOUS PROVISIONS
+------------------
+
+### Article 17
+
+Financial year: The financial year shall begin on 1 January and end on 31 December of each year. The first year ends on December 31 2020.
+
+### Article 18
+
+Distribution of assets in case of dissolution: Should the Association be dissolved, all available assets should be transferred to a non-profit organization based in Switzerland pursuing public interest goals similar to those of the Association and likewise benefiting from tax exemption.
+
+The present Statutes have been approved by the General Assembly of 23 March 2020. For Proxeus Association
+
+0x77b48b1172a5E37bC46aaC270D582d36dDB92594
+
+Oleg Lavrovsky, President
+
+0xb8012Acd96f92a57207B89573507be1961D48cDA
+
+Fabian Mösli, Secretary
+
+0x88d2235B15Fb8d0217Fd46ef154766a5D5E4F086
+
+Vivien Fuhrer, Treasurer
diff --git a/docs/build_all.md b/docs/build_all.md
@@ -2,6 +2,8 @@
 
 This section describes how to build and run the platform for developers.
 
+If you intend to deploy Proxeus to a production server, please follow the [Quick start](README) guide.
+
 ### Dependencies
 
 Here is the list of dependencies:
@@ -73,26 +75,22 @@ To initialize dependencies run:
 make init
 ```
 
-To update go dependencies run:
-```
-make update
-```
-
 The make all command build the `server` and `ui`:
 ```
 make all
 ```
 
 ### Start
 
-Run `server`.
+To run the server (`artifacts/proxeus`):
+
 ```
-./artifacts/proxeus
+make run
 ```
 
-The platform will be available at the following URL: http://localhost:1323
+The platform should in a few moments be available at the following URL: http://localhost:1323
 
-It is now time to [configure your platform](configure.md)
+It is now time to [configure your platform](configure.md).
 
 ### Tips
 
@@ -104,3 +102,5 @@ Update command failing? Try:
 `go clean -cache -modcache -i -r`
 - checking your dependency graph to isolate the issue:
 `go mod graph`
+- updating Go & JS dependencies:
+`make update`
diff --git a/docs/build_docker.md b/docs/build_docker.md
@@ -67,4 +67,4 @@ There is also a Docker Compose configure in one file with a 'minimal' Proxeus in
 
 ```
 docker-compose -f docker-compose-light.yml up
-```
+```
diff --git a/docs/contributing.md b/docs/contributing.md
@@ -1,18 +1,14 @@
 # Contributing
 
-First off, thank you `<3` for your interest in Proxeus: an open source project powered by a community of users and supporters like you.
+First off, thank you `<3` for your interest in Proxeus: an open source project powered by a community of users and supporters like you. We love to receive contributions from our community! There are many ways to contribute, from writing tutorials or blog posts, improving the documentation, reporting bugs, requesting features, developing new nodes or writing core code for the Proxeus platform. 
 
-We love to receive contributions from our community! There are many ways to contribute, from writing tutorials or blog posts, improving the documentation, reporting bugs, requesting features, developing new nodes or writing core code for the Proxeus platform. Following these guidelines indicates that you respect the time of the maintainers and fellow contributors of the project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you complete your pull requests.
+Following these guidelines indicates that you respect the time of the maintainers and fellow contributors of the project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you complete your pull requests.
 
-## Your First Contribution
-
-Unsure where to begin contributing to Proxeus? You can start by looking through the open [Github Issues](https://github.com/ProxeusApp/proxeus-core/issues). Some are labelled as "good first issue" if they're especially accessible to newcomers.
-
-See the [Coding Style](coding_style.md) section for instructions on the coding style we use. Some more tips are below in the Ground Rules and Getting Started below.
+See also [About the Proxeus Association](about) for some background.
 
 ### Community Discussion
 
-We have an open community discussion forum also on GitHub at https://github.com/ProxeusApp/community/discussions - this is a great place to share your use cases, any ideas for the platform, get feedback on work that you are doing. Please note the [GitHub Community Guidlines](https://docs.github.com/en/github/site-policy/github-community-guidelines) and our own ground rules in the [Code of Conduct (Contributor Covenant)](code_of_conduct.md).
+We have an open community discussion forum also on [GitHub Discussions](https://github.com/ProxeusApp/community/discussions) - this is a great place to share your use cases, any ideas for the platform, get feedback on work that you are doing. Please note the [GitHub Community Guidlines](https://docs.github.com/en/github/site-policy/github-community-guidelines) and our own ground rules in the [Code of Conduct](code_of_conduct.md) (Contributor Covenant).
 
 ### Reporting Issues
 Please use our [GitHub Issue Tracker](https://github.com/ProxeusApp/proxeus-core/issues) to open improvement and bug tickets.
@@ -21,18 +17,22 @@ If you find a **Security Issue** - a vulnerability that may affect live or testn
 
 ## Ground Rules
 
-* Be welcoming to newcomers and encourage diverse new contributors from all backgrounds. See our [Code of Conduct (Contributor Covenant)](code_of_conduct.md) for details.
+* Be welcoming to newcomers and encourage diverse new contributors from all backgrounds. See our [Code of Conduct](code_of_conduct.md) (Contributor Covenant) for details.
 * Create issues for any major changes and enhancements that you wish to make. Discuss things transparently and get community feedback.
 * Each pull request should implement ONE feature or bugfix. If you want to add or fix more than one thing, submit more than one pull request.
-* Do not commit changes to files that are irrelevant to your feature or bugfix (eg: .gitignore).
+* Do not commit changes to files that are irrelevant to your feature or bugfix (eg: `.gitignore`).
 * Take care that code in pull requests meets our coding guidelines. Be willing to accept criticism and work on improving your code; care must be taken not to introduce bugs.
 * Git commits are much more valued when they follow the git commit messages guide.
 * Be aware that the pull request review process is not immediate, and is generally proportional to the size of the pull request.
 * If your pull request is merged, please do not ask for an immediate release of a new version. There are many factors contributing to when releases occur. If necessary, please install from the GitLab source until the next official release.
 
-## Getting started
+## Making your first Contribution
+
+Unsure where to begin contributing to Proxeus? You can start by looking through the open [Github Issues](https://github.com/ProxeusApp/proxeus-core/issues). Some are labelled as "good first issue" if they're especially accessible to newcomers.
+
+See the [Coding Style](coding_style.md) section for instructions on the coding style we use. Some more tips are below in the Ground Rules and Getting Started below.
 
-1. Work on your own fork of the code rather than on a cloned repository. In order to fork a Github project go to https://github.com/ProxeusApp/proxeus-core then click on "Fork" and choose a suitable GitHub account for the fork —eg. your personal Github account. You only need to fork once per repository.
+1. Work on your own fork of the code rather than on a cloned repository. In order to fork a Github project go to [ProxeusApp/proxeus-core](https://github.com/ProxeusApp/proxeus-core) then click on "Fork" and choose a suitable GitHub account for the fork —eg. your personal Github account. You only need to fork once per repository.
 2. Announce you are on an issue. If you are trying to solve a reported issue, comment that you intend to solve it, and possibly discuss with the community and maintainers the best approach before starting to code.
 3. Create a new branch in your fork (be sure it is synchronized with the original project repository!) and name it after the issue from step #2. Code on that branch and commit your changes (it’s always good to add/fix tests).
 4. Open a pull request after having pushed your changes. Please, be sure to follow this git commit messages guide.