# These owners will be the default owners for everything in the repo. Unless a later match takes precedence, @pantheon-systems/devrel, as primary maintainers will be requested for review when someone opens a Pull Request.
# Additional code owners can be added for specific paths.
# For more information about CODEOWNERS files, refer to https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
* @pantheon-systems/devrel

# The Platform-Edge-Routing team is responsible for connecting custom domains to Pantheon
src/source/content/guides/domains/ @pantheon-systems/platform-edge-routing @pantheon-systems/devrel
# The Platform-Edge-Routing team is responsible for traffic limits
src/source/content/guides/account-mgmt/traffic/ @pantheon-systems/platform-edge-routing @pantheon-systems/devrel
# The Platform-Edge-Routing team is responsible for bots and indexing
src/source/content/bots-and-indexing @pantheon-systems/platform-edge-routing @pantheon-systems/devrel
# The FileSystem team is responsible for managing static files on Pantheon
src/source/content/guides/filesystem/ @pantheon-systems/filesystem @pantheon-systems/devrel
# The developer-experience team is responsible for Integrated Composer
src/source/content/guides/integrated-composer/ @pantheon-systems/developer-experience @pantheon-systems/devrel
# The developer-experience team is responsible for Terminus
src/source/content/terminus/ @pantheon-systems/developer-experience @pantheon-systems/devrel
# The developer-experience team is responsible for Secrets
src/source/content/guides/secrets/ @pantheon-systems/developer-experience @pantheon-systems/devrel
# The developer-experience team is responsible for the eVCS
src/source/content/guides/external-vcs/ @pantheon-systems/developer-experience @pantheon-systems/devrel
# The developer-experience team is responsible for Next.js
src/source/content/nextjs/ @pantheon-systems/developer-experience @pantheon-systems/devrel
# The developer-experience team is responsible for Next.js
src/source/content/nextjs @pantheon-systems/developer-experience @pantheon-systems/devrel
# The developer-experience team is responsible for GitHub Application
src/source/content/guides/github-application @pantheon-systems/developer-experience @pantheon-systems/devrel
# The cms-platform team is responsible for WordPress Multisite
src/source/content/guides/multisite/ @pantheon-systems/site-experience @pantheon-systems/devrel
# The cms-platform team is responsible for External Libraries on Pantheon
src/source/content/external-libraries @pantheon-systems/site-experience @pantheon-systems/devrel
# The site-experience team is responsible for Elasticsearch docs
src/source/content/guides/elasticsearch/ @pantheon-systems/site-experience @pantheon-systems/devrel
# The site-experience team is responsible for Solr docs
src/source/content/guides/solr-drupal/ @pantheon-systems/site-experience @pantheon-systems/devrel
src/source/content/solr.md @pantheon-systems/site-experience @pantheon-systems/devrel
src/source/content/opensolr.md @pantheon-systems/site-experience @pantheon-systems/devrel
# The site-experience team is responsible for WordPress developer docs
src/source/content/guides/wordpress-developer/ @pantheon-systems/site-experience @pantheon-systems/devrel
# There is a team just for release note permissions
src/source/releasenotes/ @pantheon-systems/release-note-authors @pantheon-systems/devrel
# Edge Routing handles GCDN and AGCDN
src/source/content/guides/global-cdn/ @pantheon-systems/platform-edge-routing @pantheon-systems/devrel
src/source/content/guides/agcdn/ @pantheon-systems/platform-edge-routing @pantheon-systems/devrel
