FWIW, the current links don’t really look right on mobile. The top logo, Ansible, and Chat are a bit squished together. I think a footer is indeed a better choice.
I’m torn on that @cybette - part of me says yes link-all-the-things; part of me thinks that Spaces still aren’t perfect and people will find the Matrix rooms as they get involved in a given project. Happy to go with what others think
I think having a quick way in the top to go back to the home page is important. A lot of forums miss that part and people end fighting the interface to return to the site.
I don’t like the current setup, but I definitly think we need something that makes it easy to go to Ansible Community | Ansible.com (and ansible.com in the future) up there.
I do agree on the footer (which can be extended), but I still think we need a top nav.
Elastic is using icons instead of words, which is not great either, but does look better:
I would point to the social room, and we can direct them from there. Most (new) people seem confused about the “spaces” concept.
So currently we’re using Custom Header Links which only supports text links.
I also tried Brand Header but that adds a bar above the existing header which felt awful, tbh.
Custom Header Links (icons) might be OK? it’s icons only which is fine if you just want to put a linking back to the website, but it’s not super obvious/intuitive.
My thought was /community because this is the community forum, with a tooltip that reads “Ansible Community Home”. Are we getting a link to the forum from ansible.com homepage? if we are, then it’s ok to have it go there.
We’ll be getting a link from the community page, so I think it makes sense to have it link back there instead of ansible.com, at least for the time being.
I like it, Single color simplifies it.
It looks a bit smaller than before or maybe that’s just me, but looking good!
woohooo!
Looking at Fedora, maybe we can use the logo mark AND the wordmark like them? That might look better and will help people to associate both marks
And for the text, go with “Automation powered by community” like in Ansible Community | Ansible.com, instead of the “radically simple…” to keep it consistent and community centred? We haven’t gotten back to the mission and all that, but for this particular case feels better.