I’m a designer on the Discourse team, and I’ve spent some time this week building a theme to get things feeling a bit more Embery.
I’ve just enabled it as the default here. If you notice any issues or have any feedback let me know.
I’m a designer on the Discourse team, and I’ve spent some time this week building a theme to get things feeling a bit more Embery.
I’ve just enabled it as the default here. If you notice any issues or have any feedback let me know.
It is looking good!
The one thing that I noticed that looked weird is the login buttons (social networks).
Thanks for working on this!
Thank you, @awesomerobot, it looks slick!
I’m really digging it, thanks for working on this @awesomerobot!
Love the new theme, really stands out among the other Discourse forums I’m in.
Pretty minor, but I noticed the buttons have a tendency to blink rapidly upon mouse-over:
Great work @awesomerobot!
The other day I was reading a post on Elm’s discourse form and really liked the readability of their theme. I wanted to float some suggestions out there and see if they resonate with you/our community.
Here’s a screenshot from an example post over there:
And here’s a post from Ember’s forum:
Some thoughts:
Testing
tag; the bright orange slider for paginatingAnd here’s a screenshot after making a few tweaks:
Here’s the CSS code for the tweaks:
html {
font-size: 15px;
}
#topic-title h1 {
font-size: 1.6511em
margin: 0 0 6px 0;
}
a.badge-wrapper {
font-size: .8em;
text-transform: uppercase;
}
a.badge-wrapper.box {
padding: 2px 10px;
}
.badge-wrapper.box span.badge-category-bg,
.badge-wrapper.box span.badge-category-parent-bg {
border-radius: 2px;
}
.cooked p, .d-editor-preview p {
line-height: 1.4;
}
.cooked pre code,
.cooked p>code,
.cooked li>code,
.cooked pre>code,
.d-editor-preview pre code,
.d-editor-preview p>code,
.d-editor-preview li>code,
.d-editor-preview pre>code {
background: #f7f7f7;
}
code, pre {
font-size: 0.94em;
}
.cooked, .d-editor-preview {
line-height: 1.5;
}
This next rule I just removed to lighten the text of the author name, post date, and paginator elements:
.names span a, .topic-body .reply-to-tab, .topic-meta-data .post-info a, .timeline-container .topic-timeline .start-date, .timeline-container .topic-timeline .now-date, .topic-list th, #reply-control .reply-to, #reply-control .reply-to i, .latest-topic-list .table-heading, .top-topic-list .table-heading, .group-nav li a, .group-nav li i, .user-navigation .nav-stacked a, .user-nav li a {
- color: #444;
}
This darkened the borders which also pulled attention away from the content a bit, so I removed it to lighten them:
.topic-body, .topic-avatar, .embedded-posts.bottom .row .topic-avatar, .embedded-posts.bottom .row .topic-body, .embedded-posts, .embedded-posts.top .row .topic-avatar, .embedded-posts.top .row .topic-body, .small-action, .timeline-container .topic-timeline .timeline-scrollarea, .category-list tbody tr, .latest-topic-list-item, .category-list tbody tr:first-of-type, .latest-topic-list .table-heading, .top-topic-list .table-heading, .user-main .about .secondary, .nav-stacked li, .content-list ul li, .post-links-container .post-links {
- border-color: #E5DBD6;
}
I have some more ideas for the overview page (I think the way Elm handles the topic labels with a small colored box instead of a full-color background is good) but figured I’d start out with this and put it out there.
What do y’all think?
Really nice!
I would avoid uppercasing all category/badge names and leave them as they’re entered.
And a small vote to revert the header from orange background to white. It takes a lot of focus.
@samselikoff, I definitely agree with these thoughts.
I sent some feedback along about the buttons privately, but I’ll post theme here was so it’s part of the public dialog:
My suggestions would be:
btn-text
, btn-icon-text
and pills
background: rgba(224, 78, 57, 0.10); color: #c7341f;
topic-map
container is a little lowHere is a screenshot of some of those changes:
Nice
Does anyone know where the CSS for our site is kept, if it’s OSS, if we can make PRs to it, etc.?
From what I saw of other discourse theme-builder stuff it’s behind the admin of our site and kept in the db (or something). I could be completely wrong.
@awesomerobot, what would be the best way to get changes made?
Thanks for the feedback everyone. I think there are some good suggestions here.
Very good question. The theme was living in the admin section of this site, but I moved it to a repo on github so anyone can feel free to make a PR.
I’ll be around to help maintain the theme and fix bugs, but for iterative style changes submitting a PR will be the quickest way to get them implemented.
Also, if you have questions about how themes in Discourse work - this is a good place to start:
Would it be possible to get the forums logo to show up when you save it to your phones home screen? I have a few different forums saved to my homescreen (all discourse apps) and the ember forum is the only one missing a logo.
The logo showed up on my phone this morning. Now it looks the best of the bunch
Oh yes, I updated it and completely forgot to let you know. Thanks for mentioning it.
Thanks for this!
Is it possible for me to use the theme locally, so I can test my changes before submitting PRs?
There are a couple of options to test themes:
hey @awesomerobot, thanks very much for your work on the theme update. Would it be possible to move that repo to something our community can update on our own over time? We’re glad you’re around to help out right now, but we also find that over a period of a few years it’s easy to lose track of who has access to what (especially if you end up taking a different job)
Thanks!
Oh sure, that does make the most sense — I just requested to transfer the repo to you