blog

archives

Apr

12

2 weeks ago

A brand new discourse.org

Erlend Sogge Heggen

This week we unveiled a completely revamped discourse.org! When our original website was first launched in 2013, Discourse’s features were quite novel. Concepts like “infinite scrolling”, “dynamic notifications” and “mobile-friendly” were state of the art for open source community platforms, especially stuck-in-90s era forum software. Now these features are taken for granted, as they should be. That doesn’t mean we’ve stopped innovating; just look at our latest v1.7 release. But we no longer have to convince people that Discourse is modern, hip – dare I say radical – and keeping with the times. That’s a […]

Read more...

Notable Replies

  1. For anyone who spends more than a few minutes to look at discourse.org it is clear that you can self host Discourse for free.

    People who aren't willing to devote those few minutes to evaluate Discourse as a forum platform on the basis of it's strengths are also pretty likely to skip or ignore the minimum requirements and standard install instructions, but nonetheless post support questions on meta. This is a waste of time for Discourse's support team. (Who, by the way, do an excellent job, regardless of if the user asking a question is a paying customer, or a non paying "consumer").

  2. I still do feel that you should include a "free" pane on your plans page or put back the "or install it yourself" link next to the "View plans" button on the call to action, at the very least. I'm not completely knowledgeable with programming stuff and I tend to skim a bit, so it took me quite a bit to see where the free version of your software was on your site.

    Also, I feel if you guys want to grow as a more popular piece of forum software -- you have to appeal to everyone. You should probably link directly to the install guide on GitHub, as well as to the GitHub repo itself.

    Finally, I still feel you guys should at least mention some of your forum's biggest features -- such as infinite pagination, Markdown, and notifications -- in text form somewhere near the bottom of the page, instead of just being on a separate page. Take Flarum's site for instance. They do a good job of quickly advertising their features with a simple scroller in the middle of the page (near the "Learn more about Flarum's features" button).

    Sorry if I'm sounding nitpicky, I'm just a staunch believer that good UX can make all the difference.

  3. Remah says:

    I am distinctly underwhelmed by the new discourse.org. Not for the same reasons as other users but sometimes orbiting around similar issues.

    On the positive side, Discourse should be defined by what it is and who you are - I could easily say "who we are" given the strong sense of community. So please don't waste your time looking at WordPress, Flarum or whatever. There are logical pitfalls in doing so. For example, free WordPress is an integrated service provided by Wordpress.com whereas free Discourse is not.

    Some issues and unanswered questions

    I've chosen three main issues and added questions for each - I've made an effort to be clear but I am watching sports games at the same time.

    • The home page lacks a passionate pitch.
      Q. How to instil a sense of passion and stronger direction?

    • Free Discourse should be ABC.
      Q. How to clarify access to the free DIY option?

    • Discourse doesn't need everyone.
      Q. How to assist prospective users to self-select?

    Some suggestions

    The home page lacks a passionate pitch so How to instil a sense of passion and stronger direction?

    I feel that the home page lacks passion because it doesn't strongly suggest either action or clearly present problems resolved. Discourse.org so clearly represented passion that I committed to it before having any need for it. Perhaps I need to let go of this but I don't think so.

    From @erlend_sh's blog entry, both early and late goals are presented but I don't see either realised.

    Initially:

    What problem can Discourse solve for YOU?

    Later:

    We ultimately settled on three “pillars”:
    1. Emails don’t scale.
    2. Problem solving is best done in public.
    3. Communities ought to be owned by their creators.

    The structure and text simply doesn't make it clear. Instead I read three out of four as warm fuzzies:

    • "your team"
    • problem of "email silos"
    • "solutions together"
    • "your community"

    Also the term "email silo" is relatively obscure - do a search to see - which is why I would leave it out. It is one step too far beyond more easily understood terms.

    Free Discourse should be ABC so How to ease access to the free DIY option?

    At a very basic level, the issue of paid versus free is confusing because free includes three very different concepts:

    • free trials
    • open source licencing
    • self-managed installs on a non-Discourse host

    Then there is the issue of using different language/imagery/concepts on different pages. I'd prefer to see basic and consistent descriptions repeated across various pages so less educated visitors can clearly make the right connection the first time they encounter each instance. For example:

    • Managed hosting seems less helpful than official Discourse hosting
    • Fork us on GitHub is cryptic compared with install Discourse yourself in the cloud. But confusion also arises because neither mention that you need to get your own host.

    Here's a table quoting the text on the various pages for the four topics I've mentioned. The situation gets even more unclear with Digital Ocean and community installs added to the mix.

    On web page Paid Free trial Free install Free licence
    www.discourse.org Managed hosting Start your free trial Fork us on GitHub an open source project
    .../about official Discourse hosting Start a free trial install Discourse yourself in the cloud Uncompromisingly open source, etc.
    .../features ? ? ? 100% open source
    .../pricing .../buy hosted Free 14 day trial self-install ?

    I do like the etc. on the about page:

    There is only one version of Discourse – the awesome open source version. There’s no super secret special paid commercial version with better or more complete features. Because Discourse is 100% open source, now and forever, it belongs to you as much as it belongs to us. That’s how community works.

    Discourse doesn't need everyone so How to assist prospective users to self-select?

    Discourse shouldn't appeal to everyone because everyone doesn't want or need Discourse. We should also remember that Discourse is represented by the quality and effectiveness of its installs.

    • Select whether I really have a useful need for Discourse.
    • Select the most appropriate Discourse implementation including the no Discourse option.

    The best example of self-selection that I can think of is clarifying the "free" use issue above. Other examples would be show-stoppers that are disappointments when revealed or confirmed in the forum:

    • hosting requirements that trip people up, i.e. versions of Linux, Docker, etc.
    • clarifying supported versus unsupported installs
    • cutting out those unprepared to leave behind traditional tools like PHP and mySQL
  4. The home page had a slightly different layout originally, it said "Are you a developer?" as the heading there. I removed it to simplify the layout. So the idea wasn't that you'd be an average user installing Discourse, you would be highly technical, a developer.

    I'm not a huge fan of the "fork us" GitHub joke thing, so it could be changed:

    Discourse is 100% free, open source software. Forever.

    Fork us on github

    to

    Discourse is 100% free, open source software. Forever.

    Install from GitHub

    Audience is a bit different though, developers, it could cover both. The fork thing is a bit too clever-clever anyways.

    Also note the buy page has the what if none of these plans fit my budget info right under it... plus info on the educational and non-profit discounts.

  5. Linking "100% free and open source software" to github.com/discourse/discourse makes sense. What about also making the second sentence read:

    You can install it yourself on your own server, or for a flat one-time fee of $99, a trusted member of the Discourse community can install Discourse in the cloud for you.

    ?

  6. Point of order: i can't code my way out of a wet paper bag and I've never been a developer at all in my entire life, but I am a pretty handy sysadmin—and that's why I wanted to self-host. Not to hack on the code (I leave that to folks who can do it without curling into the fetal position, which is what I end up doing), but to have the pleasure of hosting a community my way and on a server I already pay for.

    So, cloaking the download behind "Are you a developer?" is a little sideways, imo, just because developer != admin (and, much love to the devs I've worked with professionally, but most of them are sucktastically awful at anything resembling operations or security, at least as it applies to big-picture best practices in a multi-tenant, multi-application environment).

    However, that being said, "Install from Github" is perfect. That avoids the "what if i'm not a developer but i want to self-host?" question.

    tl;dr: the bikeshed should be purple

Continue the discussion meta.discourse.org

24 more replies

Participants

Mar

11

1 month ago

Moving from Facebook Groups to Discourse

Erlend Sogge Heggen

The following is a guest post by Martin Eriksson @meriksson On January 4th 2017, the news aggregation site cor.ax completed its migration from private Facebook Groups to a private Discourse community. Why the move? We used to have about 20 Facebook groups for people involved in a network of alternative media projects. Some of the groups were dedicated to editorial discussions, some were general discussion groups for our paying members, some were interest groups about financial issues, gaming, cultural topics etc. We started using Facebook since it was very easy […]

Read more...

Start the discussion at meta.discourse.org

Mar

6

2 months ago

Discourse API Documentation Released!

Blake Erickson

Today we would like to announce our much anticipated Official API Docs! You can find them at: http://docs.discourse.org Today, more than ever, an application needs to be able to integrate with other applications and the Discourse API allows you to easily integrate your Discourse forum with any other application. We do have a Ruby based API client, but your company or server might not support Ruby, so our documentation can easily be used to write an integration in any programming language through simple HTTP REST calls. To aid in integrating […]

Read more...

Notable Replies

  1. Already nostalgic for the old "documentation"!

    :sweat_smile::sweat_smile::pizza:

  2. That is still useful if you want to know exactly what API calls are needed for a particular UI action!

Continue the discussion meta.discourse.org

Participants

Feb

28

2 months ago

Summer of Code 2017

Erlend Sogge Heggen

This summer, Discourse will be participating in three different “summer of code” projects! Google Summer of Code 2017 First of all, we’re happy to announce that we’ve been accepted into Google Summer of Code for the 2nd time in a row. Official Profile Ideas List Application Guide Rails Girls Summer of Code 2017 As per usual (this is our 4th go) we’ll also be participating in RGSoC. That process is run entirely on RGSoC’s end, so please see their website for more information. railsgirlssummerofcode.org Outreachy 2017 (May) We’re very excited […]

Read more...

Start the discussion at meta.discourse.org

Feb

16

2 months ago

The Discourse Encouragement Fund

Erlend Sogge Heggen

For almost a year now, we’ve been doing something that’s considered quite risky for an open source project: Paying contributors. Communities like ours are fundamentally built on intrinsic motivation. Getting money involved can jeopardize the whole ecosystem, but for the past year we’ve been experimenting with a model that lets us pay contributors for mission-critical work, while maintaining a culture of volunteerism. It all started with the Mozilla Open Source grant* about a year ago. This grant effectively enabled us to pay our own developers to work on features that […]

Read more...

Notable Replies

  1. From customers who purchase hosting plans at https://discourse.org/buy

    The general idea is that paying customers help improve Discourse, both for themselves, and for the greater open source community at large.

  2. ljpp says:

    I've thinking about ways to micro-contribute to Discourse financially. Got this idea:

    • Bring ad plugin to the core, improve it.
    • Enable ads here
    • Offer a micro payment option to remove ads (add this feat too). Meta has a nice and growing user base.
    • Profit

    You provide free software and free support. We (members) might as well contribute a little, financially.

  3. It's fine to contribute by spreading the word about Discourse, it's also most excellent to contribute by running a real live Discourse community and providing feedback!

    Stepping up from that, people can contribute bugfixes, localizations, general support of others, and tons of other stuff.

    :moneybag: is important, it is what keeps us in business for sure... but it's not the only thing that matters by any means.

  4. Lutz says:

    Regardless of the fact that I am trying to support you with a little bug testing, I would also like to contribute something from time to time. The easiest would be a quick paypal donation. I think many smaller donations will help you as well.

    It is difficult to keep a smaller forum alive. Especially for non-English Communites. I am very glad to have made the step from phpBB to Discourse. This opens up many new possibilities. For this and for the support, here in this forum, I'm really grateful.

  5. Thanks, greatly appreciated! But we will gladly accept donations of your time more so than money. :wink:

  6. I think @codinghorror is right. Communities are created and grown by sharing a passion. Our passion is Discourse. The biggest mistake you can make is to divert focus from that. That's a great attest to the professionalism of the Discourse team. And in this stage of Discourse' lifecycle, quality is the most important factor. It is quality that Discourse distinguishes from other systems, and it is quality that attracts attention. And good community leadership should leverage that any way they can. By welcoming meaningful contributions in any shape or form, you build loyalty. And these days, loyalty is worth its weight in gold. Not in the short term, but always in the long term. And corrrect me if I am wrong, but that has been pretty much @codinghorror's mindset from Day One.

Continue the discussion meta.discourse.org

2 more replies

Participants

Feb

6

2 months ago

Discourse’s Fourth Birthday

Jeff Atwood

As of today*, it’s been four years of Discourse! It feels like only only yesterday that we launched Discourse as an open source project. We’ve certainly been busy for the last four years: 1 official non-beta release of Discourse 7 total releases of Discourse, currently on 1.8 beta ~600 hosted customers ~8000 public installations of Discourse on the Internet 21837 commits, 560 contributors, 20541 stars on our open source code at GitHub 17500 topics, 245000 replies, 24000 users on meta.discourse.org I’m happy to announce that in our fourth year, we’ve […]

Read more...

Notable Replies

  1. Lutz says:

    Time to say a BIG THANK YOU to all the developers and contributors. I really appreciate your work and am very grateful for it.

    Well done!

  2. SidV says:

    There is nothing like Discourse.
    Impossible to compare with "the forum/board" or "the community" or "the bulletin" that crosses your mind.

    I am very very very happy to have encouraged myself to make the leap and move forward.
    Here it is always forward (as Luke Cage says). :wink: :thumbsup:

    Thank you very much to the team, and to the whole community.
    The support and "customer service" here are simply exceptional.

    Regards from Argentine :allthethings:

  3. One thing I should have added, but neglected to, is that @falco and @oblakeerickson were hired from the community here on meta!

    We love hiring from our community, and nothing makes me happier than converting avid Discourse community members into real live team members so they can work on something they :heart: alongside us, all day, every day.

  4. Thanks to all Developers. Amazing Open source project I have known after Blender3D. Best of luck for future endeavours. :slight_smile:

  5. Happy Birthday to Discourse, well done to the team behind it and all the contributors. Here's to your next 4 and beyond :champagne:

  6. Congratulations and Happy Birthday. I was skeptical of forums and preferred mailing lists for many years, but Discourse demonstrated that the problem was with how the forums were done, not the concept itself. Discourse is clearly a far better solution and has dramatically improved the community surrounding Keyboard Maestro. Fantastic results, so thank you to you and all your team for all the hard work!

Continue the discussion meta.discourse.org

1 more reply

Participants

Jan

27

3 months ago

Discourse for Private Communities

Erlend Sogge Heggen

There are many reasons why a community might be private: Paid memberships; a company intranet; a sensitive subject matter; beta testers; a grassroots movement building momentum before going public. Whatever the reason, we want Discourse to function well in private contexts. We reached out to 23 private Discourse communities to learn more about their use cases, and 10 of them got back to us with some great answers. How does your organisation use Discourse? (…) we’re spread around the world and we’re also organized fairly traditionally into fairly independent silos. […]

Read more...

Notable Replies

  1. An opportunity I see for making Discourse continue to improve for private communities (particularly company intranet sites), is to have more integrations with other private systems

    The slackdoor plugin gives Slack some ability to unfurl links to private discourse instances, but going the other way would be cool too (i.e., having the ability to Onebox links to private Slack instances).

    Same goes for things like Google Docs. The current solution is better than it used to be, but it'd be great if Discourse could be configured to have the necessary authorization to actually fetch and onebox private docs.

    These are just a couple examples that come to mind - I imagine each private instance would have their own thoughts on what integrations like this would be valuable.

Continue the discussion meta.discourse.org

Participants

Jan

6

4 months ago

Discourse 1.7 Released!

Jeff Atwood

Today, after four months of work, we’re proud to release Discourse 1.7. Discourse 1.2 – Feb 2015 Discourse 1.3 – June 2015 Discourse 1.4 – September 2015 Discourse 1.5 – April 2016 Discourse 1.6 – August 2016 Official iOS and Android Apps Thanks to Sam Saffron, we released an Official Android Discourse app and an official iOS Discourse app. These apps offer native push notifications and a way to aggregate all your Discourse sites in one place. The apps are free to use for all, but do note that push […]

Read more...

Notable Replies

  1. Great update! But I don't get where I activate the new front page with both categories and posts. Could someone please help me?

  2. Admin > Settings > search for desktop category page style

  3. holden says:

    Wow, what an update!

    Congrats and a huge thank you to all involved.

  4. Congratulations to the entire team and all contributors! Discourse just keeps getting better!

  5. Congratulation to this milestone!

    Do you consider to distribute it via https://f-droid.org?

    You would fit into this alternative software repository since it comprises only free, open source software.

  6. We LOVE you guys. Keep up the great work! :smiley:

Continue the discussion meta.discourse.org

1 more reply

Participants

Dec

16

4 months ago

Discourse New User Tips and Tricks

Jeff Atwood

If you’re new to Discourse, here are a few quick tips and tricks to get you started: Reading Selecting a topic title will always take you to your last read post in the topic. To enter at the top ↑ or bottom ↓ instead, select the reply count or last reply date. Topics above the light red line are new or updated since your last visit. If you have read all the way to the end of a topic, its title will be light grey instead of black. Navigation For […]

Read more...

Notable Replies

  1. If there are any other tricks and tips -- non-obvious essentials that every new Discourse user should know, please provide suggestions on that here.

  2. Jeff,

    Below is a link to the user guides I've generated since we went live. They are a bit wordy, and some of them are fairly specific to our forum, but they are all in response to questions which users raised with respect to the new platform.

    Some of them seem really trivial, but we had various problems with users not being able to distinguish between private and public messages.

  3. As a newbie to Discourse, and being silly enough to volunteer to be a moderator just as we went live on the new platform I felt a distinct need for a "New Moderator tips and tricks" topic. Meta had most of the information I was looking for, but it appears as mixed in with more technical admin information.

    How about a similar theme for new mods?

  4. Are you on Discourse 1.7 or later?

  5. Here's the "How To" list for my forum:

    Some are specific to our use case. They're generally responses to frequently-asked questions.

Continue the discussion meta.discourse.org

5 more replies

Participants

Nov

2

6 months ago

Discourse for Maker Communities

Erlend Sogge Heggen

There is a thing called the “maker movement” and, well, it’s awesome. People are setting up shop in their basements, backyards or dedicated makerspaces to create things together. Makers openly exchanging their ideas and designs with one another in the pursuit of better solutions to problems that need solving. That problem can be anything from “how can we make underwater exploration affordable to hobbyists?” to “can we make an airborne flamethrower?”. Turns out Discourse is a great addition to a maker’s toolbelt when your DIY activity of choice can be […]

Read more...

Notable Replies

  1. TyIsI says:

    The Vancouver Hackspace in Vancouver, BC, Canada also uses Discourse at https://talk.vanhack.ca/. At first primarily as a replacement for the mailing lists, but now everyone is settling into using "Talk" quite nicely. We also have integration from our announcements/events category into Slack.

Continue the discussion meta.discourse.org

Participants

Oct

17

6 months ago

Official Slack integration for Discourse

Erlend Sogge Heggen

Today we’re making Slack chat a first class integration, available on all hosting plans. Over time we’ve noticed that a whole lot of our customers use Slack, and we do too! The Discourse team uses Slack strictly as a team coordination tool for things that need to be discussed right now, but other teams are using Slack in all sorts of creative ways, even as a community hub. We think Chat and Community are two great tastes that taste great together, and we’re happy to extend Discourse to better accommodate […]

Read more...

Start the discussion at meta.discourse.org

Oct

10

6 months ago

Announcing v1.0 of WP Discourse

Erlend Sogge Heggen

We are pleased to announce the v1.0 release of WP Discourse, our official WordPress plugin. A huge thanks goes out to Simon Cossar who spearheaded this push towards a stable release. We’d also like to thank Ben Word who’s been graciously maintaining the plugin since its early inception. If you haven’t heard about WP Discourse before you can learn more about it below. Use Discourse for comments: Automatically creates a forum topic for discussion when a new blog post is published. Associates WP author accounts with their respective Discourse accounts. […]

Read more...

Notable Replies

  1. If I comment on Discourse, it still says: Start the discussion... on my WordPress install.

  2. Found it. Thanks! It had to do with some Comment settings not allowing the comments to get through.

Continue the discussion meta.discourse.org

Participants

Aug

18

8 months ago

Discourse for Online Education Communities

Erlend Sogge Heggen

Just like our survey for game communities back in May, we once more sent out a survey to a mix of customers and self-supported Discourse communities. This time we wanted feedback from leaders in online education. We’re absolutely ecstatic about the amount of learning tools readily available online for young and old minds alike today. Even more so because so many of these sites have chosen to use Discourse to build their communities, in which educators and learners can work effectively together to improve their common platform. 8 hosted customers […]

Read more...

Notable Replies

  1. We're self-hosting too - forum.easyuni.com - a site in Asia for students to search, compare and "apply" to universities locally or abroad.

    For the past several months we've been working on integrating Discourse more closely with our site (and a new version of the site).

    Here's how we use Discourse:

    • 1st level categories are countries (study destinations)
    • 2nd level are colleges in those countries

    Every college published on the site would get it's own category in Discourse. Then, on a college profile page we display the latest topics from its category in Discourse.

    Own/my profile (not discourse profile):

    My profile on mobile:

    Someone else's profile (note the Message button):

Continue the discussion meta.discourse.org

Participants

Aug

5

9 months ago

Discourse 1.6 Released!

Jeff Atwood

We’re thrilled to announce that today marks the release of Discourse 1.6! Discourse 1.2 – Feb 2015 Discourse 1.3 – June 2015 Discourse 1.4 – September 2015 Discourse 1.5 – April 2016 Enhanced Security Like any responsible open source project, we take security very seriously at Discourse. We try to roll out fixes for security issues within a day of being reported and reproduced. However, this particular release had two major customer contributions to security in the form of formal security penetration testing efforts from MITIE via Vertex Technologies Nest […]

Read more...

Notable Replies

  1. I am loving the new update so far it's great!

  2. Great update! Thanks fellas. Keep it up.

Continue the discussion meta.discourse.org

Participants

Jul

8

9 months ago

Reply-by-email enabled for all Discourse customers

Erlend Sogge Heggen

After a few weeks of testing, we are now introducing reply-by-email to all our hosted customers. Every email notification your users receive from now on will include the notice “reply to this email to respond” in the footer. Replying by email is great for people who are on the move or just happen to prefer email for whatever reason — accessibility, habit, or offline access. How does it work? We’re running our own email server so that we are fully responsible end to end and we can guarantee a good […]

Read more...

Notable Replies

  1. I'm pretty confused between this:

    "Not only can you accept new topics by email to categories and groups, you can even set a custom incoming email address like mailinglist**@example.com** or support@example.com"

    and this:

    "Can I use my own domain?
    Not at this time, no. We don’t have any plans to support custom domain names at this time, but if we see that it’s widely requested we will look into it."

    Did you accidentally include information for non-hosted installs in the guide?

Continue the discussion meta.discourse.org

Participants

May

25

11 months ago

Discourse for Game Communities

Erlend Sogge Heggen

About a week ago we sent out a brief survey to the game-maker segment of our customer base, looking for some insights on how they make the most out of Discourse, and what else they’d like to see added to it.  Game companies have been some of the biggest Discourse success stories, which is no surprise considering gamers (ourselves included) formed passionate communities around the games they love before the Internet even existed! 8 Hosted Infinite Interactive – community.gemsofwar.com Choice of Games – forum.choiceofgames.com Gearbox Software – forums.gearboxsoftware.com Radiant Entertainment – discourse.stonehearth.net Turtle Rock […]

Read more...

Notable Replies

  1. Falco says:

    Great post @erlend_sh!

    And love the site list, gotta get some ideas for my own instance of gaming forum.

  2. Shoot! I forgot to nudge one of my favourite new (non-customer) Discourse forums about the surevey, https://boards.faeria.com/. If anyone wants some styling inspiration, that one's a must-see.

  3. I find it a bit curious that one of the features mentioned as awesome by the communities polled is the badge system.... not because it isn't good, I think it is AWESOME and we use it extensively on our own forum http://forum.combustionpunks.co.uk/badges
    but because there doesn't seem to be much custom use on the forums surveyed.

    We are really wanting to push the use of the badges on our forum and are looking at how other forums utilise the system as per my post here https://meta.discourse.org/t/who-is-extensively-using-the-badge-system/46770 and I am looking for inspiration from how other communities use the badges.

    Anyone know of any forums pushing the badge system?

  4. That's a good observation. We can continue this discussion in your dedicated topic.

Continue the discussion meta.discourse.org

Participants

May

3

12 months ago

Using Discourse as a community-powered wiki

Erlend Sogge Heggen

The following is a guest post by Sam Nazarko, CEO and founder of OSMC.tv Are you using Discourse in a novel way? If you’re interested in writing a guest post like this one, please get in touch. In 2014, I started working on a new project, OSMC (Open Source Media Center). OSMC is a free and open source media player based on Linux that lets you play back media from your local network, attached storage and the Internet.   As the project started to accumulate users, we wanted to help the […]

Read more...

Notable Replies

  1. this is pretty awesome! I might try this out on a new project, but just a heads up, the github links are dead. looks like the repo was refactored, so now the links are here:

    wiki.js

    wiki.php - now a module
    https://github.com/osmc/website/tree/master/server/modules/wiki

    is it possible to get Sam (or someone from OSMC) to put together a little how-to on using their Wiki code?

  2. awesome - thanks @marktheis! as an aside - is the site css based off a framework, or completely custom? I noticed you guys use express/ghost/normalize.css - wasn't sure if the rest was built from scratch or used something a la Susy or Bourbon as a starting point. either way, I love the design!

  3. css is completely custom. Frameworks are nice, but I always end up fighting the framework. And they're usually too big for my taste.

    Yes apart from express, ghost, and a few js/css modules everything (server/client) is built from scratch.

    With a website that depends on a lot of external services (discourse for wiki and comments, woocommerce for shop, another server for diskimages) I think that node with express and handlebars templates works really well.

    Btw. I'm also currently building an email system that takes posts from discourse, and turns them into ready and processed emails via Foundation for Emails. To be consumed by phplist. Yes I really don't like phplist's html editor :smile:

  4. Interlinking: if you mean canonical urls then no. We find that google prioritises osmc.tv/wiki over discourse for us, so I haven't made any changes there. (It's not that important for us atm).

    categorization: Yes each wiki post is in a category our discourse and site.

    Tagging: No. We don't use the tag plugin.

  5. Been a bit busy lately, here's the short version.

    The gist of it is to arrange it properly in discourse.
    We have a main table of contents (toc) post with links to each category toc that then have all the posts listed for that category.

    So for us it's:

    Main toc post with links to all the category posts:

    > general
    > vero
    > pi

    And then in the general post e.q.

    > FAQ
    > how to
    > get started

    So via the discourse api you get the main toc. loop the category links, then you loop the post links and get the title and body.

    We then write the whole thing to a single json file for easy use.

    So when you go to https://osmc.tv/wiki/general/frequently-asked-questions/

    It looks if "general" exists in the json file, and then after that it looks up the title of the post. If that also exists it renders the page with that content.

    Hope that helps :slight_smile:

Continue the discussion meta.discourse.org

6 more replies

Participants

Apr

14

2016

Beginner’s Guide to Creating Discourse Plugins

Jeff Atwood

Part of our important work with Rails Girls in 2014 and 2015 was not just to mentor and encourage new developers, but also evolve Discourse into a platform that’s generally friendly and easy for developers to build on. We’ll be working with the Rails Girls project again in 2016, and this year will be our first with Google Summer of Code. As we work with novice developers and help them get comfortable building on Discourse, we get better at it, and our Discourse extension points and plugin story continues to […]

Read more...

Start the discussion at meta.discourse.org

Apr

1

2016

Discourse 1.5 Released!

Jeff Atwood

We’re proud to announce that today marks the release of Discourse 1.5! This was a huge release that took us almost 7 months to build: Discourse 1.2 – Feb 2015 Discourse 1.3 – June 2015 Discourse 1.4 – September 2015 5× Faster Topic Page Perhaps the most significant improvement in this release is a dramatic overhaul of our topic page for a 5× speed improvement. That’s right, the topic page – the page where most people will spend most of their time in Discourse – is a whopping five times […]

Read more...

Notable Replies

  1. Way to go Team Discourse! This release looks amazing! Thank you for all of your hard work!

    Discourse is an AMAZING piece of software!

  2. Some great stuff there :slight_smile:

  3. Courtesy of @DeanMarkTaylor, here's an interesting stat addendum.

    Counting activity in all the "discourse/*" repos during the period of 22. September 2015 - 01. April 2016:

    • 136 users made 356 Pull Requests (across 17 repos)
    • 89 users had 221 of those PR's merged (across 16 repos)
    • In addition other pull requests were used as the basis for coding changes added to the core directly by the team.

    Big thanks to the following contributors on GitHub:

    • cpradio
    • dandv
    • davidgnavas
    • fantasticfears
    • gschlager
    • xfalcox
    • fefrei
    • mikhailvink
    • pvalexander
    • rriemann
    • abbasfaisal
    • adamcapriola
    • adrapereira
    • andyw8
    • angusmcleod
    • aryanraj
    • bgr11n
    • BYWallace
    • carsonreinke
    • chapel
    • darix
    • dasnixon
    • dereckson
    • devonestes
    • discoursehosting
    • djtye
    • Dorthu
    • dtchau
    • DukeofRealms
    • ebernhardson
    • emanuelet
    • fearlessfrog
    • featheredtoast
    • gdpelican
    • getabetterpic
    • gpaumier
    • GrantStreetGroup
    • Grexy
    • gwwar
    • halfstrik
    • httvncoder
    • humzashah
    • huulbaek
    • iamntz
    • jamesfid
    • jamesgecko
    • jamielinux
    • JaredReisinger
    • Jdesk
    • jeremylan
    • jfoclpf
    • joebuhlig
    • jomaxro
    • JSFernandes
    • jslew
    • karies
    • keepcosmos
    • kellec
    • khoa-le
    • LeoMcA
    • lumenlunae
    • maclover7
    • manelvf
    • markbiegel
    • Martyn96
    • mcwumbly
    • MichaelMarner
    • Mooash
    • motte215
    • phw
    • pra85
    • RalfJung
    • rchanley
    • RomeoPapaSK
    • rubo77
    • ryantm
    • sammyd
    • scossar
    • seth-reeser
    • sethdeckard
    • sethherr
    • sghebuz
    • simplystuart
    • Stealthii
    • tnorthcutt
    • tomasibarrab
    • uppfinnarn
    • xfix
    • zigomir

    Maybe we should start a tradition of including this exhaustive list as part of the #releases topics?

