amusewiki
amusewiki copied to clipboard
melmothx
CreateText process is confusing. Why should I edit (page 2) after I create?
(1) I had just previously edited an article's author data. During that edit, I did fill in my own contact email (2) When I submitted the article, I hit the "Create" button and went to the next screen (3) The next screen was the edit screen. This was very confusing to me. I thought i just created the article. Why do I have to edit it? I have no further edits to make. (4) I think this second screen should be eliminated or reduced and that most of these important choices should be put on the first screen (5) In the end I was confused whether or not I really did create the article and if so, when I would be notified of its approval
mcverter [email protected] writes:
(1) I had just previously edited an article's author data. During that edit, I did fill in my own contact email (2) When I submitted the article, I hit the "Create" button and went to the next screen (3) The next screen was the edit screen. This was very confusing to me. I thought i just created the article. Why do I have to edit it? I have no further edits to make. (4) I think this second screen should be eliminated or reduced and that most of these important choices should be put on the first screen (5) In the end I was confused whether or not I really did create the article and if so, when I would be notified of its approval
Hi.
The fact that you didn't need to do any edit on (3) is purely incidental.
On the first step it clearly says (in two places):
"Keep in mind that I’m cleaning the text and give it back to you in the markup used on this site. It’s up to you to check it and finally upload it. Some rarely used markup will be lost in the process. Please check the preview on the next step, where you can also insert images."
Then it says on the second step, with an alert as well:
"Not finished yet! Please have a look at the text and then click on "Save" to finalize your submission!"
On the first screen, the HTML import is provided as a courtesy to the user, but it's not the definitive source, which needs to be checked by the human, and that's why the editing step is required.
-- Marco
Ok. the problem was that I was looking for a place to input my contact email and could not find it on the first page.
I am not clear what the first page button "Create" does then. Create means create. It is done then. It is created. Process Over
Edit is a different step. I did not read over the language, yes. There was too much going on. But you shouldn't need this second page.
Once the user presses a button labeled "Create", all necessary work should be concluded
mcverter [email protected] writes:
Ok. the problem was that I was looking for a place to input my contact email and could not find it on the first page.
I am not clear what the first page button "Create" does then. Create means create. It is done then. It is created. Process Over
Edit is a different step. I did not read over the language, yes. There was too much going on. But you shouldn't need this second page.
Once the user presses a button labeled "Create", all necessary work should be concluded
That's rarely the case. Typographical filters, images, table, verses, they all can't be done there. That's why the editing step is needed (beside the logical problem I've already explained). Footnotes may or may not turn out correctly.
The button could be renamed "Setup the text and edit it", if that helps, but that's not what the issue title says (I think in the past it was label this way).
In theory, for a sloppy run, I could agree for an opt-in express lane which would skip the editing on the second page, but I think it would encourage sloppiness. There's no real preview on the first page. How do you know the outcome is good?
Especially for a moderated wiki, where you submit a text and wait for an approval, this is absolutely not good.
-- Marco
I haven't explored the use cases enough to be able to respond to your comment. You make a clear argument why a post-processing edit stage might be necessary.
I think if you just toggle parts of the UI more easily, the problem would be solved. There is a ton of text and user interfaces. Just let the user close those up in a collapsible frame.
On Thu, Jun 18, 2020 at 11:03 AM Marco [email protected] wrote:
mcverter [email protected] writes:
Ok. the problem was that I was looking for a place to input my contact email and could not find it on the first page.
I am not clear what the first page button "Create" does then. Create means create. It is done then. It is created. Process Over
Edit is a different step. I did not read over the language, yes. There was too much going on. But you shouldn't need this second page.
Once the user presses a button labeled "Create", all necessary work should be concluded
That's rarely the case. Typographical filters, images, table, verses, they all can't be done there. That's why the editing step is needed (beside the logical problem I've already explained). Footnotes may or may not turn out correctly.
The button could be renamed "Setup the text and edit it", if that helps, but that's not what the issue title says (I think in the past it was label this way).
In theory, for a sloppy run, I could agree for an opt-in express lane which would skip the editing on the second page, but I think it would encourage sloppiness. There's no real preview on the first page. How do you know the outcome is good?
Especially for a moderated wiki, where you submit a text and wait for an approval, this is absolutely not good.
-- Marco
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/melmothx/amusewiki/issues/347#issuecomment-646078563, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALC7BD7GM5NFMDSQLMNGOLRXIUDLANCNFSM4OBTN7OA .
--
How can I ......explain ............to you my state of mind? The earth has a whole skyful of lights... The blue sky, ......a hell of a lot ............of stars.
Vladimir Mayakovsky
mcverter [email protected] writes:
I haven't explored the use cases enough to be able to respond to your comment. You make a clear argument why a post-processing edit stage might be necessary.
I think if you just toggle parts of the UI more easily, the problem would be solved. There is a ton of text and user interfaces. Just let the user close those up in a collapsible frame.
The funny thing is that the pieces taking up more screen (filters and cheatsheet) are already collapsible, and they are even configurable site-wide and per-user for the initial state.
The problem is that you hide that, and nobody will click on them, so you solve a problem but you get another. And that's why it's configurable, so it's up to the admins to make the decision. So there's no "just" here.
-- Marco
ok. give me more time with it and i will think about how you can make the UI easier to use. I am mostly a front end dev, but I can also write PHP
mcverter [email protected] writes:
ok. give me more time with it and i will think about how you can make the UI easier to use. I am mostly a front end dev, but I can also write PHP
Sure, take your time
-- Marco