Skip to content

fix: solves the alignment issue #2195

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 17, 2025
Merged

Conversation

HarshMN2345
Copy link
Member

Fix: Center CallToAction Component Alignment

Changes

  • Added mx-auto class to the inner content div in CallToAction.svelte to ensure proper horizontal centering.
  • Removed page-level container wrapper from footer components in the education page to maintain consistent component alignment.
  • Each component now handles its own container constraints independently.

Why

The CallToAction component was not properly centered due to missing auto margins on the inner content container. This change ensures consistent alignment across all page components.

Result

  • CallToAction content is now properly centered.
  • Footer components maintain their individual container handling.
  • Consistent component alignment throughout the education page.

After

image

Copy link

appwrite bot commented Jul 17, 2025

appwrite.io

Project ID: 684969cb000a2f6c0a02

Sites (1)
Site Status Logs Preview QR
 website
68496a17000f03d62013
Failed Failed View Logs Preview URL QR Code

Note

Appwrite has a Discord community with over 16 000 members.

@HarshMN2345 HarshMN2345 changed the title fix: solves the alignement issue fix: solves the alignment issue Jul 17, 2025
@HarshMN2345 HarshMN2345 requested a review from ItzNotABug July 17, 2025 09:46
@ItzNotABug ItzNotABug merged commit 2937e61 into main Jul 17, 2025
3 of 4 checks passed
@HarshMN2345 HarshMN2345 deleted the fix-SER-130-Component-not-aligned branch July 17, 2025 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants