Extract out homepage.css

This commit is contained in:
Richard Feldman 2022-10-06 23:53:06 -04:00
parent 287cde00cd
commit c9d0ed8490
No known key found for this signature in database
GPG Key ID: F1F21AA5B1D9E43B
2 changed files with 17 additions and 20 deletions

15
www/public/homepage.css Normal file
View File

@ -0,0 +1,15 @@
html {
font-family: sans-serif;
line-height: 145%;
}
li {
margin-bottom: 0.5rem;
}
@media only screen and (min-device-width: 900px) {
body {
width: 900px;
margin: 24px auto;
}
}

View File

@ -8,25 +8,7 @@
<title>The Roc Programming Language</title>
<!-- <meta name="description" content="A language for making delightful software."> -->
<meta name="viewport" content="width=device-width">
<style type="text/css">
html {
max-width: 35em;
margin: 0 auto;
font-family: sans-serif;
line-height: 145%;
}
li {
margin-bottom: 0.5rem;
}
@media only screen and (min-device-width: 900px) {
body {
width: 900px;
margin: 24px auto;
}
}
</style>
<link rel="stylesheet" href="/homepage.css">
<!-- <link rel="icon" href="/favicon.svg"> -->
</head>
@ -97,7 +79,7 @@
<p>Progress towards this performance goal is already quite far along.</p>
<p>Since Roc already uses unboxed data structures that get monomorphized into LLVM—just like Rust,
Zig, and C++ do—in many cases Roc already code compiles to the same machine code that the
Zig, and C++ do—in many cases Roc code already compiles to the same machine instructions that the
equivalent code written in one of these systems languages would. Something we do regularly is
to compare the LLVM instructions generated by Roc's compiler and by these systems languages'
compilers, to check whether we're generating equivalent instructions.</p>