Skip to content

feat(fellowship): mark 2026 applications as closed - #53

Closed
miantalha45 wants to merge 3 commits into
mainfrom
fellowship-applications-closed
Closed

miantalha45 wants to merge 3 commits into
mainfrom
fellowship-applications-closed

Conversation

@miantalha45

Copy link
Copy Markdown
Collaborator

Description

Updates the Fellowship 2026 page to clearly communicate that applications are closed and removes access to the application form.

Related Issue

Fixes #

Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📝 Documentation update
  • 🎨 Style/UI update
  • ♻️ Code refactor (no functional changes)
  • ⚡ Performance improvement
  • 🔧 Configuration change
  • 🧪 Test update

Changes Made

  • Changed Fellowship 2026 messaging from “Applications Open” to “Applications Closed.”
  • Replaced application CTAs with links to the “What Comes Next” fellowship update.
  • Disabled track-selection application buttons and removed the Google Form action.

Screenshots / Videos

Before After
Applications presented as open Applications clearly presented as closed

Testing

Test Environment

  • OS: macOS
  • Browser: tested
  • Node.js Version: Not recorded

Test Steps

  1. Verified no “Applications Open” or fellowship application CTA remains on the Fellowship page.
  2. Verified informational CTAs route to /blog/fellowship-2026-next-steps.
  3. Ran git diff --check successfully.

Code Quality

  • My code follows the project's coding style and conventions
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings or errors

Testing

  • I have tested my changes locally
  • Existing tests pass with my changes
  • I have added tests for new functionality (if applicable)

Documentation

  • I have updated the documentation accordingly (if applicable)
  • I have updated the README if needed

Build & Lint

  • npm run build completes successfully
  • npm run lint passes without errors

Security

  • No sensitive data (API keys, passwords, etc.) is committed
  • Security implications have been considered

Additional Notes

A repository-wide TypeScript check currently reports pre-existing errors in unrelated admin, API, and UI files. No errors were reported from the Fellowship page changes.

Signed-off-by: Talha Amjad <myown4500@gmail.com>
junaiddshaukat
junaiddshaukat previously approved these changes Sep 23, 2026

@junaiddshaukat junaiddshaukat left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@junaiddshaukat

Copy link
Copy Markdown
Member

@copilot resolve the merge conflicts on this branch.

…ns-closed

# Conflicts:
#	components/headline-bar.tsx

Co-authored-by: junaiddshaukat <154750865+junaiddshaukat@users.noreply.github.com>

Copilot AI commented Sep 23, 2026

Copy link
Copy Markdown

@copilot resolve the merge conflicts on this branch.

Resolved by merging main into this branch and fixing the conflict in components/headline-bar.tsx in commit b92ccd0.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants