HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Automattic
wp-calypso
TypeScript2015–2024
Automattic / wp-calypso

wp-calypso

The JavaScript and API powered WordPress.com

30Distinct people
39Mentions
1Explicit recommenders
12.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The JavaScript and API powered WordPress.com

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I love that you are also working in the open! At Automattic we do a lot of Open Source development. You can even see my PR introducing Sentry to our frontend:…

artpi used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:59:58 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 year39 dated mentions

Observed mentions: 2015-11-23 18:29:06 UTC to 2024-12-11 17:41:17 UTC.

0510152015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 13 mentions; 3 submissions, 10 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 11 mentions; 2 submissions, 9 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC13310
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC1129
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC808
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC110
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Calypso Calypso is the new WordPress.com front-end – a beautiful redesign of the WordPress dashboard using a single-page web application, powered by the WordPress.com REST API. Calypso is built for reading, writing, and managing all of your WordPress sites in one place. It’s built with JavaScript – a very light node plus express server, React.js, Redux, wpcom.js, and many other wonderful libraries on the front-end. Getting Started You can try out the user-side of Calypso on WordPress.com (a lot of the logged-in area is Calypso; if in doubt, view source), you can poke around the code here on GitHub, or you can install it and run it locally. The latter is the most fun. Make sure you have git, node, and yarn installed. Clone this repository locally. Add 127.0.0.1 calypso.localhost to your local hosts file. Execute yarn and then yarn start from the root directory of the repository. Open calypso.localhost:3000 in your browser. Need more detailed installation instructions? We have them. Contributing If Calypso sparks your interest, don’t hesitate to send a pull request, send a suggestion, file a bug, or just ask a question. We promise we’ll be nice. Just don’t forget to check out our CONTRIBUTING doc – it includes a few technical details that will make the process a lot smoother. Calypso welcomes – and indeed has been built by – contributors from all walks of life, with different backgrounds, and with a wide range of experience. We're committed to doing our part to make both Calypso and the wider WordPress community welcoming to everyone. You can contribute in many ways. You can help reporting, testing, and detailing bugs, and also test new features we release in our "beta" program for testing on Horizon. To clarify these expectations, Calypso has adopted the code of conduct defined by the Contributor Covenant. It can be read in full here. Security Need to report a security vulnerability? Go to https://automattic.com/security/ or directly to our security bug bounty site https://hackerone.com/automattic. Our security policy can be read in full here. Browser Support We support the latest two versions of all major browsers. (see Browse Happy for current latest versions). Troubleshooting If you have any problems running Calypso, please see the most common issues. License Calypso is licensed under GNU General Public License v2 (or later).
Read the full README on GitHub

What Hacker News says

