fix(layout): make footer copyright year dynamic

[hyddeos]

Description

• Closes #
• What does this PR change? Give us a brief description.
  Sets the current year automatically in the Footer

[coderabbitai]

📝 Walkthrough

Walkthrough

The Footer component in Layout.astro was updated to display the current year dynamically using a template literal instead of a hardcoded static year value, with all other footer structure preserved.

Changes

Cohort / File(s)	Summary
Footer Year Update www/src/layouts/Layout.astro	Replaced static year in Footer component with dynamic current year via template literal.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A year that changes, not stays the same,
With template magic, time's a game,
The Footer now keeps perfect pace,
Showing current years with digital grace! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix(layout): make footer copyright year dynamic' directly matches the primary change in the PR, which updates the Footer component to use the current year dynamically instead of a static year.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.}

[studiocms-no-reply]

Hello @hyddeos, and thank you for opening your first pull request to StudioCMS! 🎉
Please make sure to review the project's Contributing Guide to ensure your pull request meets our quality standards.
We're excited to have you here and appreciate your contribution. If you have not already, please make sure to include the following information in your pull request: - A clear description of the changes - Steps to reproduce the issue (if applicable) - Any relevant screenshots or logs
Our team will review your pull request as soon as possible. If you have any questions or need help, feel free to ask. We're here to help you! 🚀
In the meantime, you will notice that a few checks will run on your pull request. These checks are automated and help us ensure that your changes meet our quality standards. If you see any errors or warnings, don't worry! Our team will help you address them. 😊

[Adammatthiesen]

Got to love the simple and easy fixes!

[studiocms-no-reply]

Congrats and Welcome @hyddeos to the Contributor Squad! 🎉
If you haven't already, please join our Discord community to stay in the loop for any future help we may need!

• The StudioCMS Team