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

Agnostize React components #47

Open
evaera opened this issue Oct 5, 2021 · 0 comments
Open

Agnostize React components #47

evaera opened this issue Oct 5, 2021 · 0 comments

Comments

@evaera
Copy link
Owner

evaera commented Oct 5, 2021

Right now the Docusaurus plugin contains all of the react code for rendering the docs. What if we want to reuse those React components in other websites that aren't Docusaurus?

The output from the extractor is agnostic to how it's rendered. I think it makes sense for the React components to be the same way. Reusable, included in any project. The react components are mostly pure, (data in, view out) so it should be relatively trivial to do this. We would use them from the docusaurus plugin, but this would allow us to use them in other doc generators too.

This would also allow us to make room for a very stripped down website that just renders the docs and doesn't have any of the overhead or unknowns from Docusaurus. This is more similar to how Rustdoc works. This way, when we eventually want to render and host docs from Wally packages, we can be more sure about the safety of the content. We won't have to worry about Docusaurus having a vulnerability because they don't expect to be given unsafe input.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant