List of stuff that should go on a markdown site.

[Danack]

One thing we should do is figure out what content we are going to decide to put on the site, so that people can see how useful it would be to have a site that people can actually edit easily.

One of the first things would be the list of stuff to work on page: https://github.com/Danack/RfcCodex/blob/master/project_coordination.md

What else?

[brzuchal]

@Danack actually I think all dev related content could be here and maybe in a future we could serve that under dev.php.net!?

[Danack]

I'm pretty sure there would be resistance to moving the manual to this. Although most people just use the reference on php.net , my understanding is that other people do use the docbook rendering in different ways.

But really, by giving people a list of 'this is the type of stuff we want to make easier for people to edit', it can help define the conversation and build up excitement for doing this.

[brzuchal]

@Danack I wouldn't even touch manual. But for other things like RFC's, and other developer documents it might be worth it