-
-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
basic reference with one page per function #661
base: main
Are you sure you want to change the base?
Conversation
+ use name instead of longname for linking
hmm the prebuilt reference pages are 10MB in total, just because there are so many: a total of 229 paths, each having ~40kB.. I wonder if that 10MB per build will exceed some quota or slow down the build. if yes, it should make more sense to find a way to do this dynamically. |
maybe it makes more sense to have a single reference page with anchor links? would be significantly smaller + no extra sidebar would be needed (can use right sidebar) + full text search would be much more useful |
I think the anchor links is one solution, assuming that it works better than the current solution. However, I still think having one function per page would be better, as each page could have more information and more examples on, including links to similar/related functions. See how pure data handles that below With regards to build size, could the docs be built separately? |
Yep it's certainly better..
It is already built separately but you'd still have to download everything as part of the desktop app It would be possible to have a URL like edit: if that doesn't work, it would also be possible to have a link "show more examples" or similar |
No description provided.