new site

src/site/articles/why-not-bytecode/index.html

Index: src/site/articles/why-not-bytecode/index.html
diff --git a/src/site/articles/why-not-bytecode/index.html b/src/site/articles/why-not-bytecode/index.html
index 5b3c9538ebecc6c2a5d60a4652b8ace98fa92c38..da45b2dcd93ad1dd516ac46e10818334419b2b85 100644
--- a/src/site/articles/why-not-bytecode/index.html
+++ b/src/site/articles/why-not-bytecode/index.html
@@ -136,10 +136,12 @@ Sure, you may minify or do other obfuscation when you deploy, but your core
 iteration loop is fast and easy because the engine for your language runs it
 directly from source.</p>
 
-<aside class="note">You may ask, "but doesn't Dart require an explicit compile step to
+<p>
+  You may ask, "but doesn't Dart require an explicit compile step to
 compile to JavaScript for running in the browser?" Well, yes, but we're talking
 specifically about the native Dart VM here. And we <em>are</em> working to make
-the Dart-to-JavaScript side of things as nice of a development experience as we can. Iteration time matters.</aside>
+the Dart-to-JavaScript side of things as nice of a development experience as we can. Iteration time matters.
+</p>
 
 <h2>Compiling to source</h2>