-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Modernize API doc template #8017
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
Comments
Thanks for opening this issue!
|
Sounds good to me. We can easily drop in the amendment from parse-community/minami#1 (comment) |
That would be great, also see parse-community/minami#1 (comment) why I would rather not touch the current template. |
The same template will need to be applied to the JS repo too |
Right, can we then point to the original dependency (rather than maintaining our own fork) and just add a config file to each repo? |
There were some changes to the template which may have been the reason why there is a fork. The main changes seem to be to add |
I'v tested the clean-jsdoc-theme.you can take a look here:https://6297b4ac43cc1f0062fbe19e--parse-server-doc.netlify.app/here are some screenshotsmobiledesktop |
@parse-community/server Anyone wants to pick this up for Parse Server 6? While it's not required for release, it would still be nice to have a modern docs layout with the new release. |
Have you had a look into TypeDoc it's made for TypeScript but works fine in a JS project, I've used it in a few projects and it's worked pretty well. However, I do think we need a general refactor of the docs to make things a bit more clear for new users. Happy to pick this one up if I get a bit of free time before Jan |
🎉 This change has been released in version 6.1.0-alpha.8 |
🎉 This change has been released in version 6.1.0-beta.2 |
🎉 This change has been released in version 6.1.0 |
🎉 This change has been released in version 6.1.0-alpha.9 |
🎉 This change has been released in version 6.3.0-beta.1 |
🎉 This change has been released in version 6.3.0-alpha.1 |
🎉 This change has been released in version 6.3.0 |
New Feature / Enhancement Checklist
Current Limitation
The API docs are generated from JSDoc. We are currently using our forked version of an JSDOc template that seems pretty outdated and not well maintained.
Feature / Enhancement Description
Switch to a more modern template that is maintained and improves usability, for example:
Example Use Case
n/a
Alternatives / Workarounds
n/a
The text was updated successfully, but these errors were encountered: