Skip to content

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

Closed
3 tasks done
mtrezza opened this issue May 28, 2022 · 18 comments · Fixed by #8519 or #8528
Closed
3 tasks done

Modernize API doc template #8017

mtrezza opened this issue May 28, 2022 · 18 comments · Fixed by #8519 or #8528
Labels
bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) state:released Released as stable version state:released-alpha Released as alpha version state:released-beta Released as beta version type:docs Only change in the docs or README

Comments

@mtrezza
Copy link
Member

mtrezza commented May 28, 2022

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

@parse-github-assistant
Copy link

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

@mtrezza mtrezza added the type:docs Only change in the docs or README label May 28, 2022
@dblythy
Copy link
Member

dblythy commented May 28, 2022

Sounds good to me. We can easily drop in the amendment from parse-community/minami#1 (comment)

@mtrezza
Copy link
Member Author

mtrezza commented May 28, 2022

That would be great, also see parse-community/minami#1 (comment) why I would rather not touch the current template.

@dblythy
Copy link
Member

dblythy commented May 28, 2022

The same template will need to be applied to the JS repo too

@mtrezza
Copy link
Member Author

mtrezza commented May 28, 2022

Right, can we then point to the original dependency (rather than maintaining our own fork) and just add a config file to each repo?

@dblythy
Copy link
Member

dblythy commented May 28, 2022

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 @interface to the nav bar.

@okobsamoht
Copy link

I'v tested the clean-jsdoc-theme.

you can take a look here:

https://6297b4ac43cc1f0062fbe19e--parse-server-doc.netlify.app/

here are some screenshots

mobile

desktop

localhost_63342_parse-server_out_ParseServerOptions html
localhost_63342_parse-server_out_Parse Cloud html
localhost_63342_parse-server_out_ParseServer html
localhost_63342_parse-server_out_index html__ijt=25j0lemg3jlvvckrr77g32gdo0 (1)
localhost_63342_parse-server_out_index html__ijt=25j0lemg3jlvvckrr77g32gdo0

@mtrezza
Copy link
Member Author

mtrezza commented Jun 2, 2022

We'd need to make sure that all content is included in the new template; @dblythy mentioned that there was some customization in the old template.

@dblythy dblythy mentioned this issue Oct 12, 2022
31 tasks
@mtrezza
Copy link
Member Author

mtrezza commented Nov 2, 2022

@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.

@mtrezza mtrezza pinned this issue Nov 11, 2022
@mtrezza mtrezza added the bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) label Nov 11, 2022
@KodeyThomas
Copy link

KodeyThomas commented Dec 12, 2022

@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

@mtrezza
Copy link
Member Author

mtrezza commented Dec 12, 2022

Haven't looked at TypeDoc, but it really depends on a feature comparison and what kind of visual themes they offer. What we see here looks pretty good to me already, if it's just a simple template change. In general, we want to switch to another docs framework, see forum.

@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 6.1.0-alpha.8

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label May 1, 2023
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 6.1.0-beta.2

@parseplatformorg parseplatformorg added the state:released-beta Released as beta version label May 1, 2023
@mtrezza mtrezza unpinned this issue May 1, 2023
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 6.1.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label May 1, 2023
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 6.1.0-alpha.9

@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 6.3.0-beta.1

@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 6.3.0-alpha.1

@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 6.3.0

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) state:released Released as stable version state:released-alpha Released as alpha version state:released-beta Released as beta version type:docs Only change in the docs or README
Projects
None yet
5 participants