Decide how to work on this resource about diveintohtml5 HOT 6 CLOSED

There could also be contributing file.

from diveintohtml5.

In my ideal world, this would be both historical and up-to-date.

Example of a perfect changeset, in my mind: #12

from diveintohtml5.

Agreed. That's perfect because it does little to change the existing text. It's easy because it doesn't change the direction of the language, it only updates the data. With data changes, it only gets difficult if the remark was "IE is bad because it doesn't support X" and then IE starts supporting X. We would be forced to concede that the text should either indicate that IE is now good, or that it should removed entirely.

Another issue. At some point, there will be more HTML5 technology, like image sets, to add. I would think we should not avoid these unexplored topics. Therefore, we would be writing our own sentences about them. What do you think?

from diveintohtml5.

Just came across something like this while making the PR for #69 and I think part of the issue is that there's no README.mkdown for the repo, which would help get some of how to approach questions that I had like:

Mark wrote in conversational style, which is why it's all so readable, should we emulate that? What if we suck at emulating that approachable & readable writing style? ( : D )
What about images; many of the images used are black and white, and have that old-timey-clip-art feel to them, what kind of images make sense? (I just ended up skipping the images because they felt so out of place).
How do people generally end up editing this raw html, is there a consistent tool that will simplify this process? (I ended up editing the raw html, which was a PITA with all the code h1 br span /span /h1 /code html elements)

I think that a README.mkdown would be a good place to at least start being able to clarify stuff like that.

from diveintohtml5.

There could also be contributing file.

Before there can be a contributing file I'd say the project should either be cross-linked or merged with the fork from @jonathantneal. I see commits from Irish in here so I'm going to suggest @jonathantneal subs a pull with one commit per section and we all take a stab at reviewing then address the URL issue I just opened with #92. This is a great resource – I'm happy to help review.

from diveintohtml5.

@jhabdas afaik this repo is up to date with jonathan's fork.

closing this issue as the repo is in a state of low-maintenance.

from diveintohtml5.