11 sources
artpi·Oct 27, 2016Recommendation phrase
I love that you are also working in the open! At Automattic we do a lot of Open Source development. You can even see my PR introducing Sentry to our frontend: https://github.com/Automattic/wp-calypso/pull/2107 (Unfortunately removed, we are running custom solution right now, but thats another story..) How are you dealing with discussions across your team on Github? Sometimes, we have to link to some discussion that is not happening in the open because of this or that business reason and we have to provide a context for colleagues but not everyone else. At other times we want to encourage external contributions but some decisions happen outside of GH and contributors don't feel included. Have you come across similar challenges?
In Building an Open Source Service
If you choose to start a new project with React and Webpack, I recommend to use Facebook's official boilerplate[1] and read their really informative user guide. I also find educational to look at the architecture, libraries and configuration of open source non-trivial web applications (e.g. Wordpress Calypso[2]). [1] https://github.com/facebookincubator/create-react-app [2] https://github.com/Automattic/wp-calypso
In Formidable Playbook: A practical guide to building modern applications
For those who don't have the time to watch all the videos, here's are the github links to the most interesting projects from Day 2: NavigationExperimental: new multi-tab-aware navigation component https://github.com/facebook/react-native/tree/master/Librari... cf. previous work on in-app "paths"by TaskRabbit http://tech.taskrabbit.com/blog/2015/09/21/react-native-exam... Nuclide is an IDE for building react-native apps http://nuclide.io/docs/quick-start/getting-started/ source https://github.com/facebook/nuclide Realm is a mobile database: an alternative to SQLite & key-value stores. Previously iOS and Java, now works with react native too https://github.com/realm/realm-js Exponent lets you write apps in js w/o need for iOS/Android toolchain https://exponentjs.com/ Static site generator using React.js https://github.com/gatsbyjs/gatsby Re
Read the rest
act Native for Web: A framework for building Native Web Apps https://github.com/necolas/react-native-web The source code of wp-calypso, an example of a large React.js project: https://github.com/Automattic/wp-calypso/tree/master/client enzyme's shallow-DOM testing utilities for React https://github.com/airbnb/enzyme#shallow-rendering react-native-mock: a fully mocked and test-friendly version of react native https://github.com/lelandrichardson/react-native-mock graphene: GraphQL framework for Python https://github.com/graphql-python/graphene and their hosted version http://resolver.cloud/
In React.js Conf 2016 [videos]
I wonder how much of that is simply npm duplicating libraries (at slighly different versions) due to its no-shared-dependencies approach? https://github.com/Automattic/wp-calypso/blob/master/package... uses ~130 libs. After npm install (incl. dev deps), node_modules/ weighs 170M file size (and whopping 550M(!) disk size). Let's check duplication. Dirs: (Assuming equal size & name indicate equal content) $ sed 's@\S*node_modules/@@' DU | sort -k2,2 -k1,1 | wc -l 6259 ~/wp-calypso (master) $ sed 's@\S*node_modules/@@' DU | sort -k2,2 -k1,1 | uniq | wc -l 3286 ~/wp-calypso (master) $ sed 's@\S*node_modules/@@' DU | sort -k2,2 -k1,1 | uniq --skip-fields=1 | wc -l 2799 $ sed 's@\S*node_modules/@@' DU | sort -k2,2 -k1,1 | uniq --skip-fields=1 --count | numaverage 2.23615576991783 Bytes: $ sed 's@\S*node_mo
Read the rest
dules/@@' DU | sort -k2,2 -k1,1 | tr -d , | numsum | numfmt --grouping 170,022,500 ~/wp-calypso (master) $ sed 's@\S*node_modules/@@' DU | sort -k2,2 -k1,1 | uniq | tr -d , | numsum 117,107,993 ~/wp-calypso (master) $ sed 's@\S*node_modules/@@' DU | sort -k2,2 -k1,1 | uniq --skip-fields=1 | tr -d , | numsum | numfmt --grouping 91,895,673 => dirs appear in ~2.2 places on average; ~31% of total size is wasted on exact dups, ~14% more spent on different versions on same lib. $ npm dedupe ... $ $ du --summarize --apparent-size node_modules/ 166,097,508 node_modules/ Underwhelming! Only 2%?! dedupe is constrained by npm lookup algorithm (can only lift equal versions to parent dir) but 2% is useless. Should have used sym/hard/reflinks. Anyway, I now know npm's exact-duplication overhead is not huge (though could be linked); inexact-duplication is small enough to be easily worth the ability to mix versions; and that the new control panel is indeed bloated [however I assume it has more functionality than old?].
In The Website Obesity Crisis
Eh, bbPress used to be on BackPress, which was a relatively unmaintained fork of the functional core of WordPress -- rather than having it run on unmaintained software or duplicating effort by pulling code across, it was changed to a plugin -- which is now much easier to set up and share users and content with your main site. It was a good change. Also, while WordPress.com is WordPress some of the way down, some of our other stuff is anything but. We've been migrating to much more API-driven functionality, and the current WordPress.com dashboard (codenamed Calypso) is purely Javascript, based in React, and fully open source. You can download and run it yourself if you like -- https://github.com/Automattic/wp-calypso And yes, as noted, Simperium/Simplenote, Cloudup, PollDaddy, Gravatar, others -- these aren't WordPress.
In Inside Automattic's Remote Hiring Process

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.