-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Comments
Would a good start be to simply hook up the Preview button and make it open in a new tab? |
Is the current Publish button sufficient to close this? |
I was hoping to have a quicker mode to test without opening front end, so let's leave open put consider low priority. |
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. |
Clearing milestone due to the low priority. |
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).
The text was updated successfully, but these errors were encountered: