Operator (RC1 manual test)
"We should better organize the JSON and the grouping of toggles, they seem random and not well organized by what they do." #1887 is one instance (Tari under the Monero group); this is the whole view.
What should happen
A pass over LOGICAL_GROUPS in configlogic.mjs and the order of config.reference.json: groups by what a person is trying to do (Mining · Payouts · Nodes: Monero / Tari · Workers · Dashboard & access · Notifications · Energy · Alerts · Advanced), the same order in the JSON, related toggles adjacent, and each group with a one-line description. The design review (#1875) owns the visual side; this issue is the information architecture. Do it once #1855 (Tari opt-in) lands so the Tari-off state is designed in.
Tier 1: configlogic test that every reference key classifies into a named group and none lands in "Other"; docs: the configuration doc's key table follows the same order.
Operator (RC1 manual test)
"We should better organize the JSON and the grouping of toggles, they seem random and not well organized by what they do." #1887 is one instance (Tari under the Monero group); this is the whole view.
What should happen
A pass over
LOGICAL_GROUPSinconfiglogic.mjsand the order ofconfig.reference.json: groups by what a person is trying to do (Mining · Payouts · Nodes: Monero / Tari · Workers · Dashboard & access · Notifications · Energy · Alerts · Advanced), the same order in the JSON, related toggles adjacent, and each group with a one-line description. The design review (#1875) owns the visual side; this issue is the information architecture. Do it once #1855 (Tari opt-in) lands so the Tari-off state is designed in.Tier 1:
configlogictest that every reference key classifies into a named group and none lands in "Other"; docs: the configuration doc's key table follows the same order.