ADadamschwartz·Aug 22, 2025
That general structure looks somewhat like Edward Tufte’s work.
https://edwardtufte.github.io/tufte-css/
https://github.com/edwardtufte/tufte-css
In The Block Stacking Problemedwardtufte
tufte-css
HTML2015–2025
edwardtufte / tufte-css
tufte-css
Style your webpage like Edward Tufte’s handouts.
13Distinct people
16Mentions
0Explicit recommenders
6.6KGitHub stars
What to know before exploring
What it is
Style your webpage like Edward Tufte’s handouts.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year16 dated mentions
Observed mentions: 2015-08-05 19:52:06 UTC to 2025-08-22 15:41:15 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
16 sourcesI don't think it is. In Tufte CSS, sidenotes are implemented using float: right [1], while here CSS Grid is used instead.
[1]: https://github.com/edwardtufte/tufte-css/blob/957e9c6dc3646a...
In Beating the L1 cache with value speculation (2021)Glad you like them :D They come from the tufte-css project -
https://github.com/edwardtufte/tufte-css
In Organizing OpenStreetMap mapping partiesAs it is often said in various designer forums, please avoid pure white (#FFFFFF) on black (here #111111), as it makes the text glow for the human eyes (therefore making it unreadable for long text). Instead, try to lower a bit the contrast on the text color.
Also, the dispositions for the buttons at the beginning (GitHub, NPM, ...) are not adjusted correctly for keyboard navigation (each button requires two tabs).
Appart from that, I do like a minimalist stylesheet, so I will also recommend Tufte CSS [0] for readers.
[0]: https://github.com/edwardtufte/tufte-css
In Concrete.cssed - oh, I'm so wrong below.
> "If you see anything that Tufte CSS could improve, we welcome your contribution in the form of an issue or pull request on the GitHub project: tufte-css. Please note the contribution guidelines."
lol@ me. It was right there, at the top.
https://github.com/edwardtufte/tufte-css
- - -
I don't think it relies on Github to purvey the files. I think it just encourages you to view source and grab the files yourself, old-school style, which sort of makes sense in context...
> "To use Tufte CSS, copy tufte.css and the et-book directory of font files to your project directory, then add the following to your HTML document’s head block:
<link rel="stylesheet" href="tufte.css"/>
Now you just have to use the provided CSS rules, and the Tufte CSS conventions described in this document. For best results, View Source and In
Read the rest
spect Element frequently."
This is the tufte-css, with some modifications.
Raw css is here: https://github.com/edwardtufte/tufte-css
My additions on top (and all other source) here: https://github.com/sulami/sulami.github.io/tree/develop/css
In Restarts in Common LispIt'll be nice to simplify underline links tremendously once that becomes implemented in IE/Edge & Safari. The existing methods for avoiding underlines overlapping text descenders like Tufte-CSS's method (https://github.com/edwardtufte/tufte-css) are kinda crazy looking, and also cause the occasional bug with text highlighting.
In Firefox 70This is a really nice looking stylesheet. I'd almost certainly use it the next time I needed to share some content, but unfortunately it has some pretty janky FOUT and FOIT issues for me here in Australia. I'm no CSS guru, so the best I can really do is to report: https://github.com/edwardtufte/tufte-css/issues/119
In Tufte CSSI agree regarding the example document. It's been troubling, because the fact of the matter is that those headings are legitimate, it's just that there's a mismatch between the goals of the description document and the goals of the kinds of documents that Tufte CSS is best suited for. I agree strongly with your idea of making several sample documents to experiment with. See https://github.com/daveliepmann/tufte-css/issues/26
I'll try to look into your points about leading, text size, and so on, but it would help a lot more if you could open a GH issue for them. As I've noted elsewhere in this thread, a real italic font has been added, and I'm considering what to do about small caps. To me it doesn't look so bad as-is.
I don't want Tufte CSS to look like a nicely typeset book, and it would take a lot to convince me to indent the first line
Read the rest
of new paragraphs. I find that repulsive on the web.
Your last paragraph is gold. I wrote something similar about the table style earlier today. For me, I think this project is an exercise in making style choices using a rough template as a guiding star. I too worry that others will focus more on the finger than that star it is pointing at, by slapping this on top of existing content and calling it a day.
At the moment I think sparklines are outside the scope of this project. However:
https://github.com/daveliepmann/tufte-css/issues/22
In Tufte CSSI feel your pain. I think Linjie Ding's contribution resolved the issue, let me know your thoughts: https://github.com/daveliepmann/tufte-css/pull/8
In Tufte CSSThanks for the input. This spurred me to make some changes to tables: https://github.com/daveliepmann/tufte-css/commit/c46b8b516a0...
In Tufte CSSI agree.
It looks like sidenotes are floated right and given negative right margin. (https://github.com/daveliepmann/tufte-css/blob/master/tufte....)
In Tufte CSSIt's very nice looking.
Everyone criticizing the implementation, here, let me help you:
https://github.com/daveliepmann/tufte-css
In Tufte CSSShowing the 15 most recent of 16 sources. Enable JavaScript to search and browse every indexed mention.