This is part 2 of the issue #4117
Currently, if a user get a non-existing page, they get a message saying "Report a bug or issue" in the footer, which isn't welcoming for non-developer users and is hard to notice.
We need to add a button which says " Report the Issue" instead of the link which may seem too toned down. Make an attractive button linking to this page https://github.com/publiclab/plots2/issues/new
Here is the template : https://github.com/publiclab/plots2/blob/dd18e979e619005c28254fd129852602e0279dd7/app/views/dashboard/dashboard.html.erb#L6
https://publiclab.org/wiki/issues
@jywarren @publiclab/reviewers Please add label "fto only" and "gci-candidate".
A little confused, description says 'fto' but label says 'fto-candidate'. Does more work need to be done to make it fto friendly? Or is the 'fto-candidate' label incorrect?
Hi @dave-light, I just edited the issue body. And, yes fto-candidate
label was added without checking the issue body creating confusion.
It can be made FTO issue by adding links or diff of changes to be done. Currently, its fto-candidate as it can be further simplified.
Thanks!
@gauravano If it's not an FTO I'd love to work on this? I've made one contribution to publiclab so far but if you'd rather it was left for someone else I'll understand. I currently have one other issue I'm working on.
@gauravano @dave-light @CodeSarthak I will make an FTO out of this
I turned it into a button in Chrome Dev Tools and i'm sure I can transfer that into the code repo by just referencing the class "pl-content wiki" but how can I open an FTO for the issues wiki if it is not available in the localhost testing environment? The person will not be able to see their changes.
OK thanks
@SidharthBansal please help answer my comment above yours
Hi @dave-light, sorry for missing your comment earlier. Just trying to get the goal of this issue. Our current page looks this
Do we just want to change the button text? @dave-light @CodeSarthak @sashadev-sky
OK, I got here - https://publiclab.org/wiki/issues from the footer link. I saw 2 methods listed for reporting issue one via GitHub and another posting a question at publiclab.org
I guess, we want to change the GitHub one a button. Am I right?
Hello @gauravano
Hi @dave-light, sorry for missing your comment earlier.
No worries
I guess, we want to change the GitHub one a button. Am I right?
Yes, that's what I understood.
@dave-light @gauravano I managed to change it to a button in Chrome Dev Tools and I can transfer the code to the DB I just am confused how I would see this change outside of Chrome Dev Tools if this is not a page available in the testing environment.
How do people usually make changes in a scenario like this? Do they just try to recreate that part of the page locally? Sorry I think I am fundamentally confused about something here.
The page we are talking about is a wiki page, which is just a post saved in
production database. Just like our accounts on GitHub, or our comments
here. The wiki is made by different people working together, so anyone who
have conyributed some posts to PublicLab can edit the wiki. You can check
whether you are allowed to edit or not. Or, I can edit the wiki to convert
that link to a button?
Give it a try and let me know, what response you get. Thanks!
On Fri 18 Jan, 2019, 7:18 AM Sasha Boginsky <[email protected] wrote:
@dave-light https://github.com/dave-light @gauravano
https://github.com/gauravano I managed to change it to a button in
Chrome Dev Tools and I can transfer the code to the DB I just am confused
how I would see this change outside of Chrome Dev Tools if this is not a
page available in the testing environment.How do people usually make changes in a scenario like this? Do they just
try to recreate that part of the page locally? Sorry I think I am
fundamentally confused about something here.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/publiclab/plots2/issues/4251#issuecomment-455397987,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT6S9q5039iDLprC6HaWNDw_Wl1RecMnks5vESf3gaJpZM4ZLKAj
.
@gauravano Thank you! I didn't know that wikis worked that way. I think I have had tunnel vision with the Github side of things. I can't edit yet because I have not contributed to any posts on the site, so you may have to edit it or @dave-light. Are code contributors encouraged to just create pages about anything they feel is relevant?
Also this is not meant to be an fto-candidate in this case right?
@sashadev-sky code contributors create research notes and wikis regarding new features, integrations, their work and relevant exciting things there. Questions regarding interesting ideas, GSoC proposals and many things are posted at publiclab.org. As wiki is a page which is created by collaboration of multiple users and not all contributors come to website with legitimate purpose so for preventing spam these guidelines are set.
I will convert it to button. What text you all think would be nice for the button(keeping style same as Report an issue button)? Thanks!
@gauravano I’ll definitely look through them more and consider making my own posts. I saw your post on India, I liked it!
For button I think same button as the one below it would make sense
Changes done! Looks good?
Closing this issue as @gauravano has fixed it
Most helpful comment
Changes done! Looks good?