pento / free-as-in-speech Goto Github PK

The WXR library will need to support all of the current WXR features. These can be implemented as they're needed.

• Site info.
• Users.
• Categories.
• Tags.
• Terms.
• Term meta.
• Posts.
• Post meta.
• Comments.
• Comment meta.

When text has been given a custom colour, it will have a style name something like "{\"FG\":\"textColor3\"}".

The actual colour of the text appears to correspond to a value return by the call to /_api/communities-blog-node-api/_api/settings/presets, but there's no obvious link between the style name, and the colour data in presets.

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

It'd be useful to show an overview how much data will be extracted (eg, number of posts, quantity/size of media items), as this would give the end user a rough idea of how long it will take to run.

Describe the solution you'd like

Before clicking the Export button, the extension popup could ask each Extractor to give data on what it will be extracting.

Make it easy to anonymize HARs by replacing UUIDs and randomizing things like date. This will be helpful both for when we want to add more integration tests and if ever we'll want people to submit their HARs for bugfixing.

I believe the HAR download and the anonymization could be done right out of the extension.

Free (as in Speech) was just the first name I thought of for this project, but I'm already finding it to be fairly unwieldy. It's difficult to type, and its acronym (FaiS) is not super pronounceable.

I'd like to get feedback on alternative options for the extension name.

In the communities-blog-app extractor, it currently doesn't properly map all block alignments to WordPress block alignment settings.

The extension currently just uses a generic icon, it should be replaced with something project-specific.

Some things to consider:

• While this project is associated with WordPress, it doesn't necessarily need to use WordPress branding up front. The focus is on "escaping CMS lock-in", rather than "coming to WordPress".
• It'd be useful if it worked in multiple states:
  • disabled (the extension doesn't export anything on the current site)
  • not ready (the extension supports the current site, but needs additional information before exporting)
  • ready (exporting can begin)
  • in progress (we're currently extracting the export)
  • error (something went wrong whilst exporting)

Splitting this off from #2.

TODO

Popup Page

The popup page is the primary UI for interacting with the extension.

• Fill out the page with information about what will be exported.
• After the Export button is clicked, show progress information.
• Add translation for the strings.

Wix Extractor API

This task is focussed on making a generic interface for adding support for extracting from additional Wix apps. This makes it much easier to expand and maintain the library of "app extractors".

• Determine which apps are enabled on the current site.
• Add the ability for extractors to report progress.

There are some additional parts of this API which would be nice to have, but not necessary for an MVP.

• Add the ability to store extracted data in local storage, and resume extraction. Particularly useful to recover from internet outages or browser crashes.

Apps To Support

Blog

• Add support for more blocks than just paragraphs.
• Add support for paging through posts/categories/tags.
• Add media support.

Firefox produces a <random>.xml.part file in the Downloads folder, which contains the full download, but doesn't rename it to the right thing, and doesn't notify you that it's downloaded something.