Propose new functionalities for Decidim software
#DecidimRoadmap Designing Decidim together
I think it would be better if the Collaborative Drafts wizard form followed the same standard as the Proposals wizard form.
Right now:
- Step 1 Create: presents a form and, if submitted, sends (title/body) attributes through URL to Step 2
- Step 2 Compare: compares received attributes and presents any similar collaborative drafts, then sends (title/body) attributes through URL to Step 3
- Step 3 Complete: presents a form again and, if submitted, creates the resource.
With new changes:
- Step 1 Create: presents a form and, if submitted, creates a collaborative draft (hidden from the public view until step 4 is completed)
- Step 2 Compare: compare collaborative draft and presents any similar collaborative drafts
- Step 3 Complete: presents a form again to edit collaborative draft and gives chance to discard current draft
- Step 4 Preview: Previews final form of collaborative draft and gives option to make public or to edit.
Since the action of publishing has another meaning for collaborative drafts, the action of step 4 could be called: Open; and the help text could be something like: Open your draft to collaboration
The main advantages are:
- Since the collaborative draft would actually be created in the first step, the user would be able leave the form and come back to finish the job later, without worrying about losing the information.
- Pass attribute values through (1) POST request instead of through (2) URL
(1) "domain/processes/slug/f/12/collaborative_draft/id/compare"
(2) "domain/processes/slug/f/12/collaborative_drafts/compare?utf8=%E2%9C%93&collaborative_draft%5Btitle%5D=This+is+a+title+2&collaborative_draft%5Bbody%5D=This+is+a+body+2&commit="
Report inappropriate content
Is this content inappropriate?
8 comments
Another reason to pass the values through a POST request is to prevent a ActionDispatch::Cookies::CookieOverflow when creating a long Collaborative Draft body , another advantage is that enables form validation.
GH Related:
Conversation with Oliver Valls
Instead of doing this, I would add the draft as a standard Proposal creation step. So there aren't two paths for creating a Proposal. This will require removing the create collaborative draft button.
So when creating a proposal, the "confirm" step is replaced by the Proposal draft (it may be collaborative or not depending on the author).
Step 2 Compare: compares received attributes and presents any similar Proposals (not collaborative drafts)
Step 3 Complete: presents a form again and, if submitted, creates a (Collaborative) Draft
Step 4 the author can publish the draft when she wants
Even step 3 can be removed and after confirming that the proposal that is going to be created doesn't coincide with any existing proposal a collaborative draft may be created.
+1!!!!!
@oliver_valls You mean that enabling collaborative drafts should instead give the option in the last step of the wizard form to publish as a proposal or to create a collaborative draft?
Hi @aitorlb,
No, I meant that collaborative would be part of the standard Proposal creation. (drafts won't be dis/enabled, they'd be just one step)
That makes so much more sense! The current UX is really counter-intuitive!
One "Create proposal" button, one flow and ask at the end if the person is open for improvement and co-construction or is already completely set on their proposal.
I agree with what has been proposed here. It also makes much more sense to me that the entry of proposals is unique, regardless of the number of authors.
My main doubt is how to combine drafts (open to editing) with proposals (closed to editing) once the support gathering phase begins. Are all drafts closed automatically? Those that have not been closed by their authors are discarded?
Add your comment
Sign in with your account or sign up to add your comment.
Loading comments ...