refactor: inline footer sub-components into FooterWebsite

[Cristiano2009Manu]

Contributor checklist

• This pull request is on a separate branch and not the main branch

---

Description

This PR inlines the contents of the footer sub-components FooterFlex.vue and FooterFlexCol.vue directly into FooterWebsite.vue, following the same refactor pattern as activist-org/activist#1914.

Files changed:

• Updated FooterWebsite.vue to include both mobile and desktop footer layouts inline
• Deleted FooterFlex.vue (sub-component no longer needed)
• Deleted FooterFlexCol.vue (sub-component no longer needed)
• Removed footerTypes.ts (no longer needed without sub-components)
  Testing: Verified locally that the footer renders correctly on both mobile and desktop layouts.

Testing:
Verified locally that the footer renders correctly on both mobile and desktop layouts.

Related issue

Closes #49

[netlify]

✅ Deploy Preview for scri-be ready!

Name	Link
🔨 Latest commit	7c1dd67
🔍 Latest deploy log	https://app.netlify.com/projects/scri-be/deploys/69b454aa65af7e000803c593
😎 Deploy Preview	https://deploy-preview-50--scri-be.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

Thank you for the pull request! 💙

The scri.be team will do our best to address your contribution as soon as we can. If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Web rooms once you're in. Also consider attending our bi-weekly Saturday developer syncs! It'd be great to meet you 😊

Note

Scribe uses Conventional Comments in reviews to make sure that communication is as clear as possible.

[github-actions]

Maintainer Checklist

The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

• Tests for changes have been written and the TypeScript, linting and formatting workflows within the PR checks do not indicate new errors in the files changed

• The CHANGELOG has been updated with a description of the changes for the upcoming release (if necessary)

[github-actions]

First PR Commit Check

• The commit messages for the remote branch should be checked to make sure the contributor's email is set up correctly so that they receive credit for their contribution
  • The contributor's name and icon in remote commits should be the same as what appears in the PR
  • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local scri.be repo (can be set with git config --global user.email "GITHUB_EMAIL")

[Cristiano2009Manu]

Hi! I removed yarn.lock and package-lock.json from tracking as they shouldn't be committed. Happy to make any adjustments if needed!

[andrewtavis]

Giving this a quick look, @Cristiano2009Manu :) We do need yarn.lock for deployment to Netlify, so let's keep it in. There are a few more things we'll need to change, that's with the relationship between the localization files in Scribe-i18n and this repo. I'll do the fix, but to explain what I'm doing:

• Scribe-i18n is a sub-module, so I'll send a commit over there with the changes that are needed for this project while working on it from within this project
• I'll then pull the new version of Scribe-i18n into this project

[andrewtavis]

Did a minor change to the CSS as the medium breakpoint wasn't working properly (content was centered with text left justified). Aside from that the changes were mostly formatting :)

[andrewtavis]

Thanks for the great first contribution, @Cristiano2009Manu! Really appreciate the quick work and good communication here :)