Broken Footer Link Points to Incorrect URL

[Sfayson1]

Feature Name 🎯

Fix Footer "Modules" Link

The Big Picture 🖼️

What's the Problem?

The "Modules" link in the footer of the Vets Who Code website currently points to an incorrect URL (vetswhocode.io/curriculum/subjects). This misdirection can confuse users and disrupt their navigation experience.

What's Our Goal?

Ensure the "Modules" link in the footer redirects users to the correct URL: vetswhocode.io/courses/all. This change will enhance user experience by providing accurate and functional navigation.

How Will We Know It's Working?

• Clicking the "Modules" link in the footer takes users to the intended page.
• User feedback about navigation issues is reduced.
• Analytics show consistent visits to the correct URL when users interact with the "Modules" link.

Who's Involved? 👥

Team Members

• Project Lead: [Name]
• Mentor: [Name]
• Fellow Veterans: [Names]

Who Needs to Approve?

• Mentor
• Project Lead
• Team Vote

What We're Building 🛠️

This Feature Will:

• Update the "Modules" link in the website footer to point to vetswhocode.io/courses/all.

This Feature Won't:

• Add new links or change other footer content.
• Modify the design or structure of the footer.

User Stories 📖

• As a user, I want the "Modules" link to take me to the correct page, so that I can easily access all available courses.

Design Sketches 🎨

(Not applicable for this feature as it’s a functional update, not a design change.)

Technical Details 💻

Tools We'll Use

• HTML: For editing the footer content.
• JavaScript/React: If the footer is dynamically generated or part of a component.

Data/Storage

• No data storage changes needed.

Connections

• APIs needed? None.
• Feature dependencies? Existing footer structure and links.
• External services? None.

Possible Challenges 🚧

What Could Go Wrong?

• Incorrect implementation may point the link to another unintended URL.
• Caching issues may cause delayed updates for users.

How We'll Handle It

• Double-check the updated URL before deployment.
• Clear cache and verify on multiple devices after deployment.

Testing Plan ✅

What We'll Test

• Ensure the updated link redirects correctly.
• Test on various devices and browsers to confirm functionality.

How We'll Test

• Manual testing by the development team.
• Cross-browser and cross-device compatibility checks.

Launch Plan 🚀

How We'll Release It

1. Update the footer link in the codebase.
2. Push changes to the staging environment for testing.
3. Deploy the fix to production during low-traffic hours.

How We'll Track Success

• Monitor website analytics to confirm users reach the correct page.
• Collect feedback from users if issues arise.

Who Owns It? 👤

• Maintainer: [Name]
• Contact for issues: [Email/Slack]
• Documentation location: [Link to repo/wiki]

Timeline 📅

• Design Review: [Not applicable]
• Start Coding: [Date]
• Testing: [Date]
• Launch: [Date]

Ready to Start? ✍️

• Feature Owner: _____________ Date: _____
• Mentor: __________________ Date: _____
• Team Lead: _______________ Date: _____

Notes 📝

• Verify that the link update does not break other footer functionality.
• Document the change for future reference.

[Sfayson1]

@jeromehardaway updated issue to reflect design doc format.