But the articles could contain example code, using Allegro.

Well it's true, but I think if it's an article about programming and is using Allegro in the example, since it's related to programming stuffs should be ease to convert it by the reader to use it with other version of Allegro and even other library.

Programming Example:

In this example we're going to show you how to create a class and then use an array of object to display 300 instance of and object that is going to draw a bitmap into the screen randomly.

Here we're talking about classes, arrays and programming stuff, and the al_draw_bitmap function that can be easily modified by the user with any other function which can do the same.

Game Design Concept Example:

In this example we're going to show you how to use events to separate logic from drawing and make a ball bouncing to see the differences when modifying the Logic per second nor the frames per second.

In this case Allegro 5 is obligatory to follow that example, and Allegro 4 is not able to do this job. But even thought by seeing some tutorials even if is not related to allegro 4 nor allegro 5 you may get an idea, for that reason I did this: http://wiki.allegro.cc/index.php?title=Category:Game_Design_Concepts

Allegro 5 Tutorial Example:

In this example we're going to show you how to use the Allegro UTF-8 string routines so you can handle UTF-8 strings easily.

So...
- Programming: can be used with all version of Allegro
- Game Design: might or might be not use with all version of Allegro
- Allegro Tutorials: are strictly related to eache version.

What you think?

Yes its' true, each article have an average of reusability.

Article related to:                Average reusability

Programming                        High
Game design C.                     Middle
Allegro 5/4 Tut.                   Low

If we split this sections we can link to them in any different current version of Allegro, and future versions too. And put them together so if no Article is made to an specific version of Allegro, users are going to see if that article was made for Allegro4/5/6/7/8 without need to go inside each "Allegro 4/5/6..." tutorials.

Let's see, if for example I create an article about how to create a Mario Bros clone.

I think would be in the Game design concept section, but I need to specified that I'm using Allegro 5 nor Allegro 4. Other people which are using Allegro 7 (year 2013), can see it and learn from that article even is they're not able to just copy and paste.

That is an article that use intensively Allegro 5, but for example collision detection which is generic, can be linked in each version of Allegro.

So for example I say "let's see if there is an article about physics"

I go to: Allegro 5 > Game design concepts, and shows me the articles made for allegro 5, if I can't find what I'm looking for, I scroll down to see if that articles was made for Allegro 4, and if is there at least I have something.

{"name":"603566","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/3\/f\/3f2cb80c935b784123743f063605d095.jpg","w":520,"h":616,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/3\/f\/3f2cb80c935b784123743f063605d095"}

Other way will be, to have only two version in the wiki, we have currently 4 and 5, then we can have 5.0 and 5.2, in that case what we would have to do is move the articles to each corresponding section, but still specifying that those articles were made with older version of allegro. I don't like this idea because I think is better to have all the documentation online even if is a super old version. But at some point we'll have to remove it anyway. And also because it give us more work.

Hey what if we did one of these:

{"name":"603570","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/d\/f\/dfec8b400dd607cd028a7bfa562cb075.png","w":395,"h":81,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/d\/f\/dfec8b400dd607cd028a7bfa562cb075"}

Since we're trying to push people into Allegro 5 and Allegro 4 is considered legacy, I don't think it would be a bad idea to keep new people from being confused.

Quick note on that. I chose that verbiage because:

1. it isn't "This article was written for Allegro 4" which may imply that we would need to add a "This article was written for Allegro 5." It's unique to Allegro 4 articles.

2. it weakly discourages Allegro 4 by calling it "older"

3. it explains that the warning is to specifically address compatibility, as not to infer that it the article is "outdated" and/or needs to be revised. This also weakly implies prioritizing the use of Allegro 5.

I think it would be best to just keep it as one "Bounding Box" page, and have both the A4 and A5 examples in the same article. The main emphasis for something like that should be the theory, not the code.

That would happen automatically if that page just lists everything with the category.

Nice work man. Looks great.

Only weird thing is the edit buttons. They look out of place and too visible.

Otherwise ... when can we have it!?

It's looking awesome. Thank you for the work that you're doing, Mark.

Woow man that is just brilliant! That's a Wiki!, I'm short of time right now but I'll be back!

Please let us know when is completely ready.

What for?

It is up, in use, and ready to be enjoyed.

Using it today I'll want to make a few changes to the content paragraph spacing, they feel a little congested. Maybe another thing or two. But yea, it's "done" but will have a few "patch updates" here and there.

Also, I created a new article Allegro - A Game Programming Library. So now we have three distinct ports. That main article, and then the specific articles for Allegro 4, and Allegro 5.

So Er'body Get on That Wiki, I wanna see that Recent Changes page humming along.

Hmm ... an Allegro 5 Trivia game? That's not a bad idea! Totally nerdy, but incredibly useful!

Same here, except I took a break to make progress on my game. I need to finish up my MSVC 2010 tutorial, and some intersection/collision articles.

Mark Oates: I hate to bother you, but there is a slight bug. I updated my MSVC 2010 + Allegro 5 tutorial with a bunch of shiny screenshots They're put into right-side thumbnails. However they don't show up correctly, at least in Chrome on Windows. They don't stay within the confines of their section; they just all lump together on the right.

I hope it can be fixed. The tutorial page looks crazy as-is