I’d like to start a dedicate Stan blog at <blog-name>.mc-stan.org.
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.
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, blog.mc-stan.org is conservative, but IMHO conveys exactly what is going on.
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 blog.mc-stan.org 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).
That’s on the to-do list. I want to convert it to bookdown.
I think we can use the url blog.mc-stan.org 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.
WordPress:
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.
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.
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.
IMHO, if you use something like Jekyll-now as a starting point, you can set up the blog in no time. In addition to that, you have version control, it’s inexpensive to maintain, and is easy to render the blog locally (including drafts) when you want to check how the article would look like before publishing it.
Another advantage of Jekyll-now is that you can enable comments and Google Analytics in minutes.
I was able to get a pretty good blog on github.io using RBlogdown, which is pretty impressive since I’m a web programmer dilettante. It supports math stuff, https://bookdown.org/yihui/blogdown/templates.html . The relevant bit is down on the page so I’ve reproduced below:
Support math expressions through MathJax. Add the code below to foot_custom.html.
This requires substantial knowledge of JavaScript and familiarity with MathJax to fully understand the code above, and we will leave the explanation of the code to Section B.3.
Note that bootcss.com is only one possible CDN host of MathJax, and you are free to use other hosts.
@spinkney: are there other style options? Did this just pick up the style of your blog (which would be great for our blog). If so, would you be able to configure a Stan blog and make a pull request? In which case, we can just turn it on without having to figure out all the config.
For some reason, dead links from Disqus seem to go to random pages. Any idea if that’s something we can control?