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
I think it's time to say farewell to MkDocs and mkdocs-material. view.py recently tried writing its own theme for MkDocs, but the result wasn't what I wanted, and so I rolled the docs over to mkdocs-material instead.
The plan now is to use NextJS and MDX for documentation. The most challenging part of this migration (apart from actually writing the docs) is going to be dealing with mkdocstrings generation. I somehow need to figure out how to transfer the generated markdown from mkdocstrings to the TypeScript code. If all fails, view.py will have to abandon mkdocstrings, and write the API reference from scratch (which won't be pretty.)
This will also switch the build system from Netlify to Vercel, but that should be fine.
The text was updated successfully, but these errors were encountered:
Proposal:
I think it's time to say farewell to MkDocs and mkdocs-material. view.py recently tried writing its own theme for MkDocs, but the result wasn't what I wanted, and so I rolled the docs over to
mkdocs-material
instead.The plan now is to use NextJS and MDX for documentation. The most challenging part of this migration (apart from actually writing the docs) is going to be dealing with mkdocstrings generation. I somehow need to figure out how to transfer the generated markdown from
mkdocstrings
to the TypeScript code. If all fails, view.py will have to abandonmkdocstrings
, and write the API reference from scratch (which won't be pretty.)This will also switch the build system from Netlify to Vercel, but that should be fine.
The text was updated successfully, but these errors were encountered: