Ingvar Stepanyan

> But we should mark them properly as such. I think there's a value in moving them to a subfolder or something so that people who come across the repo...

> Not everybody is prepared to dig through git logs to find documents. Sure, but a counter-argument can be that not everyone will need them. Given that latest version of...

> Don't assume that everybody coming to this site for information knows their way around git or GitHub. ;) Ha, I definitely assumed that. If not, we can include a...

> we've always decided to keep them as-is, both for historical reasons and due to incoming links Right, I guess that's the main blocker for all other discussions / decisions....

Right, sorry, I meant *this* repo (`design`). But thanks anyway :D

Basically, as a maintainer, you should be able to go to https://github.com/WebAssembly/design/graphs/traffic and see basic stats on which Markdown docs are opened, which sites people are coming from to the...

Ok, sounds like moving to a subfolder is the best compromise that we can all agree on. Would someone want to either make a PR or help me with identifying...

@binji Primary reason for me is that webassembly.org uses list of Markdown files in this repo to populate Docs. I'm currently split between two approaches to modernizing it: I can...

How about things like "Portability", "Security" and "Nondeterminism in WebAssembly" and perhaps "Use Cases"? These seem still relevant, but if they are out of date, are there better resources to...

@mathiasbynens I see a bit of flickering when scrolling through the `after.html` demo, at least while it's loading - is this expected?