TE Weekly: one argument per issue of The Economist, in two languages
Weekly bilingual reviews of The Economist
At a glance
- What is it?
- The_Economist repository holds a bilingual weekly review of The Economist, built around a fixed template: one central claim, four to seven themes, a reservations section, four things to watch and eight to twelve expressions worth reusing. The interesting part is the editorial method, which treats an issue as an argument rather than a table of contents.
- Who is it for?
- Use this project if you want a repeatable way to read a weekly magazine issue as an argument rather than as a list of articles, since the template forces the reviewer to state the claim, connect the themes and say what the framing leaves out. Do not treat it as a source of summaries to reuse, since the reviews are secondary writing about someone else's copyrighted journalism and the licence is non-commercial.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 3 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 25, 2026, and from our analysis. They are not legal advice.
Editorial analysis
The premise is an argument, not a summary
The project's tagline is read the whole issue, find the argument, and the About section explains the choice. TE Weekly publishes issue-level reviews built around each weekly issue of The Economist, alongside occasional close readings of individual articles and ideas. Rather than summarising articles one by one, every review looks for the argument running through the issue, the shared tension behind stories about politics, business, technology, science and culture. The stated aim is to turn a week of reporting into a clear framework for understanding the world, and to collect the English worth reusing along the way. So the unit of analysis is the issue, and the output is an interpretation, which is a more useful thing to publish than a list of links.
The template is fixed and every section has a job
The README lists what every review contains, and the structure is the method. One central argument connecting the issue as a whole. Four to seven themes that move from events to mechanisms and constraints, so a theme is not a topic but a causal chain. A reservations section asking what the magazine's framing leaves out. Four things to watch that can be tested against future developments, which is a falsifiability commitment rather than a prediction list. Eight to twelve expressions with meaning, tone, original examples and usage notes. And an argument in practice showing how several expressions work together in a paragraph. The voice is specified too: reviews use a neutral editorial voice while close-reading essays leave more room for the author's own perspective.
Three formats with different cadences
What I Publish separates the output into three kinds. The Weekly Review is the main series, and each issue is organised around one central claim supported by several connected themes rather than a tour through the table of contents. Close Reading is occasional author-led essays on a single article or idea, independent of the weekly schedule, and they may return to an older issue whenever a subject deserves more time. The Language Roundup is quarterly, selecting the most reusable expressions from recent issues and organising them by what they do in an argument rather than by their dictionary meanings. That last distinction is the one worth noting, because it means the vocabulary section is organised the way a writer needs it rather than the way a dictionary lists it.
The weekly cadence and the blank rows
The publishing rhythm section explains the schedule. The Economist publishes on Friday, TE Weekly is usually prepared over the weekend and published on Sunday, and the rhythm is intentionally flexible: some weeks may be skipped, while close readings can appear at any time. Reviews are prepared in both English and Chinese and published through Notion on a site called Cell by Cell. The archive table makes the skipping visible, because skipped weeks are left blank rather than filled with placeholders, and the table is numbered sequentially from 01 for July 11, 2026 up to 15 for October 17, 2026. A blank row in that table therefore means the project deliberately did not review that issue, which is different from a missing review.
What the issue titles show about the method
The archive is the clearest evidence of how consistent the argument-first method is, because the titles are arguments rather than topics. The most recent, for October 17, is Progress Needs People Who Can Still Say No. The ones before it are Every Promise Needs Someone to Pay, Greater Capacity Needs Better Rules, Shortcuts Move Costs Rather Than Remove Them, Power Is What Can Be Verified and Delivered, The Difference Between a Claim and a Capacity, The Bottleneck Is Usually Next Door, Power Can Compel Without Controlling, When Signals Become Targets, Systems Lose the Plot, Control Is Not the Same as Capacity, When Action Gets Cheap, Institutions Pay the Bill, The Future Is a Maintenance Problem, The Rule-Makers Are Escaping the Rules, The More You Control, the Less You Can Choose, and Ambition Is Cheap, Capacity Is Scarce. Read across them and you can see the recurring vocabulary of the project itself: control against capacity, claims against capacity, action against cost. The titles are not summaries of the articles, they are the argument the reviewer extracted.
How the repository is put together
The repository itself is small, which fits a project whose output is prose rather than code. There is the README, a Chinese version of it in README_CN.md, a LICENSE file, and a scripts directory that presumably holds the tooling for generating or updating the archive. Everything else lives on the author's own blog, at blog.evanzhou.org, where the TE Weekly series index sits alongside the individual posts in English and Chinese. The archive in the README is marked with HTML comment markers, a BEGIN and an END of te-weekly-archive, which is what lets a script regenerate the table in place. That is the whole engineering surface of the project: a README, a language variant, a licence, and a script that keeps the index in sync with what has been published.
The licence is non-commercial, and the material is someone else's
The README states the licence as CC BY-NC-SA 4.0, share and adapt with attribution, for non-commercial use, under the same licence, and the repository's own licence field carries a custom classification GitHub cannot label. There is a second constraint that the licence does not cover, which is the material itself. The Economist is a copyrighted publication, and what the reviews quote from it is quoted under fair use for the purpose of review and commentary rather than under the reviewer's own licence. So the CC grant applies to the reviewer's writing, the structure of the series and the archive tooling, not to the articles being reviewed. A reader who wants to reuse a review commercially, or to translate it into a paid product, has two separate questions to answer, one about the licence and one about the source.
Editorial conclusion
Use this project if you want a repeatable way to read a weekly magazine issue as an argument rather than as a list of articles, since the template forces the reviewer to state the claim, connect the themes and say what the framing leaves out. Do not treat it as a source of summaries to reuse, since the reviews are secondary writing about someone else's copyrighted journalism and the licence is non-commercial. Verify first which issue a review covers, since the archive numbers issues sequentially and skipped weeks are left blank rather than filled in, and which language version you are reading, since every review is published in both English and Chinese, since the Language Roundup is a teaching aid rather than a licence to reproduce the source material.
Frequently asked questions
What does the The_Economist repository contain?
TE Weekly, a series of weekly bilingual reviews of The Economist built around each issue, alongside occasional close readings of individual articles and ideas. Reviews look for the argument running through an issue rather than summarising articles one by one, and are published in English and Chinese.
What sections does each TE Weekly review contain?
One central argument, four to seven themes moving from events to mechanisms and constraints, a reservations section on what the framing leaves out, four things to watch that can be tested against future developments, eight to twelve expressions with meaning, tone, original examples and usage notes, and an argument in practice showing the expressions working together.
How often are the reviews published?
The Economist publishes on Friday, and TE Weekly is usually prepared over the weekend and published on Sunday. The rhythm is intentionally flexible: some weeks are skipped, and close readings can appear at any time. The archive leaves skipped weeks blank rather than filling them with placeholders.
What is the Language Roundup?
It is the quarterly part of the publication, selecting the most reusable expressions from recent issues and organising them by what they do in an argument rather than by their dictionary meanings.
Under what licence is the The_Economist material published?
The README states CC BY-NC-SA 4.0, share and adapt with attribution for non-commercial use under the same licence, with the licence file at the repository root. The reviews are also secondary commentary on The Economist's own copyrighted journalism.
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/evanbio-the-economist)Was this useful?