Documentation site - niggly issues #2770
Replies: 4 comments 2 replies
-
@chrisk-7777 We have been talking about changing our tech here, nothing has really solidified yet. Docusaurus looks pretty dope, just watched some videos about it and it checks a lot of boxes! In general I'll support anything that makes it easier to contribute and maintain (the current gatsby setup is a little tough). @kamranayub @jedeen I'll defer to you on doc site changes! What do you think?
|
Beta Was this translation helpful? Give feedback.
-
I've created an issue to track the rewrite: excaliburjs/excaliburjs.github.io#383 |
Beta Was this translation helpful? Give feedback.
-
Closing in favor of excaliburjs/excaliburjs.github.io#383 Thanks Erik and Kamran ! |
Beta Was this translation helpful? Give feedback.
-
Not sure if we posted the link, but you can check out the in progress site here! https://excaliburjs.pages.dev/ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I've been doing a quick spike locally to see if I can address a few niggly issues on the docs.
They don't have issues in the backlog, but they are pretty minor, so I thought it wouldn't hurt to raise.
They are:
Before I go down that rabbit hole, I was wondering if the core team had considered something like docusaurus that handles a lot of that out of the box?
Obviously any change as fundamental as the framework running the site is not to be made lightly - so in no way am I suggesting that should be the direction! More so curious on the overarching direction of the docs.
But... just for fun, I threw the first few pages in a docosaurus site:
Beta Was this translation helpful? Give feedback.
All reactions