-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
PLANNING ISSUE: Draft Feature #2667
Comments
I think ftos would be great and if any new community members are joining
our soc programs this summer and haven't had the experience of helping a
newcomer complete a PR this could be a great chance! @publiclab/reviewers
what do you think?
…On Fri, Apr 27, 2018, 7:12 PM Gaurav Sachdeva ***@***.***> wrote:
Hi @jywarren <https://github.com/jywarren> @steviepubliclab
<https://github.com/steviepubliclab>,
*I want to inform you guys that my exams are scheduled from 21st May to
6th June, so I wouldn't be able to do much in that time period. I would be
available for task discussions/calls/messages. I will try to open and solve
small issues in-between exams. So, I would try to do as much work as
possible till 18th May and possibly we would be done with this issue till
then.*
Issue progress: #2307 <#2307>
contains checklist but some more points need to be added and discussed
that's why I opened this issue. Most of Back-end for this feature is ready
#2308 <#2308>.
Remaining Tasks:
1. Displaying Draft on author's, moderator and admin's dashboard ---
In progress at #2666 <#2666>
2. Change in _node_default.html.erb and _node_meta.html.erb to
distinguish draft from normal notes as we do for first-timer posts
3. Addition of "draft" field in output data of PublicLab editor object
(discussion at #2594 <#2594>
)
4. Addition of checkbox and JavaScript function in rich.html.erb
5. Addition of "Draft" label on notes/show.html.erb
6.[ ] Publish_draft method in controller and its testing
6. Addition of Publish button on notes/show.html.erb
I have tried to divide the issue in minimum part as possible, I can solve
2,4,5,6 and 7 in a single PR or multiple , but I see that some parts can be
good FTO candidates like 2,3,5 and 7. What do you guys think, should I open
FTO's or not ? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2667>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJysec5AdjKUQweaB_-acJgyw_Pb_ks5ts6XLgaJpZM4TrH7C>
.
|
Ok, I will open FTO issues. |
@jywarren which label class would be appropriate for Draft. We are using danger class for unpublished |
How about -success -- that'll be green, more friendly :-)
…On Fri, Apr 27, 2018, 7:56 PM Gaurav Sachdeva ***@***.***> wrote:
@jywarren <https://github.com/jywarren> which label class would be
appropriate for Draft. We are using danger class for unpublished
[image: unpub]
<https://user-images.githubusercontent.com/20878070/39389289-92941090-4aa4-11e8-8cca-3bb3962dbc2f.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2667 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJy5DdiFABYEY0n2-Iwv8BSATehfLks5ts7AfgaJpZM4TrH7C>
.
|
Hey @Gauravano @ViditChitkara, We all three have same project so what we can do is divide the issues between three of us to work. Let me know when you are free so that we can plan this out. |
hi @namangupta01 , totally agreed. Let's open a new issue or move to channel for further discussion. Thanks ! |
Hi @namangupta01 , @Gauravano ! |
In our case, we all have same project ideas, so a Planning issue is important to sync with each other. Although, if you create Planning issue for your project, we may get chance to chime in so, good to create one. |
:-)))) great going, team!
…On Sat, Apr 28, 2018, 3:11 AM Gaurav Sachdeva ***@***.***> wrote:
In our case, we all have same project ideas, so a Planning issue is
important to sync with each other. Although, if you create Planning issue
for your project, we may get chance to chime in so, good to create one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2667 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJwzD568ZKaC4mB6oCAuTe05KY46tks5ttBX_gaJpZM4TrH7C>
.
|
hey @jywarren @ebarry @steviepubliclab , I just published an article https://medium.com/@gauravano/https-medium-com-gauravano-gsoc-18-with-public-lab-46588104ad0d . Your comments and suggestions are welcome. Should I post it on PL website? |
Awesome - great to see this at PublicLab.org now too! https://publiclab.org/profile/gauravano @publiclab/soc -- if anyone else is interested in writing updates like these, or anything about your work, it's very welcome on PublicLab.org -- thank you!!!! |
@jywarren @steviepubliclab which design would be good for displaying draft on the dashboard. Also, please state if user view needs to be different that mod/admin or not. Like, we have for the moderated post. Design 1: Similar to Moderated node with some textDesign 2: Label with nodeOr any other ideas are welcome : ) |
ooh, i like the green label. but could we put it preceding the title on the
same line?
This would only be visible to people who are working on a draft, right? or
to admins? What would set the "publish date" of the post?
…On Wed, May 16, 2018 at 12:37 PM, Gaurav Sachdeva ***@***.***> wrote:
@jywarren <https://github.com/jywarren> @steviepubliclab
<https://github.com/steviepubliclab> which design would be good for
displaying draft on the dashboard. Also, please state if user view needs to
be different that mod/admin or not. Like, we have for the moderated post.
Design 1: Similar to Moderated node with some text
[image: draft]
<https://user-images.githubusercontent.com/20878070/40139564-e460f23a-596d-11e8-970f-56720a9f3018.png>
Design 2: Label with node
[image: draft_label]
<https://user-images.githubusercontent.com/20878070/40139788-a74b78ec-596e-11e8-8715-21ea91910fb7.png>
Or any other ideas are welcome : )
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2667 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJx0eaKIPPURIE5o6FAI2x95HnBlaks5tzIAUgaJpZM4TrH7C>
.
|
Also, please comment on the opacity of the above draft listing.
yup, it would be visible to the author, moderator, and admin for now : ) . In above image, you are seeing the date at which draft is created by the user. For publish date, I will update the date entry when user would publish the draft. |
Oh I also like the green for draft. I think the Publish button might need
to be a bit more prominent?
Best,
Stevie
…On Wed, May 16, 2018 at 4:22 PM, Gaurav Sachdeva ***@***.***> wrote:
After that, we need to decide the position and design of "publish draft"
button
For start here it is design:
[image: publish_button]
<https://user-images.githubusercontent.com/20878070/40144745-4499b308-597d-11e8-99ef-77ae7c7fc903.png>
Any relevant icon in mind ? please comment on the position too. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2667 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHJLrp2VzVGFewQYCwfu_e-T-sAqlPv7ks5tzJizgaJpZM4TrH7C>
.
|
We can have a prominent "Publish Draft" button in the alert banner that
says "This is a draft" maybe?
…On Wed, May 16, 2018 at 2:37 PM, Stevie ***@***.***> wrote:
Oh I also like the green for draft. I think the Publish button might need
to be a bit more prominent?
Best,
Stevie
On Wed, May 16, 2018 at 4:22 PM, Gaurav Sachdeva ***@***.***
>
wrote:
> After that, we need to decide the position and design of "publish draft"
> button
> For start here it is design:
>
> [image: publish_button]
> <https://user-images.githubusercontent.com/20878070/40144745-4499b308-
597d-11e8-99ef-77ae7c7fc903.png>
>
> Any relevant icon in mind ? please comment on the position too. Thanks.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#2667 (comment)
>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-
auth/AHJLrp2VzVGFewQYCwfu_e-T-sAqlPv7ks5tzJizgaJpZM4TrH7C>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2667 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ9ZQExWi3iqFH9V3E6UaF7k2KkT_ks5tzJv-gaJpZM4TrH7C>
.
|
okay, I'll post new design for "Publish draft" button in few hours. Thanks. |
Hi Gaurav - I was wondering a couple things. First, does everyone get to
see drafts on the dashboard (meaning just title and photo)? Or did I read
that logic wrong. Maybe it should be just the author...
Second, we set a final url with the publish date in it. I wonder if we
should reset the url at the moment of final publication, and before then we
can use a temporary one, resetting this on publication? This is a little
complex but seems workable, no? There's a generate_path method to
recalculate the path with the current title and date. That way the title
could be changed as well and this would reflect in the final URL.
…On Thu, May 17, 2018, 7:20 AM Gaurav Sachdeva ***@***.***> wrote:
Reopened #2667 <#2667>.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#2667 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ_FDf975eCJTR5qHysgYhRqDxfHMks5tzYbugaJpZM4TrH7C>
.
|
hi @jywarren, in #2666 I have changed the logic as so, author of the draft, moderator and admin would be able to see the draft on the dashboard and access it too. Do you think this logic needs correction? ok, I would call generate_path method to generate new URL at time of final publishing of draft. I would push commits on |
Hi @jywarren @steviepubliclab , I have a raised a PR for final part of Draft feature ie., sharing secret URL. Here's demo : https://drive.google.com/file/d/1lxhz-v2WhPwBR9GMut83SrOAwPxdH-mX/view?usp=sharing Also, I have pushed on Here's some queries regarding design:
Thanks. |
Wow this is very cool. I'd say, let's display the prompt to share within
the Draft Note alert at top, with a button that says "Share a secret link".
And i like your using an `alert()` but we can do one better -- a
`prompt('This link will give recipients access to ','link')` -- what do you
think?
What about using a normal node tag, since the URL will not be visible
anyways... i guess the node tag may appear in some listings, so it's not as
secure. But user tags also will be publicly visible...
Could we hide this particular user tag? It seems a little bit delicate for
maintainability, to use user tags in such a unique way. But you're right, I
can't think of another easy way.
Wait -- what if we added a unique hash to the end of the draft URL path,
since that's not public, and since we'll overwrite it on publication?
And then the notice of "Draft Note" could explain that "the temporary URL
of this post can be shared to give others access to read it. Click here to
add a co-author"... what do you think?
Thanks for thinking this through!!
…On Sat, Jun 16, 2018 at 5:55 PM Gaurav Sachdeva ***@***.***> wrote:
Hi @jywarren <https://github.com/jywarren> @steviepubliclab
<https://github.com/steviepubliclab> , I have a raised a PR for part of
Draft feature ie., sharing secret URL. Here's demo :
https://drive.google.com/file/d/1lxhz-v2WhPwBR9GMut83SrOAwPxdH-mX/view?usp=sharing
Also, I have pushed on unstable , you can try there too.
Here's some queries regarding design:
1. Where the "Generate secret URL" should be placed and how should it
look?
Current view:
[image: screen1]
<https://user-images.githubusercontent.com/20878070/41502694-bd048ffc-71dd-11e8-9581-9d0aa4ba5839.png>
1. The URL is shared via a alert for now - is it appropriate?
Current view:
[image: screen2]
<https://user-images.githubusercontent.com/20878070/41502701-ee7abab6-71dd-11e8-85a4-c270cd5f3d5d.png>
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2667 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJwpIPY9fmEkigMFhtnfKZ0p1vZ6Oks5t9X6xgaJpZM4TrH7C>
.
|
Hi @jywarren, i will use prompt, thanks for pointing!
Just to be sure we are on the same page - I am storing a unique token in a power tag as you can see and then secret URL is generated by appending that token to the end of normal URL, as you said, at time of publishing, the URL is changed. Do you mean something like hash function? |
The only issue is that any tag is readable to the public, even if it's not super obvious. like they're listed alphabetically on /tags, for example. So since:
we could use that to append an alphanumeric hash to the end like |
Yes, you are right @jywarren. I will update my PR. Thanks. |
Hey @jywarren , I updated my PR with slug to save the secret token and also changed alert to prompt. Please review it. Thanks! Also, please comment about the "Generate secret URL" button and prompt text. Thanks again! |
Let's name the button "share private link" and put it in the alert? |
And "with which" instead of "using which" -- and then this looks good! |
@jywarren putting button in an alert? |
Do you mean notice? |
Great work on this, btw!!! |
Oops, yeah - you got it. Maybe just "This is a draft note. Once you're
ready, click [Publish] to make it public. You can share it with
collaborators [using this private link]" ?
Exciting!!
…On Sat, Jun 23, 2018 at 3:42 PM Gaurav Sachdeva ***@***.***> wrote:
Here's the updated view
[image: pic_draft]
<https://user-images.githubusercontent.com/20878070/41813038-8502ef7c-774b-11e8-9785-4d7c8a8b4820.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2667 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ68BrFB8h5PEl6iobtaspbJ8PdpIks5t_pn5gaJpZM4TrH7C>
.
|
@jywarren we can also generate the sharable link at the time of draft creation and then can show it in notice as you mentioned, instead of "Generate link" button in notice. What do you think? |
Also, I have opened an issue at #2920 regarding the display of Drafts, I would like to have your thoughts there @jywarren @steviepubliclab .Thanks! |
That sounds good - one step simpler?
…On Wed, Jun 27, 2018 at 12:48 PM Gaurav Sachdeva ***@***.***> wrote:
Also, I have opened an issue at #2920
<#2920> regarding the display
of Drafts, I would like to have your thoughts there @jywarren
<https://github.com/jywarren> @steviepubliclab
<https://github.com/steviepubliclab> .Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2667 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ-7TbOyb1xRlZ_r_Z_6NV_jnPlB1ks5uA7dbgaJpZM4TrH7C>
.
|
Any other change @jywarren ? Thanks. |
Looks fantastic!!!
…On Sat, Jun 30, 2018, 6:09 AM Gaurav Sachdeva ***@***.***> wrote:
Any other change @jywarren <https://github.com/jywarren> ? Thanks.
[image: draft_notice]
<https://user-images.githubusercontent.com/20878070/42124164-96b63906-7c7b-11e8-96f3-1c0e3cb80a50.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2667 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ6CW_J4h3jEPsP1FmW3zamrbDenRks5uB04tgaJpZM4TrH7C>
.
|
Let's do it!
…On Sat, Jun 30, 2018, 9:07 AM Jeffrey Warren ***@***.***> wrote:
Looks fantastic!!!
On Sat, Jun 30, 2018, 6:09 AM Gaurav Sachdeva ***@***.***>
wrote:
> Any other change @jywarren <https://github.com/jywarren> ? Thanks.
>
> [image: draft_notice]
> <https://user-images.githubusercontent.com/20878070/42124164-96b63906-7c7b-11e8-96f3-1c0e3cb80a50.png>
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#2667 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AABfJ6CW_J4h3jEPsP1FmW3zamrbDenRks5uB04tgaJpZM4TrH7C>
> .
>
|
Ping me when you're ready to merge it! Great work! |
It's ready @jywarren! 😃 |
Hi @jywarren @steviepubliclab,
I want to inform you guys that my exams are scheduled from 21st May to 6th June, so I wouldn't be able to do much in that time period. I would be available for task discussions/calls/messages. I will try to open and solve small issues in-between exams. So, I would try to do as much work as possible till 18th May and possibly we would be done with this issue till then.
Issue progress: #2307 contains checklist but some more points need to be added and discussed that's why I opened this issue. Most of Back-end for this feature is ready #2308.
Remaining Tasks:
_node_default.html.erb
and_node_meta.html.erb
to distinguish draft from normal notes as we do for first-timer posts (Solved in Submitting a draft #2747 )rich.html.erb
(Solved in Submitting a draft #2747 )notes/show.html.erb
(Solved in Add Draft Label to the research note if status = 3. Fixes #2678 #2682 )notes/show.html.erb
(Solved in Submitting a draft #2747 )I have tried to divide the issue in minimum part as possible, I can solve 2,4,5,6 and 7 in a single PR or multiple, but I see that some parts can be good FTO candidates like 2,3,5 and 7. What do you guys think, should I open FTO's or not ? Thanks.
The text was updated successfully, but these errors were encountered: