Create a user success table

Created on 9 October 2024, 6 months ago

Problem/Motivation

At the moment there is no clear plan yet either in terms of the functional scope or how exact the user interface for the dppca module should look like. Lets sketch an outline and a vision going forward within this issue.

Steps to reproduce

Proposed resolution

I would propose creating a user success table. It contains the list of users who are using the module, what their intent using is, how it looks like if they are successfully using the module and what is the required list of actions to achieve their goal. We can discuss the details in the comments and as soon as we agreed on the user stories we can populate the table in the issue summary:

Remaining tasks

User interface changes

API changes

Data model changes

🌱 Plan
Status

Active

Version

1.0

Component

User interface

Created by

🇩🇪Germany rkoller Nürnberg, Germany

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

Sign in to follow issues

Comments & Activities

  • Issue created by @rkoller
  • 🇩🇪Germany rkoller Nürnberg, Germany

    in regards of the user i see at least two potential groups of users. first the main group admins/sitebuilders/site owners and then maybe attorneys and legal consultants? is there another type of user to consider?

  • 🇨🇭Switzerland boromino

    That's a very good idea and I support the 2 user groups to consider.

    Keeping in mind that "whether a website owner wants to comply with regulations and/or respect the privacy of their users is entirely their decision, not ours" and that "we are not lawyers and do NOT provide legal advice", the user interface should state clearly, that it's the website owner's responsibility to make sure its site complies with the applicable regulations. We also should avoid any pattern in the UI that may imply that regulations are legally met. The latter may, however, go into the "API for law firms" and then be integrated into the UI.

    As already discussed in the last meeting, the different sections of technical implementations (e.g. Consent Management, Data protection, etc.), that may affect privacy, should only appear once and not be repeated for each regulation (e.g. GDPR, CCPA). The latter could either be displayed separately or along with the previously mentioned sections.

    Legal staff usually knows the law but may lack knowledge about technical implementations. E.g. they may not know how to check what/if cookies are set or the privacy issues with embedded third party assets/content. On the other hand, website owners may have common knowledge about regulations. Thus, the UI should provide some basic but clear information about legal consequences of technical implementations for each above mentioned section.

  • 🇩🇪Germany rkoller Nürnberg, Germany

    went ahead and wrote up a few intents for the admin and lawyer groups (called the two just admin and lawyer for brevity sake). Any feedback and suggestions modifying those intents is welcome same as if anyone could think of a few more intents. as soon as we've reached an agreement the success scenarios can be ideated and in the last step the necessary series of actions for each of the scenarios. and i've added the "user" dppca as well as a suggestion. intents for dppca dont describe a user need but the needs of the module under the hood. the intent i've added is in a vein with the example of the capabilities api in joomla where modules/plugins provide relevant information about privacy.

  • 🇩🇪Germany rkoller Nürnberg, Germany
  • 🇩🇪Germany rkoller Nürnberg, Germany

    hmmm and seeing the actual output after a bit of content was entered, i am not sure if an issue is the best place to iterate on that table. :/

  • 🇩🇪Germany rkoller Nürnberg, Germany

    Moved the table over to a google sheet and set that everyone with the link is able to edit: https://docs.google.com/spreadsheets/d/1OiEBxbCsTsLZQBklzQFSOK493Un8N0No...

Production build 0.71.5 2024