working on the website

Ary Borenszweig ary at
Mon Jul 15 06:12:38 PDT 2013

On 7/14/13 6:18 PM, Val Markovic wrote:> 3. Ruby on Rails (or Django or 
any other web framework that dynamically
> builds a server response) would be a terrible choice for a static
> website. It would be nothing but overhead for no benefit. Nothing on
> <> is dynamically generated, nothing talks to
> a database (nor should it). The site can and should be generated from
> some simple markup language. The end result should be HTML, CSS, JS and
> image files that are then just served by the simplest of servers. For
> these types of sites, the industry standard is quickly becoming to serve
> the files directly out of Amazon S3 with a CDN (like CloudFlare) in
> front of it. The end result is an incredibly fast browsing experience
> because everything is just served directly out of the CDN edge servers
> without any kind of dynamic response generation. Requests come in for
> files and the CDN just echoes them out of memory to the network.

You can also try GitHub pages. And since D already has its code in 
github it's very simple.

It generates a static site from a bunch of files. Under the hood it uses 

It also comes with automatic blogging support, which would be a nice 
thing for D (having an official D blog reporting new, awesome stuff, 
anouncing new releases, etc., instead of relying on people to suscribe 
to the newsgroup).

If Walter wants to modify the copyright notice, he could modify the file 
_includes/copyright.html. No need to search for a macro named copyright.

If he wants to highlight D code, he can do:

{% highlight d %}
void some_code() {
{% endhighlight %}

because GitHub already colors D code.

More information about the Digitalmars-d mailing list