Gatsby Core Philosophy
Gatsby’s core philosophy can be divided into three parts.
Second, our tooling philosophy. In order to make website building fun, Gatsby’s tooling must embody certain qualities. These include:
Third, our community philosophy. We can’t do this alone, so we’re striving to build the most inclusive community on the web. For that reason, we work in the open. At all times, we believe, and strive to communicate, that you belong here.
We believe that in 5 or 10 years, we’ll look back at many of these blocks like we look back at machine code or assembly language today; low-level languages that are great compile targets for higher-level languages that are easier to write in.
Using abstractions like React components,
gatsby-link, we’ve begun to craft this higher-level language. But we’re just getting started. Gatsby is a playground for discovering new building blocks for the web.
To quote Alan Kay:
“You get simplicity by finding slightly more sophisticated building blocks“.
Over the last few years, teams have begun moving from monolithic, integrated CMS setups to a modular “content mesh” pulling content and functionality from multiple sources and APIs. Their key challenge: pragmatically integrating all these pieces together.
Gatsby’s goal is to build a “content mesh system” that knits modular, best-of-breed tools in content modeling, authentication, search, analytics, payments, UI frameworks, and so on — into a unified, high-quality whole.
Read more on a journey to the content mesh.
Gatsby’s vision is to make website development fun by making it simple.
Fred Brooks wrote in The Mythical Man-Month:
The programmer, like the poet, works only slightly removed from pure thought-stuff. [They] build [their] castles in the air, from air, creating by exertion of the imagination. Few media of creation are so flexible, so easy to polish and rework, so readily capable of realizing grand conceptual structures…
Technology is incredibly fun when we, like the wizard of fantasy, can type an incantation on our computer and a new creation comes to life.
When this incantation is simple and takes seconds, we can easily get lost for hours in the rush of creation trying one thing after another improvising our way to an eventual design.
Developers, designers, demand-gen marketers, copywriters — every stakeholder in a website project can feel this — with proper tooling.
As Bret Victor suggested in Inventing on Principle, each creator needs “an immediate connection to what they’re making.”
These instant feedback loops are often felt near the beginning of projects. But they can quickly be drowned by project complexity.
Developers can spend hours waiting for deploys, tracking down phantom “tooling” bugs, and so on.
We believe that with the right building blocks, and an integrated content mesh system, website projects should continue to feel fun no matter how big they get. We believe that every member of a website team deserves the ability to easily see how their work fits into the whole.
When a copywriter edits a headline in their CMS, a designer draws a button in their illustration app, or a developer adds an if statement in their text editor, they shouldn’t have to imagine what their change looks like in context. They should see it — immediately.
Websites can have, or lack, many qualities. They can be fast, secure, maintainable, beautiful, accessible, and cheap (or not). They can be easy to build and iterate on, have great SEO, and fun to work on (or not).
We believe that these qualities should be baked into frameworks, so they are delivered by default rather than implemented on a per-site basis.
When features and qualities are only available if you implement them, that makes them a luxury — available only to a few websites.
By contrast, by baking in qualities such as performance and security by default, Gatsby makes the right thing the easy thing.
We believe the most high-impact way to make the web better is to make it high-quality by default.
Traditional CMS development presents many challenges such as walled-garden development, difficult-to-maintain local environments, and a challenging target environment.
Modern web development bundles advances in performance (bundle splitting, asset prefetching, offline support, image optimization, or server side rendering), developer experience (componentization via React, transpilation via Babel, webpack, hot reloading), accessibility, and security together.
For more on this, look at the features Gatsby bundles together.
One concept UX designers use to make applications easier to learn and less error-prone is called “progressive disclosure”.
If you were designing a user interface, you might move advanced or rarely-used features to a secondary screen, such as “advanced settings”.
Progressive disclosure simplifies the experience for most people without limiting the abilities of more advanced users.
We progressively disclose complexity by making features such as modifying webpack / Babel config,
gatsby-link opt-in, simple one-off configuration choices. We avoid all-or-nothing “ejection” scenarios where to add further customization you have to leave the tool behind and manage all complexity (eg, dependencies) yourself.
Open source is at the core of Gatsby’s success, and one of the central tenets of open source is that things are done in the open and without smoke and mirrors.
Two of Gatsby’s core strengths are its community and ecosystem.
We’re convinced that the right path forward is to continue working in the open with both trust and support of our community.
Anyone can open an issue and ask a question, and we’ll respond. Anyone can submit a pull request, and we’ll give honest feedback on it. Anyone can submit an RFC to make a major change to Gatsby. And when we want to do this, we’ll submit an RFC as a proposal.
Many of Gatsby’s key features emerged from conversation between contributors. If you plumb through Gatsby’s old issues, you’ll see discussion of many of the core ideas that led to Gatsby — from our plugin system to performance optimizations and so on.
Open source is great for developers. It lets you:
- create a body of work and experience that looks great on a resumé or CV
- build a referral network for paid work
- turn it into a sustainable source of income
However, there are significant barriers to getting started in open source.
First, getting started in open source is daunting. OSS projects can be intimidating. They often have thousands of lines of code and tons of required context and history. Navigating GitHub can be confusing. And there can be awkward social dynamics: imposter syndrome and lack of support.
Second, open source is an expense not everyone can afford. Potential contributors may not have free time to work on open source, and their jobs may not support contributing as part of our workload.
Third, many people don’t see themselves represented in open source.
We believe that that these barriers aren’t simply obstacles to contributing, they’re also obstacles to creating thriving projects. When these barriers persist:
- projects lose so many brilliant people who have so much to contribute
- projects lose an opportunity to add more maintainers
- existing maintainers lose the opportunity to build support networks
Our approach is to be proactive in creating community by:
- actively reaching out and welcoming new contributors
- remembering how steep the learning curve can be
- investing in community as a primary measure of success
For Gatsby, the open source community is everything. We want to be the most welcoming, most inclusive, most fun open source community on the planet.
To accomplish this, we follow a guiding core value: you belong here.
Some things we do in order to create an inclusive, welcoming community include:
- An enforced Code of conduct
- Commitment to accessibility
- Extensive docs
- Friendlier robots
- Implicit trust
- Active gratitude
- Active mentorship
We’ve built an active community with hundreds of contributors, and we want to live the example of what a great open source community can be.
Edit this page on GitHub