Skip to content

Determine how to map our typography components to Markdown #1116

Closed
@natdink

Description

@natdink
Contributor

Markdown is used in our platform so users can format an app or model description, for example. But OOTB markdown returns really large size when using their methodology.

So if our users decide to use markdown when writing a model description, it will display very large. For example, I have added a description here with a markdown of H1.

Image

Instead, what we want to do is map the markdown headers to smaller typography components that exist in our design system. So if a user calls markdown Header 1 with a "#" we might map that to our MUI header 3 component instead so they can never create markdown that looks really bad in our UI. Every time they use markdown within our platform (excluding the markdown block in the drag and drop), they will be using the mapped version that we set.

Image

Activity

added theissue type on May 12, 2025
natdink

natdink commented on May 14, 2025

@natdink
ContributorAuthor

@Pooja-1801 I took another stab of explaining what is needed for this ticket. Can you read through and start working on this?

natdink

natdink commented on May 19, 2025

@natdink
ContributorAuthor
bfekadu21

bfekadu21 commented on May 22, 2025

@bfekadu21

@Pooja-1801 added feedback in Figma! I think we're headed in the right direction.

Pooja-1801

Pooja-1801 commented on May 23, 2025

@Pooja-1801

Created Markdown Design to check and map our typography components to Markdown

Image
Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @natdink@ehynd@Pooja-1801@bfekadu21

      Issue actions

        Determine how to map our typography components to Markdown · Issue #1116 · SEMOSS/semoss-ui