Hi,

I'm in the process of switching over the gdcproject.org sources over from html [sic] to markdown format to allow ease of editing.

Currently I am using just a generic markdown script to generate the static webpages (ie: Markdown.pl) - though I hear that vibe.d supports markdown, so it may be an opportunity to get gdc/vibe.d hooked up and running the gdcproject.org site. :-)

There's also in the works a /news site with will be a kinda like blog of all things gdc-related.  Again in markdown and this time using Chronicle to compile the pages (maybe end up writing a version in D if I get round to it).


Pretty much all html files are easily translatable, given that the way I wrote the pages are very basic to begin with.  Only one that is somewhat complex is the downloads page, which I'm told is generated by another script.  ;)

Johannes, does this affect things you are doing?


Regards
Iain

Am Wed, 11 Jun 2014 09:24:04 +0000
schrieb "Iain Buclaw" <ibuclaw@gdcproject.org>:

> Hi,
> 
> I'm in the process of switching over the gdcproject.org sources over from html [sic] to markdown format to allow ease of editing.
> 
> Currently I am using just a generic markdown script to generate the static webpages (ie: Markdown.pl) - though I hear that vibe.d supports markdown, so it may be an opportunity to get gdc/vibe.d hooked up and running the gdcproject.org site. :-)

Great! Markdown rocks, although github-flavored markdown is a great improvement over plain markdown.

> 
> There's also in the works a /news site with will be a kinda like blog of all things gdc-related.  Again in markdown and this time using Chronicle to compile the pages (maybe end up writing a version in D if I get round to it).
> 
> 
> Pretty much all html files are easily translatable, given that the way I wrote the pages are very basic to begin with.  Only one that is somewhat complex is the downloads page, which I'm told is generated by another script.  ;)
> 
> Johannes, does this affect things you are doing?

As long as I can keep the downloads page as html there's no problem ;-)

If you want the download page in markdown as well I'll have to port the mustache template[1] to markdown. I guess that could work, but I'd probably have to use html for the tables anyway.

[1] https://github.com/jpf91/gdc-build-configs/blob/master/downloads.mustache

On 11 June 2014 10:40, Johannes Pfau via D.gnu <d.gnu@puremagic.com> wrote:
> Am Wed, 11 Jun 2014 09:24:04 +0000
> schrieb "Iain Buclaw" <ibuclaw@gdcproject.org>:
>
>> Hi,
>>
>> I'm in the process of switching over the gdcproject.org sources over from html [sic] to markdown format to allow ease of editing.
>>
>> Currently I am using just a generic markdown script to generate the static webpages (ie: Markdown.pl) - though I hear that vibe.d supports markdown, so it may be an opportunity to get gdc/vibe.d hooked up and running the gdcproject.org site. :-)
>
> Great! Markdown rocks, although github-flavored markdown is a great improvement over plain markdown.
>
>>
>> There's also in the works a /news site with will be a kinda like blog of all things gdc-related.  Again in markdown and this time using Chronicle to compile the pages (maybe end up writing a version in D if I get round to it).
>>
>>
>> Pretty much all html files are easily translatable, given that the way I wrote the pages are very basic to begin with.  Only one that is somewhat complex is the downloads page, which I'm told is generated by another script.  ;)
>>
>> Johannes, does this affect things you are doing?
>
> As long as I can keep the downloads page as html there's no problem ;-)
>
> If you want the download page in markdown as well I'll have to port the mustache template[1] to markdown. I guess that could work, but I'd probably have to use html for the tables anyway.
>
> [1] https://github.com/jpf91/gdc-build-configs/blob/master/downloads.mustache
>

Yah, I'd probably want to avoid using too many technologies in one tree if possible.  We should move to merge in your moustache changes into the main gdcproject pages though...  Maybe wrap it all into a *cough* makefile.

On Wednesday, 11 June 2014 at 09:24:05 UTC, Iain Buclaw wrote:
> Hi,
>
> I'm in the process of switching over the gdcproject.org sources over from html [sic] to markdown format to allow ease of editing.
>
> Currently I am using just a generic markdown script to generate the static webpages (ie: Markdown.pl) - though I hear that vibe.d supports markdown, so it may be an opportunity to get gdc/vibe.d hooked up and running the gdcproject.org site. :-)
>

Actually, I went straight for vibe.d, because it was the path of least resistance for mixing in html templates with markdown - plus, since I've recently [1][2] (re)fixed dub and vibe.d with the update to 2.065, thought it was best to plough through it in a day while it was still fresh on TODO my list.

All contents have been converted.  Just improving some parts of the documentation page, and then will begin testing for real.

/news is still in the works, I have an idea how to manage that in vibe.d.

Regards
Iain.

On Sunday, 15 June 2014 at 11:28:22 UTC, Iain Buclaw wrote:
> On Wednesday, 11 June 2014 at 09:24:05 UTC, Iain Buclaw wrote:
>> Hi,
>>
>> I'm in the process of switching over the gdcproject.org sources over from html [sic] to markdown format to allow ease of editing.
>>
>> Currently I am using just a generic markdown script to generate the static webpages (ie: Markdown.pl) - though I hear that vibe.d supports markdown, so it may be an opportunity to get gdc/vibe.d hooked up and running the gdcproject.org site. :-)
>>
>
> Actually, I went straight for vibe.d, because it was the path of least resistance for mixing in html templates with markdown - plus, since I've recently [1][2] (re)fixed dub and vibe.d with the update to 2.065, thought it was best to plough through it in a day while it was still fresh on TODO my list.
>
> All contents have been converted.  Just improving some parts of the documentation page, and then will begin testing for real.
>
> /news is still in the works, I have an idea how to manage that in vibe.d.
>

[1] https://github.com/D-Programming-GDC/GDC/commit/118678441cc18c447f1580fe17627e957dd29f70
[2] https://github.com/D-Programming-GDC/GDC/commit/6090d4bffdb5052c5949fd2fcf787baa8c2073ef

On 15 June 2014 12:28, Iain Buclaw via D.gnu <d.gnu@puremagic.com> wrote:
> On Wednesday, 11 June 2014 at 09:24:05 UTC, Iain Buclaw wrote:
>>
>> Hi,
>>
>> I'm in the process of switching over the gdcproject.org sources over from html [sic] to markdown format to allow ease of editing.
>>
>> Currently I am using just a generic markdown script to generate the static webpages (ie: Markdown.pl) - though I hear that vibe.d supports markdown, so it may be an opportunity to get gdc/vibe.d hooked up and running the gdcproject.org site. :-)
>>
>
> Actually, I went straight for vibe.d, because it was the path of least resistance for mixing in html templates with markdown - plus, since I've recently [1][2] (re)fixed dub and vibe.d with the update to 2.065, thought it was best to plough through it in a day while it was still fresh on TODO my list.
>
> All contents have been converted.  Just improving some parts of the documentation page, and then will begin testing for real.
>
> /news is still in the works, I have an idea how to manage that in vibe.d.
>


Raised a pull request to switch gdcproject.org over to vibe.d

https://github.com/D-Programming-GDC/gdcproject/pull/6

Also replace links to wiki.gdcproject.org with wiki.dlang.org.

On 27 June 2014 21:18, Kagamin via D.gnu <d.gnu@puremagic.com> wrote:
> Also replace links to wiki.gdcproject.org with wiki.dlang.org.

It does no harm either way.  The redirect isn't going anywhere. :)

(PS: Raise a PR!)