Continue the discussion meta.discourse.org

1 more reply

Participants

Mar

28

2016

Switching Your Discourse from Mandrill to Mailgun

Jeff Atwood

Self-hosted Discourse requires email to function, so we’ve always had a symbiotic relationship with third party email providers. In the past we’ve recommended Mandrill, we use it ourselves for some of our sites, and we’ve had nothing but positive experiences with Mandrill … until now. On February 24th, Mandrill announced they are essentially closing the Mandrill service forever as of April 27th, 2016. Going forward, all Mandrill users will be required to have a paid monthly MailChimp account and verify ownership of all sending domains. Here’s the timeline: Starting 3/16, […]

Read more...

Notable Replies

  1. Is there any way to provide Google Gmail (SMTP) or Google Apps (SMTP-relay) as one of standard option in Discourse admin panel - rather updating app.yml?

    Between, is there any post on new version 1.5 release? I mean change log summary?

  2. Setting up SMTP has to be done by updating app.yml, sorry.

    Using google for SMTP has been discussed at length.. try the search. Here's one.

    I personally tried it and gave up on it in favor of mandrill, and now have switched to mailgun. It's easy and "set and forget" once it's working.

  3. I had deliverability issues with Mailgun that I fixed by adding MX records for our Mailgun subdomain:
    https://documentation.mailgun.com/quickstart-receiving.html#add-receiving-mx-records

    It's a bit counterintuitive, because we're not receiving emails through Mailgun. But here's what Mailgun's support told me:

    The error (which is called Sender Address Verification) that you are seeing is due to the recipient server performing a MX lookup on the envelope.mail-from address and failing to find the records for the domain listed. Some email servers check the domain in this envelope.mail-from field for MX records, and if the records do not exist, the email servers reject the message. Therefore, by adding Mailgun's MX records to your domain, the MX lookups of those email servers should succeed, and the servers will accept your messages.

    Hope this helps other frustrated folks!

  4. As helpfully noted here:

    You may need to clear your giant mail queue backlog in Sidekiq before making this switch, if you had a failing email situation going on for some time.

  5. Steven says:

    It looks like a credit card is required for an account in Mailgun to be able to send emails.

    I've been working all night on a new forum to see why emails didn't work. And I just noticed this change on their sign up form. It worked as usual 2 weeks ago I think, it must be pretty recent.

    Old accounts are not affected at the moment tho

