-
Notifications
You must be signed in to change notification settings - Fork 385
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
Generate userflow based on Validation Workflow efforts #1359
Comments
Question About Format Of User Flow Hi @postphotos,
What format should this diagram have...a wiki page? And would just that satisfy this issue, or are there other formats? Thanks, Leo! |
Based on a discussion today with @postphotos I believe we have a clear pathway to get to the error validation screens once you've activated the plugin. Would love any feedback: |
See also #1183 (comment) for how there is now a pathway for a user to access the validation errors when they don't have native or paired modes enabled. |
I think this should probably be in the wiki, in other documentation and possibly incorporated into a future version of the splash screen. Essentially, I should know how errors are actually actioned. I think this is the simplest version of this:
I can also:
It's as easy as 1, 2, 3, we'd hope! 😸 |
@amedina, @westonruter, @ThierryA We've made some changes to the diagram and updated it to a cleaner and higher fidelity wireframe. Would love any feedback, and also validation that things are all pointing to where they should (since I had to re-arrange some items). Thank you! cc @postphotos |
This wirefame looks awesome!!! I think it captures pretty well the flow. Will give it another pass on the latest build. |
Question About Whether This Is Complete Hi @postphotos and @jwold, |
Yes, I believe so! :) |
As a developer learning about the AMP for WordPress plugin, I should have a clear userflow that describes how to trace and action on AMP errors on my site.
Subissue breaking out the #1006 AC2 into a new task to keep the discussion focused here.
The text was updated successfully, but these errors were encountered: