You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: