HTML Export

[dbolack-ab]

There have been a few requests for versions of "just the render pane" both in posted issues (XX followup with numbers) and in online requests. I'm going to outline the three best options for this task.

1. The return of the old /print route. That's an oversimplification, but accurate. This is primarily for use cases where the Homebrewery React framing of the pages is undesirable. This is mostly useful for direct embedding and providing a consumption endpoint for document conversion. If reimplemented I think it would be wise to lift the proxy loading code from the CBZ PR so that the latter case does not end up with XSS issues.
2. An export button that provides the brewRender iframe contents. This would be a downloadable HTML document.
3. An export button providing a zip file containing the brewRender iframe contents. Additionally, it would contain all referenced "external" files with appropriate file-paths rewritten.

It is worth noting that option One is not incompatible with options Two or Three. Two and Three probably wouldn't be implemented together though Three largely builds on the work of Two.

In my reading of requests, it has never been entirely clear which of these three users want the most. In some cases, I can't tell which the user is requesting. That said, I think implementing both 1 and 3 is the best choice.

[Gazook89]

Collecting those conversations:

• Export to Image [FEATURE]: Save Brew to Image #2278
• Export to HTML/CSS bundle [FEATURE]: Downloadable CSS + HTML bundle #661 and [FEATURE, LOCAL]: Offline save #3226
• SSG CLI tool [FEATURE]: Support for Static Page generation #956 and [FEATURE]: Add command line tool for rendering large brews into a pdf #802

Older conversations:

• reddit - standalone css
• reddit - export to html