I think the key thing for me is we suck at "getting started", and we have many projects from data, to libraries, to low level tools, to command line apps, to web apps. Each of our users may have different concerns wrt. to getting help around each different tools to get started and get docs.

@adaaaam ping

Our page at https://github.com/aboutcode-org also is missing a lot of data and links.
We also have a lot of diagrams from slides and presentations that could be used to better explain all the things we do.

@Thatwriterjon ping... somewhat related, we are tracking upcoming blog posts ideas at https://github.com/aboutcode-org/www.aboutcode.org/issues

Also related is:

• WWW: Select a dev-friendly tool to publish the web site www.aboutcode.org#18

Here is a set of updated ideas for our TODO:

1. patch to ensure aboutcode.org has no dark corners and we can get started nicely
   1.1 ensure we have minimally correct readme and getting started
   1.2 Add PURL! which is conspicuously absent
   1.3 Make blog (and blog posts) visible https://aboutcode.org/blog/

2. move away from WP toward a file-based, git-based workflow
   2.1 Sphinx+Rst, Hugo, Docusaurus, Markdown/MYST?

3. harmonize all docs modeled after SCIO https://scancodeio.readthedocs.io

4. create persona-based, use-case based workflows for docs

5. create code, scripts, deployed demos, and packaging so that its takes under 5 minutes to try out any of our tools, libraries and apps.

6. Also create an org-wide glossary to support consistency:

• Create glossary/standard reference for terms/names used in or to describe products/services www.aboutcode.org#26

Moving this as an issue!