# Discourse Upgrades

**URL:** <https://discourse.sourcecred.io/t/discourse-upgrades/383>\
**Category:** Site Feedback\
**Created:** [December 8, 2019, 4:06am UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383 "2019-12-08T04:06:36Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![burrrata](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/burrrata/32/135_2.png) [@burrrata](https://discourse.sourcecred.io/u/burrrata)\
**Post date:** [December 8, 2019, 4:06am UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/1 "2019-12-08T04:06:36Z")

</div>

> # Everything in this thread that has been implemented will be documented in the [SourceCred Discourse Admin Docs](https://discourse.sourcecred.io/t/sourcecred-discourse-admin-docs/399)

* * *
  

Since we use Discourse a lot, we might as well get the most out of it. Going through the [Discourse features](https://www.discourse.org/features) list to better understand what’s possible. Suggestions for improvement will be shared below for further discussion.

### Sources for ideas

- [Building a successful community on Discourse](https://meta.discourse.org/t/building-a-successful-community-on-discourse-toc/68504)
- [Discourse how to guides](https://meta.discourse.org/c/howto/10)
- [Discourse features page](https://www.discourse.org/features)
- [Discourse integrations page](https://discourse.org/integrations)
- [Discourse FAQ category](https://meta.discourse.org/c/howto/faq/)
- [Discourse moderation guide](https://meta.discourse.org/t/discourse-moderation-guide/63116)

### Inspiration for this work

(was going to call it an initiative, but it’s not quiet there yet lol)

- [Please help us organize this Discourse](https://discourse.sourcecred.io/t/please-help-organize-this-discourse/378)

---

<div class="post-metadata">

**Author:** ![burrrata](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/burrrata/32/135_2.png) [@burrrata](https://discourse.sourcecred.io/u/burrrata)\
**Post date:** [December 8, 2019, 4:23am UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/2 "2019-12-08T04:23:14Z")

</div>

# Ideas

* * *

## [Summarize this topic](https://www.discourse.org/features) button.

- Apparently it’s a thing. We should try it out.

## Polls

> **[How to Create Polls](https://meta.discourse.org/t/how-to-create-polls/77548)**
>
> Creating a poll The easiest way to create a poll is to use the poll builder. The poll builder can be accessed from the ⚙ in the topic composer, and allows you to make a poll without needing to know the exact syntax. Manually creating a poll To...

_Poll ([view on site](https://discourse.sourcecred.io/t/discourse-upgrades/383/2))_

## Custom Emojis

- Apparently this is an option

## Custom Banner

> **[Versatile Banner](https://meta.discourse.org/t/versatile-banner/109133)**
>
> This theme component is an evolution of the very popular Banner themes (and instructions for customizing them). The goal is to provide more ease and flexibility through the use of theme settings. Preview at Discourse Theme Creator Below is a...

## Embedding

- We could embed the SourceCred Discourse into the website. This would help us convert interested people into community members 🙂

## Integrations

> **[Discourse integrations](https://discourse.org/integrations)**
>
> Integrate your Discourse forum with your favorite apps and services.

## Questions, FAQs, and/or AQs (WIP)

~~We need to think through how to address the needs of different types of community members. In addition to the `Getting Started` category and guides, a `Help` or `Questions` category might help too.~~ Created a [Help](https://discourse.sourcecred.io/c/help/25) category 🙂

Could (maybe) even roll it as a Stack Overflow type thing where as people ask questions, if that question is common it gets added to an FAQ Artifact, and then they get Cred from asking a question and engaging with a common problem. I dunno how technically feasible that is atm, but encouraging people to engage, learn, and share knowledge is essential. Will create a post and/or [Initiative wish list](https://discourse.sourcecred.io/t/about-the-initiatives-wishlist-category/311) item to explore further.

The issue is, chronological ordering isn’t the best for such threads… you want to be able to see the best answers upfront. Maybe one approach would be to have askers ask a question according to template, the question is a wiki, and the template has slots for linking to + quoting from the accepted answers (maybe as determined by # of likes).

## Topic Templates

> **[What are Topic Templates?](https://meta.discourse.org/t/what-are-topic-templates/38295)**
>
> Topic templates are a useful tool to reinforce forum conventions or to guide new users. Category-specific topic template Some categories might follow a strict pattern. One such example would be a Movies category, wherein you’d like users to start...

## Boxes

> **[Displaying sub-categories in boxes](https://meta.discourse.org/t/displaying-sub-categories-in-boxes/59371)**
>
> There are two new ways to display a list of sub-categories within the parent category: in boxes with only the name, logo, and description in boxes with name, logo, and a list of some featured topics You can enable these styles by visiting the...

> **[howto](https://meta.discourse.org/c/howto/10)**
>
> Tutorial topics that describe how to set up, configure, or install Discourse using a specific platform or environment. Topics in this category may only be created by trust level 2 and up.

We have [our first boxes](https://discourse.sourcecred.io/c/the-credsperiment/13)!

## Themes

[Dark mode, image galleries, and more could be ours!](https://meta.discourse.org/t/beginners-guide-to-using-discourse-themes/91966)

## Anonymous posting?

- ~~Not sure if this would be a feature or a bug, but if we can allow people to post without first creating a profile that might A) lower friction in the onboarding flow, and B) make it easier for people to say what they really want without compromising their reputation (if that’s a thing people become concerned with)~~ As @Beanow pointed out [here](https://discourse.sourcecred.io/t/discourse-upgrades/383/6) this is not ideal for the SourceCred community right now.

## Badges

- Would be cool to leverage badges to make user profiles more fun and also informative to new users. For example, Discourse admins could have a badge, community engagement volunteers could have a badge, tech support volunteers could have a badge, etc… All of these players would get Cred for contributing so maybe they’re semi-volunteers? but you get the idea 🙂

## Solved Support Tickets

- Not sure if this is the intended usecase of this feature, but the Discourse [Solved](https://www.discourse.org/plugins/solved.html) integration allows users to post problems and then report when they’re solved. Could be great for community/tech help, esp for onboarding and supporting projects trying to learn about and deploy SourceCred for their communities.

## Pinned welcome thread wikis on every category

- As advertised.

### Team Building

- [https://meta.discourse.org/t/discourse-teambuild-run-your-own-team-building-activity/134907](https://meta.discourse.org/t/discourse-teambuild-run-your-own-team-building-activity/134907)

### Comments in website

Like [this](https://blog.codinghorror.com/welcome-to-the-internet-of-compromised-things/#discourse-comments). More info [here](https://meta.discourse.org/t/embedding-discourse-comments-via-javascript/31963).

  

## Homepage

Default View

- Could make default “homepage” view show categories rather than just new threads

Cool hompages

- [https://experts.feverbee.com/](https://experts.feverbee.com/)
- [https://community.effectiveremotework.com/](https://community.effectiveremotework.com/)

If we don’t go with the splash screen, then we should pin some threads

- welcome thread
- mega thread with all relevant SourceCred info

Questions:

- If Cred flows through the forum, but not the website, should we try to keep the website as simple as possible to get new users into the forum as fast as possible so that they can start engaging with the community and/or earning Cred?
- Speaking of, are we measuring views on pages/threads? Because if the forum is the main place for people to create and update information related to SourceCred, then we should give Cred for view too. For example, an FAQ list might not get a lot of engagement, but will definitely be useful. Measuring the amount of people that view it might help?

---

<div class="post-metadata">

**Author:** ![decentralion](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/decentralion/32/7_2.png) [@decentralion](https://discourse.sourcecred.io/u/decentralion)\
**Post date:** [December 8, 2019, 8:49pm UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/3 "2019-12-08T20:49:43Z")

</div>

> [@burrrata](#):
>
> - If Cred flows through the forum, but not the website, should we try to keep the website as simple as possible to get new users into the forum as fast as possible so that they can start engaging with the community and/or earning Cred?

In principle, cred for changes to the website get picked up too, both via GitHub cred measurements, and also by (future) initiatives describing the website.

I do think our [current website](https://sourcecred.io/) does too little to guide visitors towards understanding what SourceCred is all about.

> [@burrrata](#):
>
> - Speaking of, are we measuring views on pages/threads? Because if the forum is the main place for people to create and update information related to SourceCred, then we should give Cred for view too. For example, an FAQ list might not get a lot of engagement, but will definitely be useful. Measuring the amount of people that view it might help?

Discourse does record the view counts. Currently it’s not used in cred at all. I worry that it would be way too easy to write bots that anonymously pump the view counts for an attacker’s threads, and I can’t think of any way to detect or mitigate against this attack. Therefore, I don’t think we should use the view counts.

> [@burrrata](#):
>
> ### Badges

I like the idea of badges and achievements and such, but I’m not sure what kinds of badges we should have.

---

<div class="post-metadata">

**Author:** ![burrrata](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/burrrata/32/135_2.png) [@burrrata](https://discourse.sourcecred.io/u/burrrata)\
**Post date:** [December 9, 2019, 2:46am UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/4 "2019-12-09T02:46:18Z")

</div>

> [@decentralion](#):
>
> In principle, cred for changes to the website get picked up too, both via GitHub cred measurements, and also by (future) initiatives describing the website.

Right, but websites are static, so unless we’re tracking page views and click through rates there’s no way to know if an addition or change to the website is helpful or not. [Supernodes](https://discourse.sourcecred.io/t/supernodes-moving-past-raw-activity/340) might help with this, but that’s still very subjective.

Also, the point I was trying to make here was that when people (users) view the website they don’t earn or share cred as they do. If people engage on the forum, however, they’re immediately playing the SourceCred game. Then they’re learning about SourceCred, but also playing SourceCred. It’s in interactive learning experience. Seems like a (potentially) much better onboarding experience than a static website (if we can optimize it).

> [@decentralion](#):
>
> I do think our [current website](https://sourcecred.io/) does too little to guide visitors towards understanding what SourceCred is all about.

I would imagine that the main goal of the website is to A) provide high level information, B) help people deploy SourceCred (GitHub and docs), C) help people engage with the community (forum). Is that how you see it as well?

> [@decentralion](#):
>
> Discourse does record the view counts. Currently it’s not used in cred at all. I worry that it would be way too easy to write bots that anonymously pump the view counts for an attacker’s threads, and I can’t think of any way to detect or mitigate against this attack. Therefore, I don’t think we should use the view counts.

Might be able to ban bots, scraper, and automated scripts, but generally agree that the risk outweighs the reward in this case. Good call.

> [@decentralion](#):
>
> I like the idea of badges and achievements and such, but I’m not sure what kinds of badges we should have.

Same lol

Something fun would be ideal! Will keep brainstorming…

EDIT! Badge idea 🙂

> [@Please help us organize this Discourse](https://discourse.sourcecred.io/t/please-help-us-organize-this-discourse/378/13):
>
> > the Champion badge.
> 
> Yes! That would be great 🙂 Then you could see who’s actively working on stuff. That would A) be fun, B) maybe incentivize people to champion more stuff to get the cool badge, and C) it would raise awareness of championing for new users

---

<div class="post-metadata">

**Author:** ![decentralion](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/decentralion/32/7_2.png) [@decentralion](https://discourse.sourcecred.io/u/decentralion)\
**Post date:** [December 11, 2019, 3:12am UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/5 "2019-12-11T03:12:05Z")

</div>

> [@burrrata](#):
>
> I would imagine that the main goal of the website is to A) provide high level information, B) help people deploy SourceCred (GitHub and docs), C) help people engage with the community (forum). Is that how you see it as well?

Yeah, those seem like good goals for the website. 🙂 Honestly I haven’t thought about what role the website should be playing that much.

---

<div class="post-metadata">

**Author:** ![Beanow](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/beanow/32/98_2.png) [@Beanow](https://discourse.sourcecred.io/u/Beanow)\
**Post date:** [December 11, 2019, 1:45pm UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/6 "2019-12-11T13:45:00Z")

</div>

> [@burrrata](#):
>
> ### Anonymous posting?
> 
> - Not sure if this would be a feature or a bug, but if we can allow people to post without first creating a profile that might A) lower friction in the onboarding flow, and B) make it easier for people to say what they really want without compromising their reputation (if that’s a thing people become concerned with)

I think this harms transparency and attribution. So I think there needs to be a very strong use-case for this to be helpful I think. About B) people being able to speak more freely, I think there should be off-the-record channels available for this reason. But I don’t think it should be a large public stage, like the forums. I think having to stake your reputation to use the public stage is important to the health of that stage and the community as a whole.

Current off-the-record channels would be private messages on the forums, or direct messages on Discord.

---

<div class="post-metadata">

**Author:** ![burrrata](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/burrrata/32/135_2.png) [@burrrata](https://discourse.sourcecred.io/u/burrrata)\
**Post date:** [December 11, 2019, 2:44pm UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/7 "2019-12-11T14:44:43Z")

</div>

> [@Beanow](#):
>
> I think this harms transparency and attribution. So I think there needs to be a very strong use-case for this to be helpful I think. About B) people being able to speak more freely, I think there should be off-the-record channels available for this reason. But I don’t think it should be a large public stage, like the forums. I think having to stake your reputation to use the public stage is important to the health of that stage and the community as a whole.
> 
> Current off-the-record channels would be private messages on the forums, or direct messages on Discord.

Yeah good point. Anyone can sign up and use any pseudonym they want anyways. As such, the “freedom of speech” argument here was weak.

The onboarding ux flow argument is also weak because A) can’t flow Cred to an unregistered guest, and B) people can read without a profile, but if they want to play the game we need to flow Cred to their profile.

Overall, totally agree. Thanks for pointing this out 🙂

---

<div class="post-metadata">

**Author:** ![burrrata](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/burrrata/32/135_2.png) [@burrrata](https://discourse.sourcecred.io/u/burrrata)\
**Post date:** [December 12, 2019, 3:17am UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/8 "2019-12-12T03:17:28Z")

</div>

> [@decentralion](#):
>
> Yeah, those seem like good goals for the website. 🙂 Honestly I haven’t thought about what role the website should be playing that much.

Cool! Lots we can do to optimize this 🙂

One immediate idea would be to embed Discourse into the website as a main section of the website. This could help convert interested people into engaged community members. If we embedded the the [Help](https://discourse.sourcecred.io/t/about-the-help-category/408) category, then (I think) people who skimmed the website and wanted to learn more could immediately (after creating an account) start engaging with the community and asking questions.

---

<div class="post-metadata">

**Author:** ![decentralion](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/decentralion/32/7_2.png) [@decentralion](https://discourse.sourcecred.io/u/decentralion)\
**Post date:** [December 12, 2019, 5:06pm UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/9 "2019-12-12T17:06:44Z")

</div>

I like this idea. I think the Discourse is the strongest part of the project from a community/engagement perspective, so having the website leverage it makes sense to me.

The [website repo](https://github.com/sourcecred/website) lives here, if you feel like hacking on it I can do some upfront work in writing a proper README and adding some development instructions. (It’s a very shitty website, I hacked it together over the course of a weekend.)

---

<div class="post-metadata">

**Author:** ![burrrata](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/burrrata/32/135_2.png) [@burrrata](https://discourse.sourcecred.io/u/burrrata)\
**Post date:** [December 12, 2019, 10:28pm UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/10 "2019-12-12T22:28:20Z")

</div>

I too am a very poor web developer! lol

Looks like it’s mostly just basic React stuff right? If so, I should be able to noodle around on it to explore integrations. If I do, however, I’ll fork it first so that I can deploy a staging demo before merging into the master 🙂

---

<div class="post-metadata">

**Author:** ![burrrata](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/burrrata/32/135_2.png) [@burrrata](https://discourse.sourcecred.io/u/burrrata)\
**Post date:** [December 21, 2019, 2:11am UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/11 "2019-12-21T02:11:26Z")

</div>

> **[Easy responsive footer](https://meta.discourse.org/t/easy-responsive-footer/95818)**
>
> This is a theme component that will allow you to build a fully-responsive footer using nothing but plain text. Repository link https://github.com/discourse/Discourse-easy-footer Preview: ...

Done!

---

<div class="post-metadata">

**Author:** ![burrrata](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/burrrata/32/135_2.png) [@burrrata](https://discourse.sourcecred.io/u/burrrata)\
**Post date:** [December 21, 2019, 4:04am UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/12 "2019-12-21T04:04:00Z")

</div>

> [@decentralion](#):
>
> I like this idea. I think the Discourse is the strongest part of the project from a community/engagement perspective, so having the website leverage it makes sense to me.
> 
> The [website repo](https://github.com/sourcecred/website) lives here, if you feel like hacking on it I can do some upfront work in writing a proper README and adding some development instructions. (It’s a very shitty website, I hacked it together over the course of a weekend.)

Been exploring Discourse more and we can actually add headers, footers, splash sections, images, custom colors and boxes, backgrounds, fonts, etc… all the basic website things. Essentially, Discourse can be customized to become a mini website. Not sure if there’s a plan for the current website, but we could probably recreate all the components on the current website inside the Discourse homepage. If we could do that, would it maybe make sense to just make [sourcecred.io](http://sourcecred.io) the Discourse homepage?

- FTR [this site](https://theme-creator.discourse.org/latest) is 100% pure play Discourse goodness

Besides that it would just be awesome, this could also optimize engagement with the SourceCred community. Right now it’s mostly 5-10 people. If Twitter, the podcast, and our other outreach campaigns would link directly to the forum. People who hear about SourceCred would be one click away from engaging with the community. They would still see high level info on the website, but they could also ask questions and create a profile to start playing the SourceCred game right away! 🙂

---

<div class="post-metadata">

**Author:** ![decentralion](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/decentralion/32/7_2.png) [@decentralion](https://discourse.sourcecred.io/u/decentralion)\
**Post date:** [December 21, 2019, 8:32pm UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/13 "2019-12-21T20:32:53Z")

</div>

I like this idea! The one thing I’d miss from the current website is the cool animated SourceCred logo. But it’s not the most important. The site you linked is a compelling example in that it has all the splash-page stuff I’d expect, and then transitions into Discourse.

I’d like to get thoughts from some others (@s_ben, @wchargin, @Beanow) on this change. And we’d need someone to champion it. But I’m definitely open to it.

---

<div class="post-metadata">

**Author:** ![burrrata](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/burrrata/32/135_2.png) [@burrrata](https://discourse.sourcecred.io/u/burrrata)\
**Post date:** [December 21, 2019, 9:13pm UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/14 "2019-12-21T21:13:55Z")

</div>

I’d be happy to champion the initiative. Also, may or may not be able to include a cool animated logo 🙂 What would be really great though… and I’m not sure how to do this yet… would be if we could have the SourceCred graph as the main splash screen so every time you open Discourse you see the latest snapshot on the homepage. That would really drive home that A) this game is live and working, B) you can play right now by contributing to the community, and C) SouceCred is awesome!

---

<div class="post-metadata">

**Author:** ![burrrata](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/burrrata/32/135_2.png) [@burrrata](https://discourse.sourcecred.io/u/burrrata)\
**Post date:** [December 21, 2019, 9:14pm UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/15 "2019-12-21T21:14:53Z")

</div>

Oh and btw, I added a footer, some header links, and some other stuff to see how it looks. I’m still just experimenting with everything, however, so if anyone has suggestions for improvement please share 🙂

---

<div class="post-metadata">

**Author:** ![decentralion](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/decentralion/32/7_2.png) [@decentralion](https://discourse.sourcecred.io/u/decentralion)\
**Post date:** [December 21, 2019, 9:15pm UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/16 "2019-12-21T21:15:13Z")

</div>

> [@burrrata](#):
>
> would be if we could have the SourceCred graph as the main splash screen so every time you open Discourse you see the latest snapshot on the homepage.

That would be really cool. Seems technically feasible, we could have every cred update push a new asset to GitHub which we then load on the forum. Probably not a v0 feature though.

Here’s a request: can we change the color on the footer? When it’s white it’s so different from the rest of the site that it stands out in a bad way, IMO.

 ![image](https://canada1.discourse-cdn.com/flex032/uploads/sourcecred1/original/1X/4f7a50505f0d0a553f819b7f1d3e9d6b9c95ab90.png)

---

<div class="post-metadata">

**Author:** ![burrrata](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/burrrata/32/135_2.png) [@burrrata](https://discourse.sourcecred.io/u/burrrata)\
**Post date:** [December 21, 2019, 9:16pm UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/17 "2019-12-21T21:16:54Z")

</div>

> [@decentralion](#):
>
> Here’s a request: can we change the color on the footer? When it’s white it’s so different from the rest of the site that it stands out in a bad way, IMO.

Totally! Thanks for the feedback 🙂 I actually have a dark mode extension that makes it dark for me so I was totally unaware that was happening. Will look into fixing that

EDIT: went into the CSS of the plugin and it was set to make the footer the opposite of the main page for contrast. Changed it so that they’re the same. Doesn’t feel like a “real” footer (doesn’t stand out), but at least now it’s not blinding us as night lol

EDIT 2: got it set so that it’s a different color than the main background, but still similar. Is that better?

EDIT 3: changed the header to match the footer. Are we happy with that, or is it weird?

EDIT 4: so the light and dark themes both looked great, but the neutral theme was being difficult. TBH I’m not even sure what “neutral” means in the context of a theme. To keep things simple made dark the default theme with light as an option users can self select in the hamburger menu.

---

<div class="post-metadata">

**Author:** ![burrrata](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/burrrata/32/135_2.png) [@burrrata](https://discourse.sourcecred.io/u/burrrata)\
**Post date:** [December 21, 2019, 11:20pm UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/19 "2019-12-21T23:20:29Z")

</div>

> **[Discourse Button Styles](https://meta.discourse.org/t/discourse-button-styles/88154)**
>
> This theme component includes basic settings for changing button colors without writing CSS. Github repo: https://github.com/awesomerobot/discourse-button-styles Installation: How do I install a Theme or Theme Component? Preview: Example of what...

Added rounded buttons. Are we happy with this?

---

<div class="post-metadata">

**Author:** ![burrrata](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/burrrata/32/135_2.png) [@burrrata](https://discourse.sourcecred.io/u/burrrata)\
**Post date:** [December 22, 2019, 12:05am UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/20 "2019-12-22T00:05:01Z")

</div>

> **[Banner themes (and instructions for customizing them)](https://meta.discourse.org/t/banner-themes-and-instructions-for-customizing-them/82368)**
>
> 📢 ⚠ A new theme component based on this theme has been released, see Versatile Banner. It will be much simpler to configure and maintain because it uses the theme settings introduced immediately after the release of this theme. I invite you to update...

> **[Versatile Banner](https://meta.discourse.org/t/versatile-banner/109133)**
>
> This theme component is an evolution of the very popular Banner themes (and instructions for customizing them). The goal is to provide more ease and flexibility through the use of theme settings. Preview at Discourse Theme Creator Below is a...

  

Really we want something like this with multiple sections you can scroll through:

> **[Discourse Theme Creator](https://theme-creator.discourse.org/)**
>
> Demonstration sandbox for Discourse

---

<div class="post-metadata">

**Author:** ![burrrata](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/burrrata/32/135_2.png) [@burrrata](https://discourse.sourcecred.io/u/burrrata)\
**Post date:** [December 22, 2019, 12:59am UTC](https://discourse.sourcecred.io/t/discourse-upgrades/383/21 "2019-12-22T00:59:59Z")

</div>

> [@decentralion](#):
>
> That would be really cool. Seems technically feasible, we could have every cred update push a new asset to GitHub which we then load on the forum. Probably not a v0 feature though.

Manually took a snapshot and uploaded the image as a background for the homepage. Will either find a better homepage banner and/or manually update the snapshot every few days. If/when we get a server to regularly run the protocol and create a new snapshot we can just point the image to that snapshot 🙂

[Next page](https://discourse.sourcecred.io/t/discourse-upgrades/383.md?page=2)
