Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

[topic] Why Web Components? #30

Open
2 tasks done
Tracked by #33
, #34
...
justinfagnani opened this issue Jun 14, 2022 · 0 comments
Open
2 tasks done
Tracked by #33
, #34
...

[topic] Why Web Components? #30

justinfagnani opened this issue Jun 14, 2022 · 0 comments
Labels
documentation Improvements or additions to documentation topic Topic content

Comments

@justinfagnani
Copy link
Member

Code of conduct

  • I agree to follow this project's code of conduct.

Description of request

From the outline the "Why Web Components?" page will cover:

  • What do we mean by interop?
    • Interop with HTML, frameworks, the browser
    • Interop with file formats: Markdown vs MDX, etc.
    • Interoperable composition with slots
    • Interop with the future
  • Use cases
    • Standalone components
    • Component sets and design systems
    • Applications

This section is part of the docs MVP milestone.

Related link(s)

No response

Are you interested in authoring this content?

  • Yes
@justinfagnani justinfagnani added documentation Improvements or additions to documentation topic Topic content labels Jun 14, 2022
This was referenced Jun 14, 2022
Open
Merged
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation topic Topic content
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@justinfagnani