Continue the discussion meta.discourse.org

3 more replies

Participants

Mar

11

2016

The ideal GSoC applicant

Erlend Sogge Heggen

This is our first year participating in Google Summer of Code. In short, if you’re a student with some Rails & Ember skills, you should check out our GSoC profile and consider applying for a chance to do paid work on Discourse under the mentorship of the core team this summer. We’ll be taking applications during 14. – 25. of March. With that out of the way, we’d like to take a moment to explain what we’re looking for in a GSoC student. Since our admission into the GSoC program, we’ve already […]

Read more...

Notable Replies

  1. As a 10-year veteran of GSoC, I believe at least one pre-proposal code contribution (i.e., involvement with the project before applying) is the biggest predictor of student success. It's not a guarantee, and it's possible to be successful without it, but as mentioned in the blog post, it's extremely valuable.

    1. Mentors and org admins have some level of assurance that you are up for the challenge.
    2. They also see that you care enough about the project to learn a little bit about it and take on a bug. (Even if you've done a pull request and it doesn't get merged!)

    Many GSoC organizations require a contribution before the proposal, but even if they don't, it's always a good idea. :slight_smile:

    Good luck to all students!

  2. Can't wait to sign up for GSoC come tomorrow 14th March, 2016. Thank you Discourse for being there...

  3. Falco says:

    I guess he's talking about doing Passion Work on your free time.

    I have a full time job (8h a day + plus commute) and I try to help Discourse at night when I get home or on Weekends (between some Dota 2 games :wink: ).

    My wife uses her free time doing charity work, I do open source, my friend study foreign languagues, etc. It's all about following your passion :heart:.

