Moved 'How-tos/D for Win32' to wiki

[JinShil]

This is a test pull. I think it would be best to move the How-tos to the wiki. This is the first, and if it is accepted, I'll move the other How-tos.

Motivation:

• Elicit more community involvement in updating the documentation.
• Updating the wiki is easier than submitting pull requests.
• DLang.org changes are not immediate, the wiki is. Instant gratification is good.
• Having these How-tos on dlang.org implies that the core D effort is maintaining it. I doubt this is the case, and I think the community as a whole could do a better job anyway. In fact, I'm skeptical the example in this how-to even still compiles.

If this pull is accepted, I'll move the other how-tos to here: http://wiki.dlang.org/Tutorials

The new location of this specific how-to is here: http://wiki.dlang.org/D_for_Win32

[JinShil]

I'm not sure if you all are not interested in this change, or you are waiting on some prerequisite. Please let me know either way. If I don't hear anything in a few days, I will close this pull.

[ghost]

You've moved it to the wiki but you simply deleted the existing page and haven't linked to the new wiki. windows.html should still exist but either auto-redirect to the wiki page or display a link to it.

Let's see what others think about moving to the wiki: @yebblies @9rnsr @CyberShadow @WalterBright

[yebblies]

Moving to the wiki sounds like a good idea.

[9rnsr]

Looks good.

[JinShil]

You've moved it to the wiki but you simply deleted the existing page and haven't linked to the new wiki. windows.html should still exist but either auto-redirect to the wiki page or display a link to it.

The idea here is to have the "How-tos" link to go directly to http://wiki.dlang.org/Tutorials when the other HowTos are moved. For that reason, I didn't add a link to this particular HowTo. However, if I make windows.html redirect to the wiki temporarily until the others are moved, will you merge this pull?

[JinShil]

Clicked the wrong button. Didn't mean to close.

[CyberShadow]

Existing links should not be broken without a very good reason. There will be many places on the web linking to the old location of the articles. Simply displaying a 404 at the old location is not acceptable.

[JinShil]

Existing links should not be broken without a very good reason. There will be many places on the web linking to the old location of the articles. Simply displaying a 404 at the old location is not acceptable.

I'll have it be known that decrementing/changing syntax in the compiler and leaving it to the reader to figure it out and submit pulls to fix the docs is equally unacceptable.

Nevertheless, I agree with you, and I'll make windows.html display a link to the wiki and submit the changes today.

[Infiltrator]

That's what 301s are for. :)

https://en.wikipedia.org/wiki/HTTP_301

[CyberShadow]

I don't think we have any control over the server configuration. The existing redirects use the HTTP meta tag method.

[Infiltrator]

Oh. Who owns and/or controls the server, then? I thought that it Walter vel al?

[ghost]

I'll have it be known that decrementing/changing syntax in the compiler and leaving it to the reader to figure it out and submit pulls to fix the docs is equally unacceptable.

What are you refering to?

[JinShil]

What are you refering to?

I refer you to:
http://forum.dlang.org/post/zbiagarsexwoabesrkzy@forum.dlang.org
http://forum.dlang.org/post/ld1kbv$lo6$1@digitalmars.com

Then I refer you to:
http://forum.dlang.org/post/zqnvjqjqyxzlkcumynnz@forum.dlang.org

Then, take a look at my previous pull requests. And finally, try to compile the example in this very pull request.

That should give you enough context.

It made me chuckle to see that a broken link is considered unacceptable, but leaving documentation to "those who actually need them done" (i.e. the reader) is not.

I just want to keep the next reader from experiencing my misfortune. Now you probably understand the motivation for my pulls.

[ghost]

It made me chuckle to see that a broken link is considered unacceptable, but leaving documentation to "those who actually need them done" (i.e. the reader) is not.

No, I care about both. However improvements are entirely based on user contributions such as the ones you're making. Things won't get fixed until someone steps up and fixes them, it's as simple as that. :)

[JinShil]

No, I care about both.

Your actions speak louder than your words. I thank you.

However improvements are entirely based on user contributions such as the ones you're making. Things won't get fixed until someone steps up and fixes them, it's as simple as that.

I understand that and don't object to the fact that this project requires community participation or that I've had to do a few minor edits. I was merely pointing out the irony of the comments made on the forum and the comments made on this pull. Anyway, I've had my say.

I've made the necessary updates to ensure windows.html will display a link to the wiki. It will not redirect because the parent "How-Tos" node links to this page, and it may throw the user off if they are taken automatically to the wiki without giving them a chance to see the other "child" howtos. Click the parent "How-Tos" link on dlang.org to see what I mean.

I guess I'll do the same for the other howtos to avoid 404's, unless someone has another idea.

[CyberShadow]

Redirecting to the wiki is fine, IMO. Some day we'll have a dlang.org skin so it'll look more like a part of the D website.

[ghost]

Posted in NG to get more attention: http://forum.dlang.org/thread/mailman.249.1393157192.6445.digitalmars-d@puremagic.com

[ghost]

Thanks @JinShil.