fix: redirect subject landing pages to chapter 0#190
Open
Official-Prasad wants to merge 1 commit into
Open
Conversation
Contributor
|
@Official-Prasad is attempting to deploy a commit to the PushkarScripts Team on Vercel. A member of the Team first needs to authorize it. |
Author
|
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
1 participant
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.
Related Issue
Fixes #185
Description
All subject landing pages (e.g.
/sem1/c,/sem2/oops,/sem4/os) were showing a generic placeholder —"Welcome to the Tutorial / Select a chapter from the sidebar"— instead of actual content. The comment in each file even incorrectly said// app/page.tsx, confirming it was a copy-paste leftover from a template.This PR replaces all 10 placeholder
page.tsxfiles with a proper Next.jsredirect()to each subject's first chapter (ch0), so users land directly on real content.Type of Change
Screenshots / Demo
Before: Visiting
/sem1/cshowed an unstyled placeholder with no navbar or styling.After: Visiting
/sem1/cinstantly redirects to/sem1/c/ch0with full content.How Has This Been Tested?
Ran
npm run devlocally and visited each affected route (/sem1/c,/sem1/em1,/sem1/ep,/sem2/dsc,/sem2/em2,/sem2/oops,/sem3/coa,/sem4/dbms,/sem4/dops,/sem4/os). All redirected correctly to their respectivech0pages.Checklist
AI Usage
If AI tools were used, briefly explain how:
Used Claude to identify the bug, generate the fixed redirect files, and assist with the PR workflow.
Additional Notes
Files changed:
app/sem1/c/page.tsx,app/sem1/em1/page.tsx,app/sem1/ep/page.tsx,app/sem2/dsc/page.tsx,app/sem2/em2/page.tsx,app/sem2/oops/page.tsx,app/sem3/coa/page.tsx,app/sem4/dbms/page.tsx,app/sem4/dops/page.tsx,app/sem4/os/page.tsx