On Tuesday, 14 May 2019 at 07:47:36 UTC, Bastiaan Veelo wrote:
>> Apologies if this question has been asked before. Is there a reason why the spec cannot be written in something like RestructuredText or Markdown? I ask because github natively supports these formats, which makes it easier / more productive.
>>
> All of dlang.org (as far as I can see) is written in ddoc, the D embedded documentation format https://dlang.org/spec/ddoc.html. It produces output in various formats, not just HTML. If you don’t want to set up your local build of the website, then you can still make the pull requests and inspect the results as built by the testing bots that will be accessible from the PR page. While you are iterating, you may want to prepend your PR title with “[WIP]”.
>

Thank you for the tips.

I am happy to work with ddoc but it seems unnecessary friction.

Regards

On Tuesday, 14 May 2019 at 08:41:53 UTC, Dibyendu Majumdar wrote:
> On Tuesday, 14 May 2019 at 07:47:36 UTC, Bastiaan Veelo wrote:
>>> Apologies if this question has been asked before. Is there a reason why the spec cannot be written in something like RestructuredText or Markdown? I ask because github natively supports these formats, which makes it easier / more productive.
>>>
>> All of dlang.org (as far as I can see) is written in ddoc, the D embedded documentation format https://dlang.org/spec/ddoc.html. It produces output in various formats, not just HTML. If you don’t want to set up your local build of the website, then you can still make the pull requests and inspect the results as built by the testing bots that will be accessible from the PR page. While you are iterating, you may want to prepend your PR title with “[WIP]”.
>>
>
> Thank you for the tips.
>
> I am happy to work with ddoc but it seems unnecessary friction.
>
> Regards

I have some good news: starting with the 2.086 release, Ddoc supports markdown via the experimental -preview=markdown flag and the plan is to enable it soon for dlang.org.

On Tuesday, 14 May 2019 at 09:14:16 UTC, Seb wrote:
> I have some good news: starting with the 2.086 release, Ddoc supports markdown via the experimental -preview=markdown flag and the plan is to enable it soon for dlang.org.

That's great. I look forward to when this will be enabled, in the meantime I will work with the ddoc format.

Regards

On Tuesday, 14 May 2019 at 07:47:36 UTC, Bastiaan Veelo wrote:
> All of dlang.org (as far as I can see) is written in ddoc, the D embedded documentation format https://dlang.org/spec/ddoc.html. It produces output in various formats, not just HTML. If you don’t want to set up your local build of the website, then you can still make the pull requests and inspect the results as built by the testing bots that will be accessible from the PR page. While you are iterating, you may want to prepend your PR title with “[WIP]”.
>

I tried the workflow suggested above. Unfortunately it takes very long for the build (why?),  so it is not very practical to work this way.

Regards

On 5/14/19 11:35 AM, Dibyendu Majumdar wrote:
> On Tuesday, 14 May 2019 at 07:47:36 UTC, Bastiaan Veelo wrote:
>> All of dlang.org (as far as I can see) is written in ddoc, the D embedded documentation format https://dlang.org/spec/ddoc.html. It produces output in various formats, not just HTML. If you don’t want to set up your local build of the website, then you can still make the pull requests and inspect the results as built by the testing bots that will be accessible from the PR page. While you are iterating, you may want to prepend your PR title with “[WIP]”.
>>
> 
> I tried the workflow suggested above. Unfortunately it takes very long for the build (why?),  so it is not very practical to work this way.

What I do is just build the "html" target while iterating.

On Tuesday, 14 May 2019 at 17:10:13 UTC, Andrei Alexandrescu wrote:
> On 5/14/19 11:35 AM, Dibyendu Majumdar wrote:
>> On Tuesday, 14 May 2019 at 07:47:36 UTC, Bastiaan Veelo wrote:
>>>[...]
>> 
>> I tried the workflow suggested above. Unfortunately it takes very long for the build (why?),  so it is not very practical to work this way.
>
> What I do is just build the "html" target while iterating.

Yep, you can even add a bit of parallelization to make it faster:

$ cd ~/dlang/dlang.org
$ make -f posix.mak html -j20