Continue the discussion meta.discourse.org

1 more reply

Participants

Mar

4

2016

Free Discourse forum hosting for community-friendly GitHub projects

Erlend Sogge Heggen

Discourse is proudly and unconditionally 100% open source ever since our public launch just over 3 years ago. Open source does not exist in a vacuum. We strive to be not just a great open source tool, but upstanding open source citizens, too. We’ve had an informal policy of providing free hosting for other open source tools that Discourse directly relies on. And although it was never announced, if you asked us, we’d offer a standard 50% hosting discount to any popular open source project. Open source projects with a Discourse […]

Read more...

Notable Replies

  1. Just to clarify -- if your project is on GitHub and you don't quite meet the threshold criteria of …

    • 2000+ stars
    • 30+ contributors

    … feel free to contact us via the form. We'll work with you. :slight_smile:

    The purpose of the thresholds isn't to arbitrarily keep projects away, but rather to ensure that there's enough critical mass for a solid discussion community to form around your project. We guesstimate it takes about 5 people :man: :woman: :older_woman: :older_man: :baby: actively participating in the discussions each day for your discussion community to "work".

  2. That's great news!

    Your users can log in with GitHub logins

    Are only GitHub logins supported, or will Twitter, Facebook, Google+ and plain e-mail accounts also work?

    Also, I understand custom imports would take too much time, but importing from an existing Discourse instance can be done manually, right?

  3. All of those will also be available.

    Yep, that's entirely doable. Correct me if I'm wrong @team, but we do prefer to have the Discourse backup sent to us so that we can apply it ourselves.

  4. sam says:

    Yes, you can configure this yourself, no problems. Additionally we plan to roll out "automatically" configured incoming email in the upcoming months.

  5. Oh my bad, I didn't realise you were replying to the post right above. No, you will not need to create a separate gmail account for email. Speaking of which, we are gradually rolling out this feature for our customers now. We're starting in small increments, so the official announcement is still a little ways off.

  6. My comment might be slightly off-topic, but I wanted to say that I'm amazed at how Discourse team markets their product and applies various strategies to target primarily larger organizations and companies. There is a lot to learn from them - and this topic is just another excellent example of how to make people tempted to move to Discourse. Absolutely amazing stuff. Read it twice - first, as a Discourse (potential) user. Second - as a marketer.

