Dedicated Stan blog



I’d like to start a dedicate Stan blog at <blog-name>

Question 1: What should we call it?

Question 2. Who oversees content?

For (1), I would prefer it not be too cute or obscure.

For (2), I think ultimate responsibility should rest with whoever oversees the web site, which is now Breck. Hopefully it’ll all stay civil and we can just trust people to post the same way we trust them to use the wiki.

Question 3. Where is it hosted?

  • WordPress: nominal annual fee with domain mapping; supports MathJax; experience using WordPress among the team members; separate content and password management for blog; can’t edit comments (this drives me crazy they don’t let you do that yet).
  • GitHub: free; content gets managed with rest of web site; no comments built-in, so we’d need external service like Disqus (anyone know others?); more control and more management required on our side to set up styles, etc.

If I had to do this tomorrow, I’d just go with WordPress because it seems easier. Though I’d feel bad about it because I like to do everything on GitHub.


Question 4. Who has the time to write content?


Just a thought: If the documentation was primarily a website (not primarily PDF as it is now), wouldn’t almost everything that could go on the official blog also belong to the docs? I think that between Discourse, wiki and the docs there is only a small room for content curated/created by the core team that is not covered by any of the three.

As for technology, I’ve had good experience setting up blog with blogdown (Rmd to blog), but that might need some tweaking if Python is to be supported.

As for name, is conservative, but IMHO conveys exactly what is going on.


Agree on the URL. Name suggestion: “Samples”


I think you have good answers to all of those questions and I’m happy to go with your inclinations, especially as you are likely the one to do most of the blogging at first.

I’d like to second and a lofty goal of integrating / cross-linking more of our documentation (which seems to involve getting the manual into HTML).


Having never used GitHub for blogging, WP is fine. It has a bit of a laggy interface if you’re writing long posts with lots of equations/pictures, but it’s perfectly workable.

I’m not sure I see the advantage of a git interface unless you’re looking to allow external people to make PRs as a way to do occasionally “external contributor” blogs. Git would be much better than the WP system if this is what you’re looking for (afaik).


+1 for


There’s a bunch of stuff going out that would be good to put there. I write things and Daniel wanted to write some things.


That’s on the to-do list. I want to convert it to bookdown.

I think we can use the url and call it “The Stan Blog”.

Have you tried their hosted version or just Andrew’s? I find Andrew’s gets bogged down and even hangs and won’t let me log in from time to time. I found the WordPress version better.


Just a couple points on running a blog on GitHub (cause my personal one is there and so is Generable’s and I manage both:

  • it’s a bit clunky:
    • it’s not GitHub directly, but it’s actually run through Jekyll
    • they implement a version of Markdown that isn’t really that well documented, so you’ll run into gotchas
    • customization is fairly hard to do
    • running locally is actually trickier than they make it seem; once up, it works.
  • it’s easy to set up:
    • should take me an hour or less to get up and running
    • if we never stray from their default styles, it’s simple
  • comments need to be managed by something like Disqus: once set up, almost no maintenance. But even Disqus has a freemium model.
  • overall: it’s just not a real blog-in-a-box platform, so will require maintenance.


  • Andrew’s blog isn’t hosted by WordPress directly due to cost (at the time). It looks like their pricing changed since then. Back then, I remember it was in the multiple hundreds of dollars per month.
  • For our purposes, I think we’re far from any of those limits, so we can run it for free or on the cheap.
  • It’ll handle most of the things we need.


How well Wordpress works with equations? I would assume more equations in The Stan Blog than in Andrew’s blog.


Andrew’s Wordpress has a slightly annoying latex markdown. You write $latex [expression]$ and it usually works (sometimes it takes a few goes). I’ve done some posts with quite a few equations and it hasn’t been too annoying.


As an alternative to GitHub you may want to consider GitLab, which makes it straightforward to host and deploy a blog using Hugo:

If you plan to write your posts in RMarkdown then the combination with RStudio and the blogdown package makes this a fairly slick setup.


Better than GitHub about of the box because it supports MathJax. Math goes in as $latex e^x$.

It’s fine for blog authors, even if the rendering requires web access.

It’s a pain for commenters because there’s no way for them to preview. I can’t believe they haven’t fixed this yet on WordPress.


Their site currently says:

GitLab has temporarily turned off custom domains support because of a security issue. The plan is to re-enable it after the 20th of February.

Probably not, though I suppose someone might be interested. At that point, we usually just publish case studies on the web, and that’s easy as things stand now with Jupyter or R markdown.