Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 Description
This PR creates the new SASE Projects page to be featured under the Programs section of the website. The original code was done by Rishab during sprint-3.
Still need to add a link to it in the general Programs page, but will need image and description.
🔗 Related Issue(s)
If this PR fixes or relates to an open issue, reference it here:
Fixes #468
🧪 How to Test
Include clear steps so reviewers can verify your changes.
Example:
bun installandbun dev/projects📸 Screenshots (if applicable)
If your change affects the UI, attach before and after screenshots.
✅ Checklist
Please confirm all the following before requesting review:
bun fixand fixed all warnings/errorsAdditional Notes (Optional)
Add anything else the reviewers should know.
(e.g., follow-up tasks, known issues, blockers, or special setup notes)