export: provide hosted export targets

Is your feature request related to a problem? Please describe.

Nope.

Describe the desired outcome

Currently, if I export I just get a bare HTML file. If I want to share this with peers, I need to publish it myself.

While I personally know of and have access to a dozen ways to publish a single HTML file rapidly, this isn’t true of everyone who may use Accessibility Insights.

I’d love to see something like “Export to…” built-in to this project - more specifically, it would be cool to see “Export to…” options for Glitch, CodePen, GitHub Pages (if authed and a repo is selected?), and possibly even enable the community to contribute additional targets.

Describe alternatives you’ve considered

The status quo is one alternative - it doesn’t add any complexity, but does make exporting and sharing results harder.

An additional option would be an interactive CLI published to npm that requires you have npm and Node.js installed. Running something like npx insights-publish ./path/to/insights/export.html could be another option. This seems like potentially a significantly larger amount of work would be needed, though if you wanted to build built-in plugin support you could add something like npx insights-publish --to=glitch ./path/to/insights/export.html where the module resolves --to=glitch as an additional module with a prefix like insights-plugin-glitch that it will install and that can hook into an extension API and publish as the author of insights-plugin-glitch defines.

Additional context

None.

[juchampa]

Hi @bnb ,

We are happy to inform you this issue has been addressed through a public contribution to our open source repository here, by @sean-beard . This feature is now under a public flag, so feel free to use this feature and contribute to it if you’d like.

[ferBonnin]

this has been resolved for a while after the codePen integration with no other users’ comments. closing 😃