Skip to content
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

Generate API documentation for all packages #135

Closed
kasperisager opened this issue Aug 8, 2019 · 3 comments · Fixed by #290
Closed

Generate API documentation for all packages #135

kasperisager opened this issue Aug 8, 2019 · 3 comments · Fixed by #290
Assignees

Comments

@kasperisager
Copy link
Contributor

kasperisager commented Aug 8, 2019

Approaches tested so far:

@kasperisager kasperisager self-assigned this Aug 8, 2019
@kasperisager kasperisager added this to To do in ⚙️ Development via automation Aug 8, 2019
@kasperisager
Copy link
Contributor Author

This has become especially relevant now that we've published all packages to GitHub; it should be easy for consumers to discover the different packages and the APIs they expose. API Extractor currently seems like the best candidate, but is still not a viable option due to the reasons listed above.

Also, we should keep an eye on TypeStrong/typedoc#1266.

@kasperisager kasperisager moved this from 📮 To do to 🧑‍💻 In progress in ⚙️ Development Jul 3, 2020
@kasperisager
Copy link
Contributor Author

Work on this is being tracked in #290.

@kasperisager kasperisager moved this from 🧑‍💻 In progress to 📮 To do in ⚙️ Development Aug 4, 2020
@Jym77
Copy link
Contributor

Jym77 commented Dec 10, 2020

To ease the entry cost into Alfa, we could group packages by similar areas of interests. I see 4-5 groups currently:

  • Core functionality: map, list, predicate, equatable, …; these are packages that implement basic data type and interfaces. They are not specific to Alfa and could be in any project.
  • Data manipulation: aria, dom, style, …; these are packages about understanding our data and manipulating it. They could be in any project manipulating HTML documents.
  • ACT implementation: act, rules, …; these are the stuff Alfa really wants to do. They are specific to what we do with it and are essentially the tip of the iceberg that "casual" users might be interested in.
  • test frameworks: chai, cherio, react, …
  • utilities: scrapper, crawler, …

Having such high-level grouping could help navigating the 80 packages we have… Typically, it is fairly obvious (from the name) what alfa-dom is about, but if one doesn't know about it, it's hard to locate in a long list of alphabetically ordered packages…

Not sure how this fits in auto-generated doc. Maybe this could be auto-generated from package description?
Not sure if it would be possible to show that grouping at https://github.com/orgs/Siteimprove/packages?repo_name=alfa or a similar place…

⚙️ Development automation moved this from 📮 Backlog to 🏁 Done Jul 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
⚙️ Development
  
🏁 Done
Development

Successfully merging a pull request may close this issue.

2 participants