Feature/new home page

[Mahimahto]

Summary

This pull request addresses issue #873 by adding a new dummy route
/new-home in the Gatsby project. The page currently shows placeholder
text and will be used for the upcoming homepage redesign. The existing
homepage (/) has not been modified.

Issue

Closes #873

Description

• Created src/pages/new-home.js
• Added placeholder content
• Ensured there is no change to the existing homepage

Summary by CodeRabbit

• New Features
  • Added a new page with introductory content and heading to the application.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[maanasb01]

Hi @Mahimahto, it seems you have not synced up your branch before making changes for this issue. This PR contains old commits for Uli-Community as well. Can you sync your branch with the tattle's main branch and then only keep the relevant changes?

[Mahimahto]

Hi @maanasb01 , I did sync with the main branch and created a separate branch before making the changes. That said, I see that some older commits are still showing up in the PR. I’ll fix this by syncing again and updating the PR with only the required commits.

[maanasb01]

Yeah sure, I see your main branch is up to date with the Tattle's. So it could be that you might have created this PR's feature branch from some other old branch in your local repository.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new React component file is created at uli-website/src/pages/new-home.js containing a NewHome functional component that renders a main element with padding, a heading "New Home", and placeholder text content.

Changes

Cohort / File(s)	Summary
New Home Page Component uli-website/src/pages/new-home.js	Creates a new functional component NewHome with JSX returning a <main> element containing an <h1> heading and <p> placeholder text; exported as default export

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A freshly sprouted page takes root,
With "New Home" signs and placeholder boots,
The design will bloom where this seed now sits,
No overwriting—just blank canvas bits!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Feature/new home page' clearly relates to the main change—adding a new home page component—and is concise and specific.
Description check	✅ Passed	The PR description is mostly complete with summary, issue reference, and description of changes, though it does not fully match the provided template which asks for steps to test and expected behavior.
Linked Issues check	✅ Passed	The code changes successfully implement the requirements from issue #873: creating a new dummy route at /new-home with placeholder content without modifying the existing homepage.
Out of Scope Changes check	✅ Passed	The PR contains only the necessary change—adding new-home.js—which is directly in scope with the linked issue requirements; no out-of-scope modifications detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}