www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - So, About That Official Blog...

reply Jack Stouffer <jack jackstouffer.com> writes:
This keeps coming up, so in the theme of Andrei's talk and 
because my day job is a web dev, I decided to do something about 
it. I have created this tumblr blog which I hope to shape into 
the official dlang blog: http://officaldlang.tumblr.com/

A couple of notes:

1. I choose tumblr because we really shouldn't reinvent the wheel 
here with something as simple as a blog. Tumblr has thousands of 
servers, solid funding, solid uptime, and a simple interface.
2. Tumblr supports markdown
3. Tumblr gives complete access to its templating engine, 
allowing you to make the site look like what ever you want
4. Tumblr allows for custom domains, so if everyone here likes 
this idea then I can have the domain of the blog be blog.dlang.org
5. Any core team members who ask for access to the blog via an 
email to me will get it automatically

Now, onto the content,

I added two of Walter's Dr. Dobbs articles as examples. I'm not 
sure about the legality of this, if someone asks me to remove 
them I will.

Obviously we should have release announcements on the blog, but I 
think that one of the best ways that the blog can get interesting 
content is reposting content from the community, with the 
author's permission of course and a link back to the original. I 
would be willing to put my two D posts on there if people agree 
with this idea. We could also call for reviews of interesting PRs 
or ask for PRs of interesting bugs.

Please let me know what you think! I believe this is a good first 
step in the right direction.
May 05 2016
next sibling parent reply qznc <qznc web.de> writes:
On Thursday, 5 May 2016 at 18:22:50 UTC, Jack Stouffer wrote:

 Please let me know what you think! I believe this is a good 
 first step in the right direction.


Great that you took the initiative!

Does tumblr allow for syntax highlighting for code examples (e.g. 
including pygments)?

For content, the bi-annual vision statement belongs there as well.
May 05 2016
parent reply Jack Stouffer <jack jackstouffer.com> writes:
On Thursday, 5 May 2016 at 20:41:22 UTC, qznc wrote:

 On Thursday, 5 May 2016 at 18:22:50 UTC, Jack Stouffer wrote:

 Please let me know what you think! I believe this is a good 
 first step in the right direction.


 
 Does tumblr allow for syntax highlighting for code examples 
 (e.g. including pygments)?


Yes! In tumblr you have full control of the HTML, CSS, and JS on 
the page, which is another great reason to use it.
May 05 2016
parent reply Joakim <dlang joakim.fea.st> writes:
On Thursday, 5 May 2016 at 20:53:21 UTC, Jack Stouffer wrote:

 On Thursday, 5 May 2016 at 20:41:22 UTC, qznc wrote:

 On Thursday, 5 May 2016 at 18:22:50 UTC, Jack Stouffer wrote:

 Please let me know what you think! I believe this is a good 
 first step in the right direction.


 
 Does tumblr allow for syntax highlighting for code examples 
 (e.g. including pygments)?


 Yes! In tumblr you have full control of the HTML, CSS, and JS 
 on the page, which is another great reason to use it.


I have long suggested a blog, good to see you doing it.  Github 
might be better because it does automatic syntax highlighting, no 
need to format code yourself.  Jakob's post on memory safety came 
out looking very nice:

https://jakobovrum.github.io/d/2016/01/20/memory-safety.html

Not sure what commenting functionality either provides, that 
should be there too, though dealing with spam can be a pain 
without proper filters.
May 05 2016
parent reply Jack Stouffer <jack jackstouffer.com> writes:
On Friday, 6 May 2016 at 01:21:03 UTC, Joakim wrote:

 Github might be better because it does automatic syntax 
 highlighting, no need to format code yourself.


I thought about Github because it would offer one advantage to 
tumblr: it could be owned by the dlang Github account. But, while 
Github pages can be a blogging platform, tumblr is specifically 
designed to be a blogging platform, and that means several nice 
features that we get for with no extra work from anyone in the 
community. In addition to the examples I listed in my original 
post, one other great feature I discovered today is that tumblr 
provides a guest post feature where any tumblr user can submit a 
post to be reviewed, and with a click of a button, it can be 
posted on the blog with attribution.

