Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out flows to start testing the front-end renders blocks as expected #659

Closed
mtias opened this issue May 4, 2017 · 5 comments
Closed
Labels
[Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later

Comments

@mtias
Copy link
Member

mtias commented May 4, 2017

It'd be good to have some form of automated flow for this. Alternative, maybe another view next to "Visual / Text" that is enabled in development that renders the post markup as if it was the front end (quick preview).

@mtias mtias changed the title Figure out flows to start testing the front end renders blocks as expected Figure out flows to start testing the front-end renders blocks as expected May 4, 2017
@mtias mtias added this to the Alpha milestone May 4, 2017
@jasmussen
Copy link
Contributor

Would a good start be to simply hook up the Preview button and make it open in a new tab?

@youknowriad
Copy link
Contributor

youknowriad commented May 12, 2017

Is the current Publish button sufficient to close this?

@mtias
Copy link
Member Author

mtias commented May 15, 2017

I was hoping to have a quicker mode to test without opening front end, so let's leave open put consider low priority.

@mtias mtias added the [Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later label May 15, 2017
@westonruter
Copy link
Member

I want to call this out as being an area for collaboration with Customizer, namely in applying post data and post meta to the frontend for previewing.

@jasmussen
Copy link
Contributor

Clearing milestone due to the low priority.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Priority] Low Used to indicate that the issue at hand isn't a top priority to address and can be handled later
Projects
None yet
Development

No branches or pull requests

4 participants