2 ms·

After poking around your page for a while, as someone mentioned, it's a scavenger hunt to actually find out how to use it. You _really_ need to rework those tu

by ben509 8y ago

After poking around your page for a while, as someone mentioned, it's a scavenger hunt to actually find out how to use it. You _really_ need to rework those tutorials. I'd honestly scrap most of them and write a user guide in narrative form. I know your product is aimed generating, essentially, slideshows, but that's a terrible way to present user documentation. Some of them are indicative of poor design: under Overview, you write "Finding Toolbars", and we need to know this because they're "At Top and Left, Out of View Initially." Don't hide the toolbars and you don't need to tell me where to find them. You have an entire slide "The State of Section Application" explaining how an on-off button works. If you have to explain it, just explain it in the UI: App is Off. [Start up.] App is On. [Shut down.] "Starting a new site" -- It looks like you just copied random stuff from another page. (Or is someone playing with the app and editing your site?)

hopeful2 8y ago
Thank you indeed for your comments. My intention was to get feedback on the editor itself. Your comment on the tutorials (demos) is actually a bonus to us. We will rename the menu item to demo and write separate tutorials and documentation in narrative form as you suggested. The purpose of some sections is to demonstrate site wide section, and may not be in logical order in the demo. The demos are talking points when we provide training to the end users. They can edit the sections and remember a thing or two while they practice. The meaningful words and phrases are better than ipsum lorem. The comments on toolbar are good points too. We have recently changed the workflow for users to edit their content on their own website, on an editable page (index.goandmake.html) next to the published page (index.html). They can navigate to a page and edit. This makes oauth2 integration much harder, but is more intuitive than loading and editing data of a separate domain. so the toolbar can be visible by default, and hidden after user clicks a button. we are going to act on this. It is good you noticed it and brought it up. Highly appreciate your inputs.
- ben509 8y ago
  Thanks! Best of luck with your project!

by ben509 8y ago

hopeful2 8y ago

Thank you indeed for your comments. My intention was to get feedback on the editor itself. Your comment on the tutorials (demos) is actually a bonus to us. We will rename the menu item to demo and write separate tutorials and documentation in narrative form as you suggested. The purpose of some sections is to demonstrate site wide section, and may not be in logical order in the demo. The demos are talking points when we provide training to the end users. They can edit the sections and remember a thing or two while they practice. The meaningful words and phrases are better than ipsum lorem. The comments on toolbar are good points too. We have recently changed the workflow for users to edit their content on their own website, on an editable page (index.goandmake.html) next to the published page (index.html). They can navigate to a page and edit. This makes oauth2 integration much harder, but is more intuitive than loading and editing data of a separate domain. so the toolbar can be visible by default, and hidden after user clicks a button. we are going to act on this. It is good you noticed it and brought it up. Highly appreciate your inputs.

ben509 8y ago
Thanks! Best of luck with your project!