tufte-css: Edward Tufte's handout typography as a single stylesheet
Style your webpage like Edward Tufte’s handouts.
At a glance
- What is it?
- tufte-css ports the typography of Edward Tufte's handouts to HTML with one stylesheet and a font directory. It is a CSS-only project, essentially feature-complete, and deliberately excludes JavaScript, print output and static site generator integration.
- Who is it for?
- Adopt tufte-css if you write long-form HTML or Markdown articles that need sidenotes and booktabs tables and you are willing to hand-write the markup, since the project treats static site generator integration as out of scope. Do not adopt it if you need JavaScript behaviour, a print stylesheet or static site generator integration; the README states all three are out of scope.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 144 days ago.
- What is it written in?
- Mainly HTML, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- edwardtufte/tufte-css6,592 ★ · +25
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| edwardtufte/tufte-css | 6.6k | 6.6k |
25 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The problem tufte-css solves, and who it is written for
Edward Tufte's handouts use a distinctive style: simple, with well-set typography, extensive sidenotes, and tight integration of graphics and charts. The README states that tufte-css brings that style to HTML documents. The project is directly inspired by and based on Tufte-LaTeX and the R Markdown Tufte Handout, so the target reader is someone who has seen that layout in print or PDF and wants the same reading rhythm on a web page.
The audience is narrow and specific. This is for people who write long-form prose in HTML and care about margins, sidenote placement and table rules. It is not a general purpose design system, and the README says so: Tufte CSS is specifically a CSS-only solution for styling HTML for the web. If you are building an application interface, a marketing page or anything driven by component state, the stylesheet has nothing to offer you.
The repository is small on purpose. The top-level entries are tufte.css, tufte.min.css, the et-book font directory, index.html, img/, tests/, package.json, playwright.config.js, .gitignore, .nvmrc, LICENSE and README.md. The README tells you to ignore everything except tufte.css and et-book.
How the stylesheet works: one file, one font directory, no JavaScript
The mechanism is a plain CSS file that you link from your document head, plus a font directory that supplies the ET Book typeface. There is no build step required for consumers, no runtime and no script tag. The README describes index.html as a self-describing demonstration document that walks through the features of Tufte CSS, and points to the live version as the best overview.
Sidenotes are the feature that shapes the rest of the layout. The project credits Stephen A Thomas with automagically numbered sidenotes and Ben Newman with the sidenote numbering style. Chris MacKay is credited with sidenote toggling on small screens, so on narrow viewports the margin notes become interactive rather than simply overflowing. That toggle is the one place where behaviour depends on more than static styling, and it is worth checking in a browser before you commit to the layout.
Tables follow the same editorial logic. Kevin Godby is credited with booktabs tables, a rule style borrowed from LaTeX conventions where horizontal rules are used sparingly and vertical rules are avoided. Clay Harmon contributed media queries and rem units, which is why the sizing scales with the root font size rather than being locked to pixels. Linjie Ding contributed the italic typeface, and Claudiu-Vlad Ursache worked on HTML5 conformity.
There is no data flow to describe, because there is no data. The CSS reads your markup structure and positions it. That is the whole architecture, and it is the reason the project can be feature-complete.
Installing tufte-css and writing a first sidenote
The README gives a manual installation path rather than a package manager command: copy tufte.css and the et-book font directory to your project, then link the stylesheet in the head block. The package is also published to npm under the name tufte-css at version 1.9.0, and package.json lists tufte.css, tufte.min.css and et-book/ in its files array, so an npm install will fetch those three things. The README itself does not document the npm route, so treat the copy approach as the supported one.
Start by linking the stylesheet. The README gives this exact line for your document head:
<link rel="stylesheet" href="tufte.css"/>After that link is in place, the demonstration document at index.html is the reference for markup. Open it in a browser and view source to see how each feature is written, since the README describes it as self-describing and says the live version is the best overview.
If you want to work on the stylesheet itself rather than consume it, the repository has a Node toolchain. The engines field requires Node 18 or newer, and .nvmrc is present at the top level. Tests use Playwright to assert computed CSS properties:
npm install
npm testThe README notes that fixtures in tests/ are plain HTML files, so you can open one directly in a browser to inspect a feature in isolation without running the suite. For producing the minified file, package.json defines a build script that runs cleancss:
npm run buildThat writes tufte.min.css from tufte.css. The deploy notes in the README then say to bump the version in package.json and run npm publish, with a prepublish script that runs the build first.
What tufte-css deliberately refuses to do
The scope section is unusually blunt, and it is the most useful part of the README for anyone evaluating the project. JavaScript solutions are out of scope and will not be used, even though the README concedes they are often superior to pure CSS. Handling printed versions of web pages is out of scope. Integration with static site generators or other formats is out of scope.
That last exclusion has practical consequences. If you write in Hugo, Jekyll or Markdown, tufte-css will not meet you halfway. You get a stylesheet and a demonstration document, and you supply the HTML structure yourself. The README's position is that separate work can build on top of Tufte CSS to serve those cases, which is a reasonable division of labour but means the integration cost lands on you.
Print is the second gap that matters. A handout aesthetic invites the question of whether the page prints well, and the README does not claim it does. There is no print stylesheet in the top-level file listing. If print output is a requirement, this project does not address it.
The maintenance statement is also worth reading literally. The README says the project is maintained but not under active development, and that it is considered essentially feature-complete, with refactoring and new functionality at very low priority. The last push to the repository was on 2026-06-24. Contributions to fix bugs or add functionality are still welcome, but you should not expect the design to move.
Tufte-LaTeX and Pico CSS as different answers to the same question
The README names its own ancestor: tufte-css is directly inspired by and based on Tufte-LaTeX. The difference is the output format and the toolchain. Tufte-LaTeX produces a PDF through a LaTeX document class, which means you get the print path that tufte-css excludes, along with LaTeX's build requirements and error messages. Choosing between them is really choosing between a PDF artifact and a web page, not choosing between two stylesheets.
Pico CSS sits at the opposite end of the philosophy. It is a classless CSS framework, meaning it styles semantic HTML elements without requiring you to add layout classes. tufte-css is not classless in the same sense: the demonstration document walks through specific markup for sidenotes, tables and figures, and the README treats that document as the reference. The practical difference is that Pico asks you to write plain HTML and accept its defaults, while tufte-css asks you to write HTML in a particular shape to get a particular editorial layout. If you want a general purpose baseline for an app, tufte-css is the wrong tool and Pico is closer to right. If you want Tufte's margins and sidenote numbering specifically, no general framework gives you that without custom CSS.
Maintenance cost, upgrades and the MIT licence
The upgrade surface is about as small as it gets. Consumers copy two things: tufte.css and the et-book directory. The package version is 1.9.0 and the repository has no published releases, so version bumps are tracked through package.json rather than a release feed. Because the project is described as essentially feature-complete, the main reason to upgrade is a bug fix or a small addition, not a new feature you are waiting on.
If you vendor the file rather than installing it, upgrades are manual: replace tufte.css and re-check your pages. That is a real cost if you have customised the stylesheet, because you will need to reapply your changes. The minified tufte.min.css is generated by the build script, so you should not edit it by hand.
Contributing has its own requirements. The README asks for a clear description of the concern, steps to reproduce, and where possible before and after screenshots plus links to prior discussions or commits. Pull requests should be one change at a time. Fixes and new functionality should be tested against index.html on screens as small as an iPhone 4 and as large as your normal display, with browser developer tools as a substitute for a physical device.
The licence is MIT, stated in the README and in the license field of package.json, with the full text in LICENSE. The et-book font directory ships inside the package, and the README credits Adam Schwartz for the ET Book font without stating separate font licensing terms. If you redistribute the font, check the font files and the LICENSE yourself rather than assuming the MIT grant covers every asset. This is not legal advice.
Editorial conclusion
Adopt tufte-css if you write long-form HTML or Markdown articles that need sidenotes and booktabs tables and you are willing to hand-write the markup, since the project treats static site generator integration as out of scope. Do not adopt it if you need JavaScript behaviour, a print stylesheet or static site generator integration; the README states all three are out of scope. Before committing, verify that the sidenote toggle works at the small screen sizes you care about, because the README asks contributors to test index.html down to an iPhone 4, and confirm your toolchain can link tufte.css and copy the et-book directory.
Frequently asked questions
What is Tufte style in tufte-css?
It refers to the look of Edward Tufte's handouts: simple, with well-set typography, extensive sidenotes, and tight integration of graphics and charts. The README states that tufte-css brings that style to HTML documents, inspired by Tufte-LaTeX and the R Markdown Tufte Handout.
Do I need JavaScript to use tufte-css?
No. The README states that Tufte CSS is specifically a CSS-only solution and that JavaScript solutions are out of scope and will not be used. You link tufte.css and copy the et-book directory, and that is the whole setup.
Can tufte-css be used with Hugo, Jekyll or Markdown?
The README lists integration with static site generators or other formats as out of scope, and says those applications can be served by separate work that builds on top of Tufte CSS. There is no documented integration path in this repository.
How do I run the tufte-css test suite?
Tests use Playwright to assert computed CSS properties. The README says to run npm install to set up and npm test to run, and notes that fixtures in tests/ are plain HTML files you can open directly in a browser to inspect a feature in isolation.
Is tufte-css still being developed?
The README says the project is maintained but not under active development and is considered essentially feature-complete, with refactoring and new functionality at very low priority. The last push to the repository was on 2026-06-24, and contributions to fix bugs or add functionality are still welcome.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/edwardtufte-tufte-css)Star history chart for your README
[](https://hysenlabs.com/projects/edwardtufte-tufte-css)Was this useful?