Continue the discussion meta.discourse.org

5 more replies

Participants

Feb

5

2016

Discourse’s Third Birthday

Jeff Atwood

As of today, it’s been three years since we launched Discourse as a public project. How time flies when you’re having fun! As birthday present, I’m pleased to announce that as of this morning – literally, this morning – we now own our domain name: discourse.com The domain was previously owned by Educational Testing Services, aka the non-profit company behind the SAT and ACT college entrance exams. If you’re curious what used to be there, check out the wayback machine. That domain went permanently offline in 2006. We’ve had no […]

Read more...

Notable Replies

  1. Happy Birthday! :confetti_ball: :gift: :confetti_ball:

  2. downey says:

    Happy birthday! I feeling old coming from the red/blue pill days.

    It's good to have the .com domain name, but I'd argue the general cultural expectation is for an open source project to run under a .org domain. :slightly_smiling:

  3. Congratulations to the entire team!

  4. Congratulations to the discourse team.

  5. In this case they could be more like WordPress and move the hosting portion over to the .com

Continue the discussion meta.discourse.org

8 more replies

Participants

Jan

28

2016

A Year in Discourse – Recap of 2015

Erlend Sogge Heggen

Discourse is a large open source project buzzing with activity, so a lot of cool things happen over the course of a year. Let’s look back at 2015 and pick out some highlights. Our Most Popular Topic of 2015 The most viewed topic of the year was The State of JavaScript on Android in 2015 is… poor. At 200+ replies and lots of first-time – and drive-by, but nothing wrong with that – posters, the single-threaded conversation stayed the course just fine, and the opening article was enriched many times over by […]

