Add introductory paragraph

This commit is contained in:
Nico Burns 2022-04-18 17:40:27 +01:00
parent d665898132
commit 300d8ebaee
2 changed files with 23 additions and 2 deletions

View file

@ -12,23 +12,26 @@ body {
#main-container {
margin: 0;
padding: 0;
margin: 24px;
}
#left-sidebar {
width: 200px;
margin-left: 24px;
}
.toc {
position: sticky;
top: 24px;
}
.toc h3 {
margin-top: 16px;
}
.toc ul {
list-style: none;
padding: 0;
}
.toc li {
padding-left: 0;
margin: 6px 12px;
margin: 6px 0px;
}
.toc li a {
color: #CCC;
@ -84,6 +87,10 @@ h2.page-subheading {
justify-content: flex-start;
}
p.introduction {
color: #666;
}
h3 {
font-size: 1.6em;
font-weight: normal;

View file

@ -26,6 +26,20 @@
<!-- Main page content -->
<div id="content">
<!-- <p class="introduction">
Many programming langauges (such as Python and Go) take a "kitchen sink" approach to their standard libraries, including functionality
like regular expressions, random number generation, serialization (JSON, XML, etc), and HTTP clients and servers directly in the stdlib.
</p> -->
<p class="introduction">
Compared to other programming languages such as Python and Go, Rust's standard library is very small, including only core data structures in the standard library with all other functionality farmed out to 3rd party ecosystem crates, and a common complaint from new Rust developers is that they don't know where to start: which crates they ought to use and which crates they ought to trust.
</p>
<p class="introduction">
This list attempts to answer those questions.
</p>
{% for group in crate_groups %}
<section data-toc-section id="section-{{ group.slug }}">
<h3>{{ group.name }}</h3>