🔴 Build a more useful, easy to integrate version of DevKit

[milstan]

Description

This is the TOP PRIORITY issue in the Product line of work in Q4 2022. The Document and Onboard part is the TOP PRIORITY in the DevRel line of work in Q4 2022.

Intended outcome

In Q3 we built the first version of DevKit with a working (and impressive) demo. The goal for Q4 is to grow this version towards a more complete feature set (among the scope of our technical specs) that maximises:

• usefulness for clients in their real-life situations/scenarios
• ease of integration (the effort of integration justifies the usefulness - gain of time/money that the product offers)

Sub-tasks

Build

• [ ] Authentication: Enable Data Subject during the process of request processing, and envale System/Components authentication when communicating around requests
• [ ] #989
• [ ] #988
• [ ] #987
• [ ] PCE works with Retention policies, and can load/offload Regulations
• [ ] #1006
• [ ] #1009
• [ ] #1014
• [ ] #913

These subgoals are further specified in concrete issues in corresponding component repositories.

Document and Onboard

• [ ] 1. #962
• [ ] 2. #963
• [ ] 3. https://github.com/blindnet-io/devrel-management/issues/96 — added by @Vuk-BN on Oct. 10
• [ ] +. #964

These subgoals are to be further specified.

[nweldev]

From @Vuk-BN on Oct. 10 by email

« Please channel your efforts towards the tasks below, in the following order:

1. Documentation for the DevKit - further contribute and develop the available documentation to reflect all components in production and development of the DevKit 2. Tutorials for the Devkit - create a new and functioning demo app (e.g. CV-collector app for our recruitment process) with a tutorial that describes each development step 3. Github discussion board - develop an initial github discussion board with no less than 5 discussions or topics that an average developer might have when it comes to the integration of the DevKit »

I updated the associated section (Document and Onboard) accordingly.