/many: Each page should have a quick explainer at the top

[bryceerobertson]

No description provided.

[bryceerobertson]

Could simply be a replica of the description in the menu.

[melissasamworth]

@ricewithabee I think I agree, but could you give some more reasons and evidence for? Bonus if you include dogfooding or direct anecdotes from users

[bryceerobertson]

My argument would be that we have descriptions in the menu at the moment because we've identified that people need brief explainers on what each page is about, but what if they come to a page from somewhere other than the menu e.g. Google or a shared link?
I also think the menu items shouldn't have descriptions (addressed in a separate issue), which would make the descriptions on the page their replacement.

[bryceerobertson]

My dogfood (I think?): when I was looking at the Projects page for example, I wanted to remind myself what exactly these projects were about. In order to find out, I had to open the menu.

[bryceerobertson]

Update: maybe it's good for some e.g. /projects. Bryce will test it out on /projects.

[bryceerobertson]

@melissasamworth @soerenelverlin I've added the text to /projects. What do you think? Should we try something similar on other pages?

[melissasamworth]

@melissasamworth @soerenelverlin I've added the text to /projects. What do you think? Should we try something similar on other pages?

@bryceerobertson I definitely like it on projects. I could go either way with the other pages.

[bryceerobertson]

One datapoint is that someone at EAGxNordic didn't like the resources much until Søren explained them a bit more. We can discuss on Friday.

[melissasamworth]

I do kind of like this idea. Add to the feature ideas doc

[bryceerobertson]

Done

[bryceerobertson]

For /courses: explain that this is just for self-led learning and facilitated courses can be found at /events-and-training.