-
Notifications
You must be signed in to change notification settings - Fork 24
Certifications web copy updates #2909
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
6044ceb to
9acc43b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates web copy across HashiCorp certification pages to improve clarity, consistency, and user experience. The changes include simplified descriptions, reorganized content, and standardized formatting based on a content review document.
- Simplified certification program descriptions with more concise, user-focused language
- Updated exam FAQ content with clearer eligibility requirements and recertification pathways
- Standardized heading capitalization and table formatting across exam documentation
Reviewed Changes
Copilot reviewed 10 out of 10 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| src/content/certifications/landing.json | Updated hero description for clarity and conciseness |
| src/content/certifications/landing-faq.mdx | Simplified exam experience and recertification explanations |
| src/content/certifications/programs/infrastructure-automation.json | Updated program summaries and exam descriptions with clearer, more concise language |
| src/content/certifications/programs/security-automation.json | Updated program summaries and exam descriptions with clearer, more concise language |
| src/content/certifications/exam-faqs/vault-associate-003.mdx | Restructured prerequisites section, updated recertification tables, and standardized headings |
| src/content/certifications/exam-faqs/vault-operations-professional.mdx | Restructured prerequisites section, updated recertification tables, and standardized headings |
| src/content/certifications/exam-faqs/terraform-associate-003.mdx | Updated exam availability info, restructured prerequisites, and added recertification tables |
| src/content/certifications/exam-faqs/terraform-associate-004.mdx | Updated exam availability info, restructured prerequisites section, and standardized headings |
| src/content/certifications/exam-faqs/terraform-authoring-operations-professional.mdx | Restructured prerequisites section, updated recertification tables, and standardized headings |
| src/content/certifications/exam-faqs/consul-associate-003.mdx | Restructured prerequisites section, updated recertification tables, and standardized headings |
π‘ Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
src/content/certifications/exam-faqs/terraform-authoring-operations-professional.mdx
Show resolved
Hide resolved
π¦ Next.js Bundle AnalysisThis analysis was generated by the next.js bundle analysis action π€ This PR introduced no changes to the javascript bundle π |
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
β¦tions-professional.mdx Co-authored-by: Copilot <[email protected]>
β¦v-portal into BE/certs/web/revamp
Changed tables to list for exam version diffs; mocked up two wording options for recert; nits
π Relevant links
ποΈ What
This PR includes all changes from the copy doc linked above.
One change not yet done is the standardizing of content differences between exams. Working with Ashley on that and will update.
π€· Why
π οΈ How
πΈ Design Screenshots
π§ͺ Testing
π Anything else?
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.