Also, I can just include a simple JS library for the same 
auto-highlighting functionality.


 Not sure what commenting functionality either provides, that 
 should be there too, though dealing with spam can be a pain 
 without proper filters.


Disqus can be added quite easily to either, but I don't think 
that's something we actually want to do. IMO let's keep 
discussion on here, HN, and reddit, where there are mechanisms in 
place for getting rid of spam.
May 05 2016
parent reply Dicebot <public dicebot.lv> writes:
On 05/06/2016 04:26 AM, Jack Stouffer wrote:

 Also, I can just include a simple JS library for the same
 auto-highlighting functionality.


Please prefer static generators and pygment-like highlighters to JS
whenever possible. Demanding JS enabled for simple programming blog to
be rendered decently it simply outrageous.
May 05 2016
next sibling parent reply maik klein <maikklein googlemail.com> writes:
On Friday, 6 May 2016 at 03:01:07 UTC, Dicebot wrote:

 On 05/06/2016 04:26 AM, Jack Stouffer wrote:

 Also, I can just include a simple JS library for the same 
 auto-highlighting functionality.


 Please prefer static generators and pygment-like highlighters 
 to JS whenever possible. Demanding JS enabled for simple 
 programming blog to be rendered decently it simply outrageous.


I would also recommend a static site generator, I currently use 
Hugo https://gohugo.io/ though it is written it Go haha. Jekyll 
got really slow after 30 blog entries, especially if you want to 
do the syntax highlighting offline.
May 06 2016
next sibling parent reply Johannes Pfau <nospam example.com> writes:
Am Fri, 06 May 2016 07:48:48 +0000
schrieb maik klein <maikklein googlemail.com>:


 On Friday, 6 May 2016 at 03:01:07 UTC, Dicebot wrote:

 On 05/06/2016 04:26 AM, Jack Stouffer wrote:  

 Also, I can just include a simple JS library for the same 
 auto-highlighting functionality.  


 Please prefer static generators and pygment-like highlighters 
 to JS whenever possible. Demanding JS enabled for simple 
 programming blog to be rendered decently it simply outrageous.  


 
 I would also recommend a static site generator, I currently use 
 Hugo https://gohugo.io/ though it is written it Go haha. Jekyll 
 got really slow after 30 blog entries, especially if you want to 
 do the syntax highlighting offline.



Martin Novak uses pelican(0) for his (1) blog + isso (2) for comments.
Markdown blog posts + plugins for everything(3,4) + git + markdown
comments + self hosted comments sounds nice.


The main problem with static blog generators is that having multiple
blog authors is a little bit more complicated. We should at least give
direct push access to all authors. You don't want to wait weeks for
somebody to pull a spelling fix pull request ;-)

And it's a little harder to setup, but maybe we could use a setup which
automatically rebuilds the blog once somebody pushes to the git
repository. Then users don't need to have pelican installed locally.
Maybe use all non-final branches for previewing/testing where every
contributor gets a branch. We could use this workflow:

git pull

git push origin master:jpf91

git push


(0) http://blog.getpelican.com/
(1) https://code.dawg.eu/
(2) https://posativ.org/isso/
(3) https://github.com/getpelican/pelican-plugins/ 
(4)
https://github.com/getpelican/pelican-plugins/tree/master/liquid_tags
May 06 2016
parent Jack Stouffer <jack jackstouffer.com> writes:
On Friday, 6 May 2016 at 08:28:36 UTC, Johannes Pfau wrote:

 The main problem with static blog generators is that having 
 multiple blog authors is a little bit more complicated.


[snip]


 And it's a little harder to setup


I wouldn't call it the main problem, but it's certainly a large 
contributing factor to why I choose tumblr and not a self hosted 
solution.

There is a reason that the official blog never happened before 
now, mainly because people didn't want to figure out/deal with 
the logistics involved. As I said earlier in this thread, with 
tumblr we get a lot of this stuff out of the box.
May 06 2016
prev sibling parent reply Nick Sabalausky <SeeWebsiteToContactMe semitwist.com> writes:
On 05/06/2016 03:48 AM, maik klein wrote:

 On Friday, 6 May 2016 at 03:01:07 UTC, Dicebot wrote:

 On 05/06/2016 04:26 AM, Jack Stouffer wrote:

 Also, I can just include a simple JS library for the same
 auto-highlighting functionality.


 Please prefer static generators and pygment-like highlighters to JS
 whenever possible. Demanding JS enabled for simple programming blog to
 be rendered decently it simply outrageous.


 I would also recommend a static site generator, I currently use Hugo
 https://gohugo.io/ though it is written it Go haha. Jekyll got really
 slow after 30 blog entries, especially if you want to do the syntax
 highlighting offline.


I've been moving the direction of hybrid approaches. Kinda like static 
site generating, but the regenerating is done automatically as-needed, 
can receive updates via HTTP GET/POST and do other real-time processing 
during certain requests, etc. I don't know much about off-the-shelf 
website tools out there (or whether there are any that work this way), 
but it's what I did for the travis d compiler list ( 
https://semitwist.com/travis-d-compilers ):

It's fully dynamic templated, driven by Vibe.d and a database, new 
entires are added automatically via HTTP POST, etc, it has REAL 
server-side logic running. But instead of regenerating the HTML page on 
every request (or dynamically regenerating a JSON/XML description of the 
data on every request for client-side JS to then render - an approach I 
never really understood), the Vibe.d-based site simply regenerates a 
static HTML page when the *data* changes, which on most web pages is 
much less frequent than actual page requests.

There are other ways to adjust static/dynamic balances too. There's 
usually a LOT of components on even a fully-dynamic page that ARE 
pre-cachable, even if the page as a whole isn't:

For example, a classic case where a static site generator wouldn't work: 
An online shopping search results page. You can't predict ahead of time 
what queries will be run and pregenerate entire results pages, but you 
CAN pregenerate divs for how each individual item will be displayed when 
it does appear in someone's results page. Then when someone runs a 
search you just write the appropriate pre-built divs to the output 
stream, one after the other.

In short: Hybrid site generating :) Only generate on-the-fly what NEEDS 
to be on-the-fly. Only regenerate things when they change, not every 
time they're viewed (unless they change more than they're viewed, like 
maybe an admin-only site webstats page, but such cases are rare).
May 08 2016
next sibling parent Jacob Carlborg <doob me.com> writes:
On 2016-05-08 22:31, Nick Sabalausky wrote:


 I've been moving the direction of hybrid approaches. Kinda like static
 site generating, but the regenerating is done automatically as-needed,
 can receive updates via HTTP GET/POST and do other real-time processing
 during certain requests, etc. I don't know much about off-the-shelf
 website tools out there (or whether there are any that work this way),
 but it's what I did for the travis d compiler list (
 https://semitwist.com/travis-d-compilers ):

 It's fully dynamic templated, driven by Vibe.d and a database, new
 entires are added automatically via HTTP POST, etc, it has REAL
 server-side logic running. But instead of regenerating the HTML page on
 every request (or dynamically regenerating a JSON/XML description of the
 data on every request for client-side JS to then render - an approach I
 never really understood), the Vibe.d-based site simply regenerates a
 static HTML page when the *data* changes, which on most web pages is
 much less frequent than actual page requests.


