Extension pages

[everzet]

• Publish information about tracked and released extensions (reference: https://atom.io/packages)
• Design and template extension list and extension page, link to documentation page

[jakzal]

How would you envision discovering new extensions? Would a yml file with a list be sufficient to start with? Extension authors would need to submit a PR in order for their extension to be shown on the site.

[everzet]

You're talking about #14. This issue is just about handling incoming releases. The starting point for documentation OR extension information parsing is here.

Basically, you call the ReleaseManager::release() by providing release reference to it. Release reference contains (currently) GitHub repository name and a version ID (which could be a branch or a tag name). ReleaseManager listeners then do the rest - Release module downloads that particular release, Documenter builds documentation and ExtensionCatalogue (coming from this issue) parses extension information.

Documenter is already finished and does his job of documentation generation on every release you give it to (if it has documentation, of course). This issue is about also generating and accessing extension information on every release.

When that is done we'll need to decide on how would we approach #14. Either it will be a webhook that accepts any GitHub release notification, or a CLI script with a list of extensions in yml file that tries to find all new releases or a combination of both. But that comes in #14

[everzet]

Documentation is ready, so this one is the next issue I'm working on.