Linking to Zulip on the Discourse bottom banner

Hello, I recently noticed that we now have a bottom banner on Discourse with some links to the Julia twitter, youtube, github, stack overflow and Slack pages.

I was hoping to start a conversation about having the Julia Zulip community included in that list.

The Julia Zulip community is a chat platform that averages a bit over 100 active users per day and is used both as an open source Slack alternative, but also as a home for several Julia sub communities who depend on it’s support for inline LaTeX math and persistent message history. It’s mentioned on https://julialang.org/community/, so it’d be nice if could be included on the Discourse banner too.

There are dozens of us!

24 Likes

In case a negative, simplified version of the Zulip icon is needed, I just uploaded one to Wikimedia Commons :wink:

2 Likes

They’ve actually updated their logo away from that design:

Oh well… good thing I enjoy playing with SVG anyway :joy:

2 Likes

@mbauman

I actually looked into this when I threw that footer together — the only reason I didn’t add Zulip was because the theme component we’re using here (easy-footer) uses font-awesome 5 brand icons… and Zulip isn’t there. I don’t know how to use arbitrary SVGs… if someone can figure it out I’d be happy to add it.

3 Likes

Hm, I see, that’s. Perhaps one hacky option would be to (ab)use unicode? e.g. maybe there’s a unicode Z in an appropriate font that’s close enough. Any ideas @cormullion?

I think we can easily add custom CSS to each theme… which could allow us to define a custom zulip class for its SVG definition… I think. The FontAwesome names just end up as the link.className here:

So we just need a custom CSS class defined, right?

8 Likes

On a related note, you can upvote the Zulip icon on Font Awesome: https://github.com/FortAwesome/Font-Awesome/issues/16999

2 Likes

https://github.com/discourse/Discourse-easy-footer/blob/b70f0edc3961afa9179658a4e8aab3f838fd5cb0/settings.yml#L34 maybe

Bump. It would be great to get this added to the footer.

@mbauman @cormullion Looks like you might be close to figuring it out?

Not really, no. Looking back at my post above, the important thing isn’t the link.classname — it’s the link.icon. And I think that {{d-icon link.icon}} is an expander function expands it out to a hardcoded link into FontAwesome.

Hmm. If it’s hardcoded to be a FontAwesome icon, maybe we just pick a generic “chat” icon for now? E.g. https://fontawesome.com/icons/comments?style=regular

And then once https://github.com/FortAwesome/Font-Awesome/issues/16999 has been implemented, we can switch to the correct icon.

Good idea. Done.

5 Likes