Something like sever side caching?


 There are other ways to adjust static/dynamic balances too. There's
 usually a LOT of components on even a fully-dynamic page that ARE
 pre-cachable, even if the page as a whole isn't:

 For example, a classic case where a static site generator wouldn't work:
 An online shopping search results page. You can't predict ahead of time
 what queries will be run and pregenerate entire results pages, but you
 CAN pregenerate divs for how each individual item will be displayed when
 it does appear in someone's results page. Then when someone runs a
 search you just write the appropriate pre-built divs to the output
 stream, one after the other.


Sounds like Russian doll caching [1].


 In short: Hybrid site generating :) Only generate on-the-fly what NEEDS
 to be on-the-fly. Only regenerate things when they change, not every
 time they're viewed (unless they change more than they're viewed, like
 maybe an admin-only site webstats page, but such cases are rare).


[1] 
http://blog.remarkablelabs.com/2012/12/russian-doll-caching-cache-digests-rails-4-countdown-to-2013

-- 
/Jacob Carlborg
May 09 2016
prev sibling parent reply Seb <seb wilzba.ch> writes:
On Sunday, 8 May 2016 at 20:31:26 UTC, Nick Sabalausky wrote:

 I would also recommend a static site generator, I currently 
 use Hugo
 https://gohugo.io/ though it is written it Go haha. Jekyll got 
 really
 slow after 30 blog entries, especially if you want to do the 
 syntax
 highlighting offline.


 In short: Hybrid site generating :) Only generate on-the-fly 
 what NEEDS to be on-the-fly. Only regenerate things when they 
 change, not every time they're viewed (unless they change more 
 than they're viewed, like maybe an admin-only site webstats 
 page, but such cases are rare).


Guys - KISS! During the time we already spent in this thread, we 
could have written least five great blog entries!

Therefore +1 for static site generators - they keep stuff simple.
The advantage of Jekyll is that it works so nice with Github 
pages and everyone can thus preview the changes on their local 
gh-pages branch. Getting the Dlang theme is not difficult, see 
e.g. my proposal for to put the DIPs into a github repo:

https://github.com/wilzbach/d-dip
http://wilzbach.github.io/d-dip/DIP86

The DIP Jekyll site builds in ~five seconds (90 pages).
That being said, I like Hugo too.

Btw if we just keep using DDOC (a static site generator), all the 
custom macros will continue to work ;-)
May 09 2016
parent reply Seb <seb wilzba.ch> writes:
On Monday, 9 May 2016 at 12:31:37 UTC, Seb wrote:

 On Sunday, 8 May 2016 at 20:31:26 UTC, Nick Sabalausky wrote:

 [...]


 Guys - KISS! During the time we already spent in this thread, 
 we could have written least five great blog entries!

 Therefore +1 for static site generators - they keep stuff 
 simple.
 The advantage of Jekyll is that it works so nice with Github 
 pages and everyone can thus preview the changes on their local 
 gh-pages branch. Getting the Dlang theme is not difficult, see 
 e.g. my proposal for to put the DIPs into a github repo:

 https://github.com/wilzbach/d-dip
 http://wilzbach.github.io/d-dip/DIP86

 The DIP Jekyll site builds in ~five seconds (90 pages).
 That being said, I like Hugo too.

 Btw if we just keep using DDOC (a static site generator), all 
 the custom macros will continue to work ;-)


So

1) Jekyll
2) Hugo
3) Ddoc

Let's just make a simple decision, create the blog and create 
articles.
As long as we don't get any content, this doesn't matter anyways!
May 30 2016
parent Mike Parker <aldacron gmail.com> writes:
On Tuesday, 31 May 2016 at 02:06:42 UTC, Seb wrote:


 Let's just make a simple decision, create the blog and create 
 articles.
 As long as we don't get any content, this doesn't matter 
 anyways!


There will be a relevant announcement soonish.
May 30 2016
prev sibling parent reply Jack Stouffer <jack jackstouffer.com> writes:
On Friday, 6 May 2016 at 03:01:07 UTC, Dicebot wrote:

 Please prefer static generators and pygment-like highlighters 
 to JS whenever possible. Demanding JS enabled for simple 
 programming blog to be rendered decently it simply outrageous.


