Skip to content
Gathering best practices from the community to help developers and site owners find success in scaling WordPress.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
_pages
diagrams
.gitignore
CONTRIBUTING.md
LICENSE
README.md
logo.png

README.md

WordPress at Scale

WordPress at Scale

Gathering best practices from the community to help developers and site owners find success in scaling WordPress. The contents of this repository are synced with scalewp.io via the WordPress Github Sync plugin.

The Problem

WordPress can scale; this is proven. But the expertise on exactly how to do so exists in silos, pockets, as quote-unquote "tribal knowledge". Many people who are new to WordPress (or new to the challenges of scaling) are uncertain, and it isn't easy to find correct answers through searching online.

Mission

This repository exists as a resource for any developer or site owner to learn about the challenges of scalability, and how they can be overcome using bulletproof industry standard approaches. It is meant to provide developers with architectural guidance for infrastructure and services, and to educate site owners so they can better evaluate their options.

Contents

The content is broken up into several pages to make it more easy to consume and share:

  1. Outline
  2. Elastic Architecture
  3. Page Caching
  4. Object Caching
  5. Query Performance
  6. Search
  7. Full Stack Diagram
  8. Development and Workflow

Contributing

Pull requests are welcome! The data collected here is the result of many years of work by many people and there's always more to learn. Make a contribution, and we would be happy to list you on the Contributors page!

To suggest a change or addition to the main content, please fork the repo and make a pull request against the proper file within the _pages directory. If you have a more general question, issue, or suggestion, you may use GitHub's issues functionality.

You can’t perform that action at this time.