commit 15292dec70b85550beb085ebeea937119e3ada13
parent 1eca63992afa931754789fc0e0d23e85eaedb254
Author: Florian Dold <florian@dold.me>
Date: Mon, 17 Nov 2025 16:36:14 +0100
update DD74
Diffstat:
1 file changed, 23 insertions(+), 2 deletions(-)
diff --git a/design-documents/074-merchant-backend-simplification.rst b/design-documents/074-merchant-backend-simplification.rst
@@ -68,7 +68,8 @@ Personas
^^^^^^^^
* Personas are a preset of feature flags and other settings
-* The user selects a persona when logging in (from a drop-down).
+* The backend provides a default persona. After login, the UI for
+ this persona is chosen. It can be changed in the "Personalization" menu.
* We do not call it "profiles", because it clashes with the "profile" terminology
as it is typically used in UIs (contact info, profile picture, ...).
@@ -190,6 +191,16 @@ Proposed Solution (Iteration 2)
be implemented once iteration 2 is done.
+Simplification of Resource Identifiers
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Currently, the user has to choose the resource identifier for templates,
+products, and so on. It's not clear to the typical user *why* they have to
+choose this, so we should provide a reasonable default for the resource ID.
+
+https://bugs.gnunet.org/view.php?id=10620
+
+
Simplication of Bank Account Settings
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -296,7 +307,17 @@ Discussion / Q&A
* Yes, under ``Personalization``, just like the language and date format.
+* Can the user choose a person at login or instance creation?
+
+ * No, we want to avoid too many input fields / choices.
+
+* Is the chosen persona persistent?
+
+ * Not for now, it's stored per session. We could make it persistent
+ in the future, but there are no plans for that presently.
+
* Should developer mode be a separate persona, or should there always be a developer mode toggle
for every persona?
-
+ * Problem with "developer as persona": The developer mode already affects the behavior
+ *before* login, such as when choosing a different backend base URL.