Using JS for an eye candy feature on the internet is not 
"outrageous". It's not like with JS turned off the code would be 
displayed with no formatting and in sans-serif.
May 06 2016
next sibling parent Dicebot <public dicebot.lv> writes:
On 05/06/2016 03:34 PM, Jack Stouffer wrote:

 On Friday, 6 May 2016 at 03:01:07 UTC, Dicebot wrote:

 Please prefer static generators and pygment-like highlighters to JS
 whenever possible. Demanding JS enabled for simple programming blog to
 be rendered decently it simply outrageous.


 
 Using JS for an eye candy feature on the internet is not "outrageous".
 It's not like with JS turned off the code would be displayed with no
 formatting and in sans-serif.


If the eye candy feature is purely static styling (and there are perfect
static highlighters available) - it is outrageous.
May 06 2016
prev sibling parent reply Adam D. Ruppe <destructionator gmail.com> writes:
On Friday, 6 May 2016 at 13:34:02 UTC, Jack Stouffer wrote:

 Using JS for an eye candy feature on the internet is not 
 "outrageous". It's not like with JS turned off the code would 
 be displayed with no formatting and in sans-serif.


Those JS things have a habit of lagging my laptop to a crawl, 
whereas a server side highlighter works beautifully without 
slowdown.

When your site works better without JS than with, you've made a 
mistake somewhere, especially when what the JS is doing could be 
free!
May 06 2016
next sibling parent reply Jack Stouffer <jack jackstouffer.com> writes:
On Friday, 6 May 2016 at 13:47:48 UTC, Adam D. Ruppe wrote:

 Those JS things have a habit of lagging my laptop to a crawl, 
 whereas a server side highlighter works beautifully without 
 slowdown.


Ok, I think we're focusing on an unimportant implementation 
detail here. Let's get back on track and discuss the important 
things, like

* Officiating this
* Getting content
* Legality of reposting past D articles
* Any branding problems

etc.
May 06 2016
parent reply Dicebot <public dicebot.lv> writes:
On 05/06/2016 04:17 PM, Jack Stouffer wrote:

 On Friday, 6 May 2016 at 13:47:48 UTC, Adam D. Ruppe wrote:

 Those JS things have a habit of lagging my laptop to a crawl, whereas
 a server side highlighter works beautifully without slowdown.


 
 Ok, I think we're focusing on an unimportant implementation detail here.
 Let's get back on track and discuss the important things, like
 
 * Officiating this
 * Getting content
 * Legality of reposting past D articles
 * Any branding problems
 
 etc.


There is one important relation to generating content - storing posts in
github repo and generating blog on merged automatically allows for
anyone to make fixup pull requests for stuff like typos or styling
tweaks. Same for proposing new posts. It is much more convenient than
e-mail based whitelist of posters.
May 06 2016
parent reply Jack Stouffer <jack jackstouffer.com> writes:
On Friday, 6 May 2016 at 16:00:26 UTC, Dicebot wrote:

 There is one important relation to generating content - storing 
 posts in github repo and generating blog on merged 
 automatically allows for anyone to make fixup pull requests for 
 stuff like typos or styling tweaks. Same for proposing new 
 posts. It is much more convenient than e-mail based whitelist 
 of posters.


You're right, the possibility of independent help is a point in 
favor of a generated blog.

However, I believe there are some downsides as well. Consider how 
long trivial PRs for the dlang.org and dconf.org sites sit with 
no reviews, e.g. https://github.com/dlang/dlang.org/pull/1286, 
https://github.com/dlang/dlang.org/pull/1283, 
https://github.com/dlang/dconf.org/pull/112, etc.

On the other hand, this problem can be mitigated (but not 
completely solved) on tumblr because access to tumblr blogs is 
permission based, even though it's a rather simplistic 
implementation. Normal users added via admins can make posts and 
edit them while admins can edit/delete anyone's posts and change 
the styling. There's also guest posts which allow random people 
to submit posts for review and approval and they have no 
permissions what so ever.