Read more...

Notable Replies

  1. p.s. I would have liked to include some proper GitHub statistics e.g: "unique contributors to Discourse (+ related projects) from Jan 1 2015 to Dec 31 2015" and so forth, but I can't work out how to get this from the GitHub API.

    If someone would like to lend a hand with this, let me know and I'll be sure make good use of it, starting with our upcoming v1.5 release!

  2. I think we should consider doing this with plain ol' git rather than github.

    The script that parses the logs to create release notes might be a good place to start. There might also be prior art out there.

  3. Had a little play with BigQuery, first time I have so you might want to check for errors:

    This is just for the github.com/discourse/discourse project.

    SELECT
    count(*) as count,
    type as type,
    STRFTIME_UTC_USEC(TIMESTAMP_TO_USEC(created_at), "%Y-%m-%d") as date
    FROM (
      TABLE_DATE_RANGE([githubarchive:day.events_], 
        TIMESTAMP('2015-01-01'), 
        TIMESTAMP('2015-12-31')
      )) 
    WHERE repo.name = "discourse/discourse"
    AND NOT type contains "Comment"
    GROUP BY date, type
    ORDER BY date, type

    I can provide a Google Sheet or CSV perhaps if needed.
    Google Sheet here

Continue the discussion meta.discourse.org

