fix: improve responsive layout

[azdanov]

See #49 (comment)

I removed container classes to avoid "jumping" between breakpoints and instead used a static max-width. Some additional minor cleanup for top padding in about/blog pages.

[Copilot]

Pull request overview

Updates responsive layout behavior across key pages/sections by replacing container-based widths with fixed max-w-* wrappers and adjusting padding/typography for better consistency across breakpoints.

Changes:

• Replace container wrappers with max-w-6xl wrappers (and adjust horizontal padding) to reduce breakpoint “jumping”.
• Adjust spacing/typography on blog/about/download-related sections for improved vertical rhythm.
• Switch edition preview images to static asset imports for use with astro:assets Image.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/pages/[...blog]/[...page].astro	Updates blog list section padding values.
src/layouts/BaseLayout.astro	Replaces arbitrary 2xl font-size class with 2xl:text-xl.
src/components/widgets/Sponsors.astro	Replaces container wrapper with max-w-6xl wrapper.
src/components/widgets/Header.astro	Adjusts header wrapper padding at md breakpoint.
src/components/widgets/Editions.astro	Uses static image imports; replaces container with max-w-6xl and adjusts padding/gaps; tweaks image classes.
src/components/widgets/AboutDistribution.astro	Tweaks vertical padding and heading sizing; simplifies markup structure.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codayon]

Nice. I think, this issue with footer should also be addressed, currently, there is a gap after the sitemap links.

---

If fixed, it may look something like this, thanks.

[codayon]

For DropdownMenu, if we set modal={false} in MenuItems tag, we can scroll even if the dropdown is toggled on. Currently if we toggle the dropdown, it doesn't let us to scroll.

[azdanov]

Nice. I think, this issue with footer should also be addressed, currently, there is a gap after the sitemap links.

That's a valid remark and might warrant discussing, but out of scope of current issue. It was a design decision of current template to left align columns in footer.