I think that if we dole out the admin permissions sparingly to 
competent people, then they can handle typos/quick fixes without 
the slow bureaucracy.
May 06 2016
parent Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:
On 5/6/16 6:27 PM, Jack Stouffer wrote:

 Consider how long trivial PRs for the dlang.org and dconf.org sites sit
 with no reviews, e.g. https://github.com/dlang/dlang.org/pull/1286,
 https://github.com/dlang/dlang.org/pull/1283,
 https://github.com/dlang/dconf.org/pull/112, etc.


Merged :o) -- Andrei
May 06 2016
prev sibling parent Adrian Matoga <dlang.spam matoga.info> writes:
On Friday, 6 May 2016 at 13:47:48 UTC, Adam D. Ruppe wrote:

 On Friday, 6 May 2016 at 13:34:02 UTC, Jack Stouffer wrote:

 Using JS for an eye candy feature on the internet is not 
 "outrageous". It's not like with JS turned off the code would 
 be displayed with no formatting and in sans-serif.


 Those JS things have a habit of lagging my laptop to a crawl, 
 whereas a server side highlighter works beautifully without 
 slowdown.

 When your site works better without JS than with, you've made a 
 mistake somewhere, especially when what the JS is doing could 
 be free!


I totally agree. This tumblr site easily lagged a bored i7. A big 
NO from me.
May 08 2016
prev sibling next sibling parent reply Jacques =?UTF-8?B?TcO8bGxlcg==?= <jacques.mueller gmx.de> writes:
On Thursday, 5 May 2016 at 18:22:50 UTC, Jack Stouffer wrote:

 This keeps coming up, so in the theme of Andrei's talk and 
 because my day job is a web dev, I decided to do something 
 about it. I have created this tumblr blog which I hope to shape 
 into the official dlang blog: http://officaldlang.tumblr.com/


That's nice! But it seems like you misspelled the blog title.
May 05 2016
next sibling parent Jack Stouffer <jack jackstouffer.com> writes:
On Thursday, 5 May 2016 at 21:25:23 UTC, Jacques Müller wrote:

 That's nice! But it seems like you misspelled the blog title.


Thanks for pointing that out, fixed link: officialdlang.tumblr.com
May 05 2016
prev sibling parent Nick Sabalausky <SeeWebsiteToContactMe semitwist.com> writes:
On 05/05/2016 05:25 PM, Jacques Müller wrote:

 On Thursday, 5 May 2016 at 18:22:50 UTC, Jack Stouffer wrote:

 blog: http://officaldlang.tumblr.com/


 That's nice! But it seems like you misspelled the blog title.


It's a feature, it keeps with web 2.0 tradition! :)
May 07 2016
prev sibling next sibling parent Jack Stouffer <jack jackstouffer.com> writes:
On Thursday, 5 May 2016 at 18:22:50 UTC, Jack Stouffer wrote:

 Please let me know what you think! I believe this is a good 
 first step in the right direction.


In an attempt to get more interest in this, I have sent several 
invites to people in the core team who have blogs or have written 
articles in the past. If you're interested in the concept of a 
dlang blog, I would appreciate it if you give me some feedback 
after you've looked at the interface a bit.
May 07 2016
prev sibling parent reply deadalnix <deadalnix gmail.com> writes:
On Thursday, 5 May 2016 at 18:22:50 UTC, Jack Stouffer wrote:

 This keeps coming up, so in the theme of Andrei's talk and 
 because my day job is a web dev, I decided to do something 
 about it. I have created this tumblr blog which I hope to shape 
 into the official dlang blog: http://officaldlang.tumblr.com/

 A couple of notes:

 1. I choose tumblr because we really shouldn't reinvent the 
 wheel here with something as simple as a blog. Tumblr has 
 thousands of servers, solid funding, solid uptime, and a simple 
 interface.
 2. Tumblr supports markdown
 3. Tumblr gives complete access to its templating engine, 
 allowing you to make the site look like what ever you want
 4. Tumblr allows for custom domains, so if everyone here likes 
 this idea then I can have the domain of the blog be 
 blog.dlang.org
 5. Any core team members who ask for access to the blog via an 
 email to me will get it automatically


