chore(#126): footer component should not predefine content within sec…

[BrianGilbert]

…tions

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes (if not applicable, please state why)
• All new and existing tests are passing.

Screenshots/Media:

Summary by CodeRabbit

• New Features
  • Introduced dynamic content support in the footer section of the app.
• Refactor
  • Replaced static content in the footer with slot elements for more flexibility.

[coderabbitai]

Walkthrough

The changes primarily focus on the refactoring of the Footer component in Vue.js. The modifications involve the introduction of new conditional templates in the Footer.stories.js file and the replacement of static content with slot elements in the Footer.vue file, allowing for more dynamic content injection.

Changes

File Path	Change Summary
src/components/Footer.stories.js	Added conditional templates for content_bottom1 and content_bottom2, and removed the template for copyright.
src/components/Footer.vue	Replaced static content in ct-footer__bottom__content-bottom1 and ct-footer__bottom__content-bottom2 divs with slot elements for dynamic content injection.

Poem

🐇 Hopping through the autumn leaves, 🍂

Code changes we weave, not by thieves.

On this day, in history's sway,

The Berlin Wall began to fall away. 🏰

In our code, a similar stride,

Old barriers removed, with pride.

With slots and templates, our code now dances, 💃

Celebrating change, and all its chances. 🎉

So here's to autumn, and code that's free,

From this little rabbit, with glee. 🐇🎈

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• If you reply to a review comment from CodeRabbit, the bot will automatically respond.
• To engage with CodeRabbit bot directly around the specific lines of code in the PR, mention @coderabbitai in your review comment
• Note: Review comments are made on code diffs or files, not on the PR overview.
• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai help to get help.
• @coderabbitai resolve to resolve all the CodeRabbit review comments.

Note: For conversation with the bot, please use the review comments on code diffs or files.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 22bd5f9 and e0f9d22.

Files selected for processing (2)

• src/components/Footer.stories.js (1 hunks)
• src/components/Footer.vue (1 hunks)

Files skipped from review due to trivial changes (1)

• src/components/Footer.vue

Additional comments: 1

src/components/Footer.stories.js (1)

• 26-30: The changes look good. The new templates for content_bottom1 and content_bottom2 will allow for more flexibility in the content that can be inserted into these sections of the footer.