Export

[psrpinto]

The user went through all this trouble to get their information into Playground. Now they need to easily export it into their permanent host.

[psrpinto]

We need to drill-down this issue. This is a crucial part of the user experience IMHO.

[ashfame]

My take: Since Playground will eventually support streaming all the content to a real prod webhost, we just rely on that and not build anything in try-wp.

try-wp fits itself into the process of data liberation, and once content is available in Playground, we have met that goal.

For me, try-wp is just a thin layer acting as fallback to figure out the context of the website in absense of structured data and all the PHP side stuff is reused or built there for rewriting url, downloading assets etc. Exactly what you linked to in #141 and similarly for #57

[psrpinto]

Agree that we should leverage the export features already provided by Playground. We'll need to figure out how to include those features in Try WordPress, at the moment Playground's export UI is not present in Try WordPress.

[ashfame]

Quick thought: Minimal way would be to just guide the user to PG page to get their export out by either just instructions after redirecting them to the right page or use tour plugin to guide them.

[psrpinto]

I'm not sure I understand how the tour plugin could be useful here, could you clarify? Specifically, what would be the button (or other UI component) that the tour plugin would highlight as the first step the user needs to do the export?

[ashfame]

So consider an admin page in WordPress where post-transformation steps are handled. Basically how the existing importers in WordPress work - they work on a WP admin page and shows progress/results there. So if those options are available there, we can also guide the user there by navigating them to its url and then using tour plugin to walk them around.