Please no tumblr.
May 08 2016
next sibling parent reply Steven Schveighoffer <schveiguy yahoo.com> writes:
On 5/8/16 9:12 AM, deadalnix wrote:

 On Thursday, 5 May 2016 at 18:22:50 UTC, Jack Stouffer wrote:

 This keeps coming up, so in the theme of Andrei's talk and because my
 day job is a web dev, I decided to do something about it. I have
 created this tumblr blog which I hope to shape into the official dlang
 blog: http://officaldlang.tumblr.com/

 A couple of notes:

 1. I choose tumblr because we really shouldn't reinvent the wheel here
 with something as simple as a blog. Tumblr has thousands of servers,
 solid funding, solid uptime, and a simple interface.
 2. Tumblr supports markdown
 3. Tumblr gives complete access to its templating engine, allowing you
 to make the site look like what ever you want
 4. Tumblr allows for custom domains, so if everyone here likes this
 idea then I can have the domain of the blog be blog.dlang.org
 5. Any core team members who ask for access to the blog via an email
 to me will get it automatically


 Please no tumblr.


Yes, why not some dogfood? https://github.com/Dicebot/mood

https://forum.dlang.org/post/ujpnaipcixdeiauskago forum.dlang.org

-Steve
May 08 2016
parent Jack Stouffer <jack jackstouffer.com> writes:
On Sunday, 8 May 2016 at 09:48:04 UTC, Steven Schveighoffer wrote:

 Yes, why not some dogfood


Convenience mostly.

As I have pointed out earlier, by going with an external 
solution, we get several things out of the box like:

* multiple authors with permissions without replying on the slow 
PR system
* no need to worry about server logistics
* a simple interface for writing/editing posts
* ability to write posts in markdown, a WYSIWYG editor, or in raw 
HTML
* ability to create posts of different types with automatic 
styling and embedding, e.g. 
https://officialdlang.tumblr.com/post/143954431089/andrei-appears-on-cpp-cast-to-talk-about-the
* the guest posting system which I have already explained
* a tagging system
* etc.

I'm not saying that no one else offers these, it's just that we 
can have a blog TODAY with a very minimal amount of effort. Also, 
the barrier to writing a post to the blog should be as low as 
humanly possible in order to let non-web people contribute posts.
May 08 2016
prev sibling parent reply Jack Stouffer <jack jackstouffer.com> writes:
On Sunday, 8 May 2016 at 07:12:10 UTC, deadalnix wrote:

 Please no tumblr.


Please elaborate.
May 08 2016
next sibling parent deadalnix <deadalnix gmail.com> writes:
On Sunday, 8 May 2016 at 14:29:33 UTC, Jack Stouffer wrote:

 On Sunday, 8 May 2016 at 07:12:10 UTC, deadalnix wrote:

 Please no tumblr.


 Please elaborate.


It is mostly used for shitposting memes, playing professional 
victims and porn. The very best place when you want to advertise 
yourself as serious.
May 08 2016
prev sibling parent tired_eyes <pastuhov85 gmail.com> writes:
Static generator assumes there wouldn't be any comment system for 
blog entries? At least a link to the corresponding forum topic, 
line phoronix.com?
As of Tumblr, does it allow for arbitrary domain name? 
whatever.tublr.com looks a bit unpresentably. blog.dalng.org 
definitely would be better.
Last, dlang don't want to go with Github and prefer self-hosted 
Bugzilla to avoid dependency on 3rd party, same goes for Tumblr.
May 30 2016