Skip to content
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

fix(docs): Logical sequence for internal components #1845

Open
wants to merge 1 commit into
base: canary
Choose a base branch
from

Conversation

Sonkaryasshu
Copy link

changed internal components sequence to be more logical and easy to follow.

changed internal components sequence to be more logical and easy to follow.
Copy link

changeset-bot bot commented Dec 27, 2024

⚠️ No Changeset found

Latest commit: 3fdc8c7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Dec 27, 2024

@Sonkaryasshu is attempting to deploy a commit to the resend Team on Vercel.

A member of the Team first needs to authorize it.

@gabrielmfern
Copy link
Collaborator

Why is this easier to follow exactly?

@Sonkaryasshu
Copy link
Author

The updated sequence groups related components logically, making it easier to locate and understand their context. For instance:

  • Structural components like row, column, and section are grouped together in a meaningful order, reflecting the hierarchy typically used when building layouts or following docs(when i realised to correct it).
  • Content-related components like image, text, link, and button are positioned near each other, aligning with how they are often used in tandem.
  • Utility components like code-block, code-inline, and font are placed together to streamline their reference.

This organization reduces cognitive load by reflecting the natural flow of creating email layouts, making the docs more intuitive and efficient to use.

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