As discourse becomes more and more popular, I increasingly find myself teleported to sone discourse forum via some link. And one of the first things I usually want to know is: Where am I? What is this forum about? And unless the site admins have done an exceptionally good job in formulating the essence of their site in a single sentence in site description (which is shown on the About page), it’s often not that easy to really understand what that forum is about.
How about adding a long site description field to the site settings and show it on the About page?
LOL, well, what I had in mind was not so much that the site description doesn’t get filled out (in my experience it usually does) but that it’s shortness is often not enough to convey what the forum really is about, especially when it’s something innovative/uncommon. For two reasons:
It requires some thinking to boil down the essence of your seite into one sentence.
If the site owner comes up with something decent, chances are that it’s more of a slogan than an actual description.
But even if the problem were that the short field doesn’t get filled out (or in a useless way), I would indeed think that there is at least a chance that the long field would get filled out. It’s so much easier to describe your seite in many words than to come up with an elevator pitch.
Any chance of getting the site description field to support HTML or at least weblinks? I figured the description on the about page would be a good place to link my users back to meta.discourse.org if they’re curious about the software
I’ll stick the link on the FAQ page for now. I think the nicest long term solution would probably be to add a similar “About” topic to the Staff category of new installations and insert the text into a section of the About page, the same way it’s done with the FAQ, TOS and Privacy Policy system-created topics.
The reason this happens is because the example is a bit old now. The template has changed in Discourse and so the snippet in my post is outdated (because it was based on the old template)
This is the main reason why we don’t recommend full template overrides, they require maintenance.
I’ve deleted the old post to prevent any further confusion about this.
The good news is that one of the changes made to that template recently introduces a new plugin-outlet that serves the same purpose.