Skip to content
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.

Added Frequently Asked Questions Page #202

Closed
wants to merge 42 commits into from
+1,238 −0
Closed

Added Frequently Asked Questions Page #202

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
42 commits
Select commit Hold shift + click to select a range
9d80dad
Added FAQ
Sep 1, 2015
bea69ad
Updated FAQ
Oct 22, 2015
596d92c
Cleanup
Oct 22, 2015
a532931
Corrections
Oct 23, 2015
b782659
Updated FAQ based on Diggsey's suggestions
Oct 24, 2015
e94751d
Addressing feedback
Nov 6, 2015
9646f3f
More corrections
Nov 15, 2015
756a5d2
Added answer for Rust versioning
Nov 15, 2015
2aad0da
Add another answer
Nov 15, 2015
a3c9d13
Mobile style improvements
Nov 15, 2015
5f458fb
Removed copyright notice
Nov 18, 2015
5c1409b
Removed list of companies using Rust
Nov 18, 2015
5a66ed8
Some additional cleanup and review
Nov 18, 2015
dbd997b
Organized sections
Nov 18, 2015
57f72c5
Simplified CSS
Nov 18, 2015
d718d7c
Updating answers
Nov 20, 2015
57f62ac
Addressed latest round of feedback
Dec 16, 2015
fabd2ba
Take a pass over the whole FAQ
brson Dec 20, 2015
8b3265f
Fix alignment of operator table in FAQ
brson Dec 20, 2015
dc0774d
Merge pull request #1 from brson/faq
AndrewBrinker Jan 3, 2016
0ef5d23
Fixed typos
Jan 3, 2016
9da71ec
Updated answer about higher-kinded type support
Jan 3, 2016
20c365f
Clarified answer on Ord/PartialOrd and Eq/PartialEq split
Jan 3, 2016
095d45c
Updated borrow checker answer
Jan 3, 2016
7721973
Typo fixes
Jan 3, 2016
435b1de
Addressed charlotteis' suggestions
Jan 3, 2016
601a473
Small fixes
Jan 3, 2016
ef9715a
Changed to 4-space indent in code samples
Jan 3, 2016
123c803
Updated based on tshepang's latest feedback
Jan 4, 2016
1c3a038
More corrections based on tshepang's feedback
Jan 4, 2016
3425bdd
Integrated latest feedback from tshepang
Jan 4, 2016
c374cbb
First pass with new feedback
Jan 7, 2016
7ba7f3d
New draft of the higher-kinded types answer
Jan 8, 2016
e7bab64
Partial addition of API doc links
Jan 8, 2016
1594ab3
Fixed based on feedback from pnkfelix
Jan 8, 2016
ffb11a7
Small correction
Jan 8, 2016
ea304ed
Updated based on latest feedback
Jan 9, 2016
8e490bb
Updated ord/eq answers
Jan 9, 2016
6705771
Updated borrow checker answer
Jan 9, 2016
6b75c04
Updated lifetime elision answer
Jan 9, 2016
c4e41f0
Fixed typo
Jan 9, 2016
898dd0f
Added links to API docs
Jan 9, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions _config.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,4 @@
name: The Rust Programming Language
markdown: redcarpet
redcarpet:
extensions: ["tables"]
10 changes: 10 additions & 0 deletions _layouts/faq.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
---
layout: default
---

<link href='https://fonts.googleapis.com/css?family=Source+Serif+Pro:400,600' rel='stylesheet' type='text/css'>

<div class="faq">
{{ content }}
</div>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we not use a custom layout for this? Is the only customization here the copyright disclaimer? If so I feel ok, for now at least, assuming that the copyright declaration on the www repo itself is sufficient.

This is an interesting choice though, and we should consider whether something like it should be done for the entire site.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The custom layout is actually for an interesting reason. Markdown doesn't allow having Markdown embedded in HTML tags, and the <div class="faq"> is used for some custom styling (which may be undesirable, and definitely needs a bit of fine-tuning for mobile). I prefer to write in Markdown, although the file could of course be transitioned to entirely HTML if the extra layout is undesirable.


105 changes: 105 additions & 0 deletions css/style.css
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -383,3 +383,108 @@ ul.laundry-list {
text-align: right;
margin: 5px 10px 0 0;
}

.faq {
border-top: 1px solid #dedede;
margin-top: 2em;
margin-bottom: 8em;
padding-top: 4em;
}

.faq p,
.faq ul,
.faq ol,
.faq blockquote,
.faq pre {
margin: 0 0 1rem;
font-family: "Source Serif Pro";
}

@media screen and (min-width: 820px) {
.faq {
padding-right: 6em;
}

.faq p,
.faq ul,
.faq ol,
.faq blockquote,
.faq pre,
.faq h1,
#toc {
margin-left: 8rem;
}
}

.faq blockquote {
border-left: .25em solid #dedede;
padding-left: 2rem;
}

.faq blockquote p {
margin: 0;
}

.faq h1 {
font-size: 2.5em;
line-height: 1.5em;
margin-top: 0;
margin-bottom: 1rem;
font-weight: 400;
position: relative;
}

.faq h2 {
font-size: 2em;
line-height: 1.5em;
margin: 3rem 0 1rem;
font-weight: 400;
border-top: 4px solid #dedede;
padding-top: 1rem;
}

.faq h3 {
font-size: 1em;
line-height: 1.5em;
font-weight: 500;
margin: 2rem 0 .25rem;
}

.faq pre {
margin-top: 2rem;
margin-bottom: 2rem;
}

.faq code {
display: inline-block;
padding: .1em .2em 0;
font-size: 0.95em;
line-height: 1em;
background-color: #f7f7f7;
border-radius: 2px;
font-weight: 400;
font-family: Consolas, "Andale Mono WT", "Andale Mono", "Lucida Console", "Lucida Sans Typewriter", "DejaVu Sans Mono", "Bitstream Vera Sans Mono", "Liberation Mono", "Nimbus Mono L", Monaco, "Courier New", Courier, monospace;
}

.faq pre code {
font-size: 1em;
line-height: 1.5em;
}

#toc h2 {
border: 0;
font-size: 2rem;
line-height: 1.5em;
}

#toc ol {
margin: 0 0 0 2rem;
padding: 0;
-webkit-columns: 150px 3;
-moz-columns: 150px 3;
columns: 150px 3;
}

.faq table {
margin-left: 8rem;
}
Loading