Participants

Jan

12

2016

How Coinbase Uses Discourse to Educate Customers and Improve SEO

Erlend Sogge Heggen

As part of our ongoing series of interviews with customers, our latest is with John Mardlin who helps traders, devs and humans use bitcoin at Coinbase — partly through their Discourse-powered community.coinbase.com. What is Coinbase? Coinbase’s mission is to make bitcoin accessible for normal people. Our core product is a wallet with +3MM users, which enables buying and selling of Bitcoin in over 30 countries (with more coming soon). We also offer a range of services that are enabling the bitcoin ecosystem to flourish the Coinbase Exchange for active traders […]

Read more...

Notable Replies

  1. I was going to add that I'm still keeping my eye on the topic about warning on external links, e.g. bad guys posting phishing links like this:

    [totally safe and normal link](http://evil-phishing-site.com/bad-link)

    It might be best to warn (if enabled) on TL0 posted links, like so:

  2. cregox says:

    "Improving SEO" must be one of the best and often technically overlooked discourse features.

    For one, www.discourse.org have no mention of "SEO", "engine" or "google" (in this sense) after a quick CMD + F.

    Very good word choices for the title! :slightly_smiling:

  3. I suppose we should be opening new topics to discuss feature requests mentioned in the post?

  4. @john_mardlin incredibly helpful to read about your SEO strategy and results.

    Also, I am intrigued by how you link up your knowledge base and Discourse as that's a balance we're trying to strike as well and we'll probably just move forward, copying your approach with "feedback" buttons on the bottom that link to hidden docs.

    @codinghorror I'd love to see more blog posts about how people use Discourse, this was really helpful.

  5. Go nuts.

    It was a lot of work at first, but we eventually found some tricks to simplifying the process. The key was instead of manually creating a new topic, we made use of the /newtopic URL feature, and built a spreadsheet of all our KB articles:

    Hopefully that's enough to help you reverse engineer the process. :smile:

    To @cregox, SEO was actually more of a pleasant side effect. I typically think of SEO as a marketing tactic, although for us it's almost entirely SEO for people to help themselves. Though really the lines behind customers service and marketing are blurring, and both are good things to have. :chart_with_upwards_trend:

Continue the discussion meta.discourse.org

3 more replies

Participants