refactor: landing page

[anniexwang]

Overview

(Brief overview (a few sentences) of what this PR achieves.)

• Added navbar with similar UI design as cave learn
• Redesigned HomeButtonCard to match cave learn UI

Proposed Changes

(Describe your changes here. Also describe the motivation for your changes: what problem do they solve, or how do they improve the application or codebase? If this pull request fixes an open issue, use a keyword to link this pull request to the issue.)

...

Screenshots of your changes (if applicable)

How to Test & Review

(Help your reviewer by providing clear instructions on how to verify your changes. Include specific commands, edge cases to watch out for, or UI navigation paths.)

1. Confirm that the navbar works
2. Confirm that the buttons still lead to the right page

Type of Change

(Write an X or a brief description next to the type or types that best describe your changes.)

Type	Applies?
🚨 Breaking change (fix or feature that would cause existing functionality to change)
✨ New feature (non-breaking change that adds functionality)
🐛 Bug fix (non-breaking change that fixes an issue)
🎨 User interface change (change to user interface; provide screenshots)
♻️ Refactoring (internal change to codebase, without changing functionality)	x
🚦 Test update (change that only adds or modifies tests)
📚 Documentation update (change that only updates documentation)
📦 Dependency update (change that updates a dependency)
🔧 Internal (change that only affects developers or continuous integration)

Checklist

(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)

Before opening your pull request:

• I have performed a self-review of my changes.

  • Check that all changed files included in this pull request are intentional changes.
  • Check that all changes are relevant to the purpose of this pull request, as described above.

• I have added tests for my changes, if applicable.

  • This is required for all bug fixes and new features.

• I have updated the project documentation, if applicable.

  • This is required for new features.

• (Frontend) I have added/updated text in i18n JSON files for any new user-facing strings to support multilingual features.
  After opening your pull request:

• I have verified that the CI tests have passed.

• I have requested a review from a project maintainer, and a fellow student.

• Technical Debt: If temporary workarounds or "TODOs" were used, I have opened a tracking issue to address them properly.

  • Linked Issues:

Questions and Comments

(Include any questions or comments you have regarding your changes.)

[masa-2a]

Are you still working on this?

[anniexwang]

Are you still working on this?

Yup, just resolved the new merge conflicts

[matt-dahlgren]

Great work Annie!