nhcarrigan/docs
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 2 Pull Requests 6 Actions Releases 1 Activity

docs(mentorship): add programme sunset callout to all pages #32

Merged
naomi merged 1 commits from feat/mentorship into main 2026-05-26 11:20:56 -07:00
Conversation 0 Commits 1 Files Changed 21
+168
hikari commented 2026-05-26 09:22:22 -07:00
Owner
Copy Link
Copy Source

Summary

The open Mentorship Programme is being closed. This PR adds a :::caution[Programme Sunset] aside to the top of every page under src/content/docs/mentorship/ (and the nested resources/ subdirectory) so anyone landing on these pages immediately understands the current state of the programme.

The callout:

  • States that the open programme has been sunset and is no longer accepting new participants
  • Notes that the pages remain available as reference material
  • Describes the new private, invite-only personalised development programme
  • Clarifies that there is no application process
  • Directs interested readers to the Discord community as the route to being noticed for an invite

Files changed

  • 11 main mentorship pages (00-faq through 10-graduation)
  • 10 resource pages under mentorship/resources/
  • 21 files total, 168 insertions, 0 deletions

Test plan

  • pnpm lint passes (0 cspell issues across 176 files)
  • pnpm build succeeds (177 pages built, no Starlight aside errors)
  • Spot-checked rendered placement on 00-faq.md and resources/career-prep.md
  • Visual confirmation in deployed preview

Notes

While working on this, I noticed one pre-existing em-dash in mentorship/07-writing-code.md (line 184, in the body content, not the callout). Out of scope for this PR but worth a future cleanup pass to bring those legacy docs in line with your tone guide.

## Summary The open Mentorship Programme is being closed. This PR adds a `:::caution[Programme Sunset]` aside to the top of every page under `src/content/docs/mentorship/` (and the nested `resources/` subdirectory) so anyone landing on these pages immediately understands the current state of the programme. The callout: - States that the open programme has been sunset and is no longer accepting new participants - Notes that the pages remain available as reference material - Describes the new private, invite-only personalised development programme - Clarifies that there is no application process - Directs interested readers to the Discord community as the route to being noticed for an invite ## Files changed - 11 main mentorship pages (`00-faq` through `10-graduation`) - 10 resource pages under `mentorship/resources/` - 21 files total, 168 insertions, 0 deletions ## Test plan - [x] `pnpm lint` passes (0 cspell issues across 176 files) - [x] `pnpm build` succeeds (177 pages built, no Starlight aside errors) - [x] Spot-checked rendered placement on `00-faq.md` and `resources/career-prep.md` - [ ] Visual confirmation in deployed preview ## Notes While working on this, I noticed one pre-existing em-dash in `mentorship/07-writing-code.md` (line 184, in the body content, not the callout). Out of scope for this PR but worth a future cleanup pass to bring those legacy docs in line with your tone guide.
hikari added 1 commit 2026-05-26 09:22:23 -07:00
docs(mentorship): add programme sunset callout to all pages
Node.js CI / CI (pull_request) Successful in 56s
Details
Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 1m21s
Details
175595a26d 
The open Mentorship Programme is being closed. A caution-style aside is
now displayed at the top of every mentorship page (including the nested
resource pages) explaining the sunset, describing the new invite-only
personalised development programme, and pointing readers to the Discord
community as the route to being noticed for an invite.
naomi merged commit c8f7f701b4 into main 2026-05-26 11:20:56 -07:00
naomi deleted branch feat/mentorship 2026-05-26 11:20:56 -07:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/docs#32
Delete Branch "feat/mentorship"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?