search

paulirish / w3fools

https://www.w3fools.com/
152 stars 42 forks source link

Community Editing Wiki for revising the core w3fools site text #59

Closed tchalvak closed 10 years ago

tchalvak commented 10 years ago

Hey All,

I created a wiki workspace to allow for editing of the w3fools site text in a more community-friendly way. The objective is to allow the text to be dealt with independently of the html to start, to move towards a very maintainable final site, separate out any highly-likely-to-change things if necessary to maximize maintainability, and encourage growth of the developer community over criticism of w3schools (as per https://github.com/paulirish/w3fools/issues/50 ).

The wiki is here: http://w3foolsremake.pbworks.com/

We ccccoooooould move the content to a github wiki on this repo, but as far as I recall, that's markdown based and will be less easy-to-edit. That has it's pros and cons, it's nice and relaxing to be able to just do stuff via a wysiwyg wiki like pbworks at the early stage, but people having to create an account on pbworks to edit is also a turn-off. Conversely, markdown probably takes more work, but everyone who comes across this issue is likely to have a github account already. Oh, and I believe we'll need the admin of the wiki to go through the steps of opening up a wiki on the repo or something annoying like that.

I'll start a separate issue for discussion of how to approach the site look/theme/retheming.

537 commented 10 years ago

This looks good. Although, I think W3Schools should change or have more information about coding and such that are helpful - Not just update the old one to a similar new one with little changes.

Garbee commented 10 years ago

@537 We can't really change W3Schools beyond what they have already done (which is add the report issue form.) They are making business choices, the only thing the community can do is warn against them and recommend other resources which are open and well respected.

Garbee commented 10 years ago

If the core text needs to be changed, people can fork the repo and make PRs.

tchalvak commented 10 years ago

Mmmm, the whole point of a wiki is to provide a simple mechanism for those without a clear/complex understanding of html to make changes. Trying to making a mass of changes within the html format just lends itself to a high level of complexity to make what should be simple changes.

Garbee commented 10 years ago

And the people commenting about W3Schools information should understand HTML fairly well. Which makes a wiki style setup in fact useless for us since understanding HTML should be a qualifier to be able to make a change to W3Fools.

renoirb commented 10 years ago

Disclaimer: I work for the W3C and work full time on WebPlatform.org.

If such a wiki is there only to pick on W3Schools, there are more positive ways than that. Maybe you could participate to an already started community that is independent from any browser vendor but funded by a group of vendors that are also part of the ecosystem. There is such a community; WebPlatform Docs. There is another similar and well established community, Mozilla Developer Network. As for tutorials and documenting the best (or mordern) way, I started htmlcsstherightway.com but haven’t got time to work on it. I preferred to contribute to WebPlatform when I heard of it.