Skip to content
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

Suggestions for new questions page #6323

Open
steviepubliclab opened this issue Sep 23, 2019 · 12 comments
Open

Suggestions for new questions page #6323

steviepubliclab opened this issue Sep 23, 2019 · 12 comments
Labels
break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration feature explains that the issue is to add a new feature planning Planning issues!

Comments

@steviepubliclab
Copy link
Contributor

Hello! I'm looking at the new draft for the /questions page (https://publiclab.org/questions_shadow) and wanted to start a thread for suggestions on it.

  1. I'm interested in seeing the need for "questions:___" to come out of the tag line. I'm wondering if we can change the system here so any regular tags added to the /questions page get this power tag on the back end rather than having this something the user needs to do or see. I think it's a little confusing and a lot of people don't know to do this tagging as a power tag as it stands.

  2. I'm confused if this new interface would be at /questions or if it would show up when you type in your question and click continue (see current /questions page). If the new interface doesn't show current/recent questions, where would one go to see them?

  3. Where would people to go view questions by topics? I think this is a useful part of the current page.

  4. I'm curious why we are directing people to draft in a two page process? First users ask their question, then for myself I'm expecting it to post, but instead it directs me to another page that asks me to fill in more information. I'm curious about the design decision behind having this spread over two pages.

Think that's it for now! Thanks all!

@steviepubliclab steviepubliclab added the feature explains that the issue is to add a new feature label Sep 23, 2019
@jywarren
Copy link
Member

jywarren commented Sep 23, 2019 via email

@jywarren
Copy link
Member

Re: topics, that section seems not to have made it into this version but it's supposed to be there from the mockup:

Screen Shot 2019-09-23 at 4 02 57 PM

Zoomed in:

image

Let me get that fixed!

@jywarren
Copy link
Member

Actually i see that in the original design, clicking soil would open a tag card that displays a list of soil questions. What do you think of that @steviepubliclab ? We went over this a million years ago so I had totally forgotten this little "switcher" but it shouldn't be too hard to generate.

@jywarren
Copy link
Member

Here it is updated to the latest style guide:

image

@jywarren
Copy link
Member

jywarren commented Sep 23, 2019

The code that drives this is here; currently it's set up to show just "recent questions" instead of questions by topic:

<div class="RecentQuestions col-md-12">
<span class="d-none d-lg-inline"><h2>Recent questions </h2></span>
</div>
<%= render partial: "questions/recent_questions_shadow" %>

Also: the "feature questions" are currently just popular ones, i think. They can be rewired to show questions bearing the tag featured:question here:

@popularquestions = filter_questions_by_tag(@questions, params[:tagnames])
.order('views DESC')
.limit(20)

@jywarren
Copy link
Member

Finally, regarding your first point, @steviepubliclab - do you mean, you'd like question:general to be removed from the form, here?

image

@steviepubliclab
Copy link
Contributor Author

for 1- yes, but I actually I think I meant something more complicated than this. Like if someone's working in the questions form, can we take the power tags out and have the system added it on the the back end -- so people would just add regular tags and they would turn into the power tags whenever you're submitting from the questions template. I think people don't realize they need to do "question:topic" to mark something as a question rather than a normal research note.

2- I think it's important people can come to this page to see, and search for questions. This isn't just an asking interface it's also our best Answering interface. If we don't make that part easy, I think people will be less inclined to answer questions

3- ok great by topic is good, but what if they're topic of interest isn't listed? goes to point 2 a bit.

@jywarren
Copy link
Member

jywarren commented Nov 26, 2019

Thanks Stevie, sorry, catching up here. In particular, you mentioned "search for questions" -- do you think this page must have a search box? Just clarifying, thanks!

OK, so breaking out some to-dos:

@jywarren jywarren added break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration planning Planning issues! labels Nov 26, 2019
@steviepubliclab
Copy link
Contributor Author

Hi Jeff,
I think viewing questions by topic is helpful, but it doesn't help us with duplication. A search feature could help with this.
-Stevie

@jywarren
Copy link
Member

Thanks - sorry, what did you mean by "duplication"?

@steviepubliclab
Copy link
Contributor Author

by duplication I just mean people posting the same or similar questions.

@jywarren
Copy link
Member

jywarren commented Dec 3, 2019

Ah i see - and yeah, we can also try to do better on finding "similar posts" as you type yours, to reduce duplication as wel - we actually had that, but turned that feature off because it was causing site slowdowns :-(

image

@stale stale bot added the stale label Oct 7, 2020
@publiclab publiclab deleted a comment from stale bot Oct 8, 2020
@stale stale bot removed the stale label Oct 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration feature explains that the issue is to add a new feature planning Planning issues!
Projects
None yet
Development

No branches or pull requests

2 participants