docs(portal): staff button and Management Templates layout parity

This commit is contained in:
AIAMarketing authored and Jeff Hales committed 2026-11-01 14:05:35 -07:00
1 parent 3e05458944
commit b0cf2d7119
1 file changed
+19
@@ -111,6 +111,25 @@ existing orange resource-button style; arbitrary anchors remain ordinary links.
Both unlocked views now use the site's orange accent for list-item markers.
The source classes and styles still do not reach the passive DOM.
### Staff resources and Management Templates, 2026-11-01
The owner observed that the non-management (general-staff) portal still lost
HubSpot's resource-button presentation. After **sanitizing** the decrypted DOM,
a headed `Management Templates` section identifies the general-staff resource
view. Valid HTTP(S) resource links in that view receive only the local
`portal-resource-button` class; `mailto:` and `tel:` retain contact-link
styling. Neither destination validation nor removed legacy classes/styles,
scripts, media or HTML attributes are relaxed.
The `Management Templates` unordered list receives a local
`portal-template-grid` class: two columns at desktop widths (768px+),
one column on smaller screens. Semantic list order and keyboard tab order
are retained, with responsive full-width buttons. This is a presentation
change only: it does not infer or approve employee resource access.
Synthetic staff/management browser fixtures check the distinction and
responsive columns. The actual decrypted staff source remains private;
owner should confirm layout and links in the local preview before merging.
Scoped typography, spacing, lists, table rules and keyboard focus apply to both
unlocked streams. Synthetic staff/management fixtures exercise these mappings
at 320/390/768/1440px. Owner must inspect the real views privately to confirm