DOCSEARCHbyAlgolia
Submit Docs

WordPress.org Meta Repository

repository·trunk·Indexed 41 days ago

https://github.com/wordpress/wordpress.org

Official mirror of the WordPress.org meta SVN repository. Contains source code, themes, and plugins for the WordPress.org ecosystem, including the Plugin and Theme directories, GlotPress translation services, and the Browse Happy site. Includes documentation for local development environments using Docker and wp-env, as well as the 996 Grid responsive design framework.

Tokens
93.2K
Snippets
287
Records
385
Agent score
51%

What's inside WordPress.org

  1. Overview of WordPress.org GP Contributor Moderation

    trunk

    The wporg-gp-contributor-moderation plugin is a moderation tool for the WordPress.org translation system. It identifies users who repeatedly submit incorrect translations and applies one of two moderation states:

    1. Warning: Displays a warning message to the user, but the translation form remains accessible and the submit button remains enabled.
    2. Blocking: Displays a blocking message to the user, disables the submit button, and prevents access to translation file upload URLs (e.g., /import-translations/).

  3. Overview of the 996 Grid Responsive Design Framework

    trunk
    996 Grid is a fixed-width grid framework consisting of 12 even columns. It is designed to adapt content automatically across various screen sizes, from desktop to mobile. At its largest breakpoint, the content area is constrained to a maximum width of 970px, which can be subdivided into columns of two, three, four, or six.

  4. Understand WordPress.org Trac Customizations

    trunk

    The WordPress.org Trac customizations consist of plain static assets served from https://s.w.org/style/trac/. These assets provide client-side enhancements for Trac installs such as core.trac.wordpress.org, meta.trac.wordpress.org, bbpress.trac.wordpress.org, and buddypress.trac.wordpress.org.

    There is no build step for these files. They are automatically included into Trac site templates via Jinja2:

    • site_head.html includes the stylesheets.
    • site_footer.html includes the scripts.

  6. WordPress Meta Git Repository Workspace Map

    trunk

    The repository contains several active services at its root. Key subprojects include:

    • api.wordpress.org: Host for WordPress core API endpoints (updates, version suggestions, community events, translations, Composer v2 package repository).
    • wordpress.org: Primary WordPress.org hubs (Plugin Directory, Theme Directory, Support Forums, Rosetta, HelpHub, Photo Directory, learn.wordpress.org).
    • common: Shared library, modules, and utilities (SSO client, Slack hooks, profiles, testing structure).
    • environments: Local development environment configurations (Docker and wp-env).
    • .github: Custom CI workflows and helper scripts.
    • browsehappy.com: Theme and settings for browser version checking.
    • buddypress.org: Themes and plugins for bbPress.org and BuddyPress.org.
    • jobs.wordpress.net: Official WordPress job board (JobsWP plugin).
    • profiles.wordpress.org: User profile activity and management handlers.
    • svn.wordpress.org: Slack integration hooks for SVN commits or Trac tickets.
    • trac.wordpress.org: Trac environment configurations and migration utilities.
    • wp-themes.com: Live theme preview system handlers.
    • wordpress.tv: Video collection site themes.
    • global.wordpress.org: Subdomain configurations for global networks.

  7. Use WPORG GP Bulk pre-translations for project strings

    trunk

    The wporg-gp-bulk-pretranslations plugin extends the capabilities of https://translate.wordpress.org/ by allowing General Translation Editors (GTEs) to pre-translate project strings using internal or external translation systems.

    Supported Translation Systems

    When performing a bulk selection of strings, you can choose from the following systems to generate pre-translations:

    • Translation memory: Uses existing internal translation data.
    • OpenAI: Uses OpenAI's models for machine translation.
    • DeepL: Uses the DeepL translation service.

    Workflow

    1. Navigate to a project on https://translate.wordpress.org/.
    2. Use the bulk select feature to choose the strings you wish to pre-translate.
    3. Select your preferred translation system (Translation memory, OpenAI, or DeepL) from the new options added to the bulk select interface.
    4. Once the process completes, a status bar will appear indicating the number of pre-translations that were successfully added.

    Note: This functionality is restricted to users with GTE (General Translation Editor) permissions.

  8. Understand the polyfill behavior and auto-disable mechanism

    trunk

    This plugin acts as a polyfill for two pending Gutenberg features (lightbox captions and masonry gallery styles).

    Auto-disabling: The plugin monitors the active Gutenberg version. When the upstream pull requests are merged into WordPress core, the plugin will automatically disable itself to prevent duplicate behavior. When this happens, you will see an admin notice in your dashboard, at which point you can safely deactivate and delete the plugin.

  9. Understand the Browse Happy API

    trunk

    The Browse Happy API is a separate project used to detect browsers via user-agent strings. It returns information regarding browser versions, security status, and whether an update is required.

    This API is utilized by WordPress.org for the admin dashboard widget that alerts users to outdated or insecure browsers.

    Note: This repository contains the theme for the Browse Happy website, not the API logic itself. The API source code is located at: https://meta.svn.wordpress.org/sites/trunk/api.wordpress.org/public_html/core/browse-happy/.

  10. Manage Sass partials in the theme

    trunk

    Styles are organized into Sass partials located under client/styles/{settings,tools,objects,components}/. These partials are aggregated using hand-maintained _*.scss index files.

    Important: When adding a new Sass partial, you must manually @import it into the corresponding index file in the matching directory, otherwise the new styles will not be included in the final bundle.

  11. Manage stable tags and trunk development

    trunk

    The Stable tag value in readme.txt is critical for ensuring users receive the correct version of your code.

    • Defining Version: The readme.txt located in your /tags/[stable-tag]/ directory is what WordPress.org uses to display information about the current stable version.
    • Trunk Development: If you are developing in the trunk directory, you can update the trunk/readme.txt to reflect changes in your in-development version. As long as the trunk's readme.txt points to the correct Stable tag, you won't incorrectly disclose in-development information as being part of the current stable version.

  12. Understand WordPress.org Abilities and MCP integration

    trunk

    WordPress.org Abilities provide the infrastructure for exposing WordPress.org capabilities to the Model Context Protocol (MCP) server. Abilities registered via the WordPress Abilities API using the wporg/ prefix are automatically discovered and exposed as MCP tools, resources, or prompts by the wporg-mcp-server.

    Abilities are organized into domains, which group related tools, resources, and prompts together. This allows for modular extension of the server's capabilities.