Skip to content

DOCS-1842 - Add persona-based learning paths to training FAQ - #7085

Open
mafsumo wants to merge 7 commits into
mainfrom
DOCS-1842
Open

DOCS-1842 - Add persona-based learning paths to training FAQ#7085
mafsumo wants to merge 7 commits into
mainfrom
DOCS-1842

Conversation

@mafsumo

@mafsumo mafsumo commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

Purpose of this pull request

This pull request adds a "Role-based learning paths" section to the Training and Certifications FAQ, covering the 8 new persona-driven learning paths (Security: SOC/Security Analyst, Cloud Security Architect, SOC Administrator; Observability: DevOps/IT Contributor, Log Analyst/SRE, IT Ops Leader, System Administrator, DevOps Leader). Each path links to its guided path in the Learning Portal and a downloadable PDF handout, so Digital CS and PS outreach can point customers to a specific role-based path instead of a generic course list.

Select the type of change

  • Minor Changes - Typos, formatting, slight revisions
  • Update Content - Revisions, updating sections
  • New Content - New features, sections, pages, tutorials
  • Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

https://sumologic.atlassian.net/browse/DOCS-1842

Adds a role-based learning paths section to the Training and Certifications
FAQ so Digital CS and PS outreach can point customers to a specific persona
path instead of a generic course list. Each of the 8 paths links to its
guided Learning Portal path and a downloadable PDF handout.
@mafsumo mafsumo self-assigned this Sep 1, 2026
@cla-bot cla-bot Bot added the cla-signed Contributor approved, listed in .clabot file label Sep 1, 2026
@mafsumo mafsumo added the do-not-merge Pull requests that should not be merged label Sep 1, 2026
Comment thread docs/get-started/training-certification-faq.md Outdated
Comment thread docs/get-started/training-certification-faq.md Outdated
@kimsauce

kimsauce commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

In light mode, two button styles are too close in weight. "Start path" (filled grey) and "Download PDF" (outline) read as almost the same emphasis, so the visual distinction does no work. "Start path" is the primary action per row — let it carry a bit more weight (e.g. keep it as button--secondary, and drop "Download PDF" to a plain text link with a download icon, or button--link). That also de-clutters the table.

@kimsauce

kimsauce commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

Repeated link text ("Start path" / "Download PDF" ×8) gives screen-reader users no context. Add aria-label="Start the SOC/Security Analyst path" etc.

kimsauce and others added 4 commits September 2, 2026 08:57
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com>
Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com>
kimsauce and others added 2 commits September 2, 2026 12:26
Downgrades "Download PDF" from an outline button to Infima's plain
button--link style so "Start path" reads as the clear primary action per
row, and adds role-specific aria-labels to all 16 links so screen readers
get context instead of repeated "Start path"/"Download PDF" text.
@mafsumo

mafsumo commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator Author

Thanks for the feedback, Kim. Both items are addressed: "Start path" keeps its filled secondary button as the primary action, and "Download PDF" now uses Infima's plain button--link style so the two read as distinct again. I also added a role-specific aria-label to every link, start and download, so screen readers get the role name instead of hearing "Start path" or "Download PDF" sixteen times.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed Contributor approved, listed in .clabot file do-not-merge Pull requests that should not be merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants