Examples for extending WordPress/Gutenberg with blocks.

Overview

Gutenberg Examples

Demo

Examples for extending Gutenberg with plugins which create blocks.

See also: Gutenberg developer documentation

Installation

Gutenberg Examples are distributed as WordPress plugin.

  1. Download a pre-built zip archive of the latest release.

    Do not download from the "Clone or download" GitHub button, as this includes the source material only. Read the Development instructions below if you’re interested in building your own copy of the plugin.

  2. Navigate to the Plugins > Add new screen in your WordPress administrative dashboard.
  3. Click Add New at the top of the page.
  4. Click Upload Plugin at the top of the page.
  5. Click Choose File, then find and Upload the downloaded zip file.
  6. After the plugin finishes installing, click Activate.
  7. You’re done!

Development

First, you need a WordPress Environment to run the plugin on. The quickest way to get up and running is to use the provided docker setup. Install docker-ce and docker-compose by following the most recent instructions on the docker site.

In the folder of your preference, clone this project and enter the working directory:

git clone [email protected]:WordPress/gutenberg-examples.git
cd gutenberg-examples

To bring up this local WordPress instance run:

docker-compose up -d

The WordPress should be available at http://localhost:9999

To stop this local WordPress instance later run:

docker-compose stop

Now go to http://localhost:9999/wp-admin/plugins.php and Activate Gutenberg-examples plugin. The docker script has mapped the gutenberg-examples folder to this now activated plugin. Every time you build an example, it is automaticaly updated in the running docker instance. Old block inserted are not updated, you need to add in your page again.

For each of the examples that include an esnext example the following commands are required to build the plugins:

To install the node packages

npm install

To build the production version of the plugin

npm run build

To build a development version, change to the local directory of the block you are working on, and run npm start to watch for changes and automatically rebuild as you develop.

cd 01-basic-esnext/
npm start



Code is Poetry.

Comments
  • Warning: include(.../format-api/build/index.asset.php): failed to open stream: No such file or directory in ...format-api/index.php on line 20

    Warning: include(.../format-api/build/index.asset.php): failed to open stream: No such file or directory in ...format-api/index.php on line 20

    The current trunk branch produces the following warning.

    Warning: include(wp-content/plugins/gutenberg-examples/format-api/build/index.asset.php): failed to open stream: No such file or directory in .../wp-content/plugins/gutenberg-examples/format-api/index.php on line 20
    

    It appears the build files are missing.

    bug [Status] Needs More Info 
    opened by mipon 12
  • Major structural overhaul to the repo

    Major structural overhaul to the repo

    This PR is an attempt to simplify the structure of the repo by using a single build process for all of the examples.

    Benefits:

    • Allows the repo to show off the power and flexibility of the @wordpress/scripts package by leveraging both the built-in handling of multiple blocks while also adding our own functionality via an extended webpack.config.js file.
    • Simplifies the repo by no longer needing to leverage Lerna to build out the various examples.
    • Allows all files to be stored in a single build directory. This will make using an Action to generate a new .zip archive much easier and potentially allow us to not have to version the build directory - which is not a common practice in the wild.

    Changes:

    • New blocks must be added to the src directory as would be done normally when using the scripts package.
    • Any non-block examples such as data API examples or slot fill examples must be added to the non-block-examples directory for the build process to find them
    opened by ryanwelcher 11
  • Include examples of tests

    Include examples of tests

    I've found it time consuming to get Jest properly configured with Babel and JSX and all the things. I think it'd be useful to include working testings and all the required build tool configs, in order to make this easier and more convenient for people.

    enhancement 
    opened by iandunn 10
  • Add Site Title to Dynamic Block

    Add Site Title to Dynamic Block

    I appreciate @ryanwelcher's suggestion on simplifying PR #205

    This PR adds the Site Title option value (found at Settings > General)

    image

    and adds it to the "10-dynamic-block" example.

    Front End

    image

    In the Editor

    image

    Note: In the editor the Site Title (in this case "gutenberg-examples") can not be modified.

    Resolves #203

    opened by salcode 6
  • Chore: Upgrade @wordpress/scripts to the latest version

    Chore: Upgrade @wordpress/scripts to the latest version

    npm run lint-js still doesn't work.

    I'm seeing:

    /Users/gziolo/PhpstormProjects/gutenberg-examples/test/examples.js
      12:1  error  'test' is not defined    no-undef
      17:2  error  'expect' is not defined  no-undef
      21:1  error  'test' is not defined    no-undef
      26:2  error  'expect' is not defined  no-undef
    
    ✖ 4 problems (4 errors, 0 warnings)
    
    enhancement 
    opened by gziolo 6
  • Easier up-and-running workflow

    Easier up-and-running workflow

    It's not very easy to clone and install this repository as a plugin. We might consider either pre-built distributables, and/or improving the install/build workflow.

    Currently, the developer must cd into each -esnext folder, npm install && npm run build.

    Via Slack Overflow sleuthing, I found some nice conveniences to this:

    find ./* -maxdepth 1 -name package.json -execdir sh -c "npm install; npm run build" \;
    

    But this will not support WIndows. We could either find dependencies with CLIs which perform similar, or create our own script.

    enhancement 
    opened by aduth 6
  • Issues with settings spread and translations

    Issues with settings spread and translations

    All of the examples of registering blocks use the following approach to registering blocks.

    import json from '../block.json';
    import edit from './edit';
    import save from './save';
    
    const { name, ...settings } = json;
    
    registerBlockType( name, {
    	...settings,
    	edit,
    	save,
    } );
    
    

    It was pointed out in this comment that spreading the settings object is not technically required as this is done on the server-side for blocks registered. It should be used to override those server-side values or in the case of registering a JavaScript-only block.

    Based on a conversationwith @gziolo it also seems that if the settings are passed as they are defined in block.json ( as in the approach above ) any translations will not be processed and would need to be provided in that object.

    bug 
    opened by ryanwelcher 5
  • Convert build procedure to use wp-scripts

    Convert build procedure to use wp-scripts

    • Simplifies the build procedure to use wp-scripts setup
    • Removes .babelrc and webpack.config.js to use standard configs from wp-scripts
    • Adjusts code to live where wp-scripts expects it to be
    enhancement 
    opened by mkaz 5
  • 2 Editable examples not working (step 3 and 4)

    2 Editable examples not working (step 3 and 4)

    Examples 3 and 4 are broken on my naked / Gutenberg only latest wordpress environment.

    Wordpress Version: 4.9.6 Gutenberg Version: 2.9.2 Gutenberg Examples Version: 0.1.0

    image

    bug 
    opened by katerlouis 5
  •  Error establishing a database connection after first install

    Error establishing a database connection after first install

    After doing the following as instructed in the readme,

    git clone https://github.com/WordPress/gutenberg-examples.git
    cd gutenberg-examples
    docker-compose up -d
    

    I opened http://localhost:9999 on my browser. However, the page says "establishing a database connection".

    OS: Xubuntu 20.04

    opened by martian17 4
  • block.json must be inside

    block.json must be inside "src" folder when using custom or multiple entry points

    I've just submitted an issue to the Gutenberg repo regarding the placement of block.json because it's not very clear that when you use a custom entry-point or multiple entry points such as "editorScript" or "viewScript" webpack expects block.json to live inside the src folder. In all your examples where there is a src folder, block.json is not inside that folder which is confusing unless you realize that works because in all the examples you are using the default entry point of src/index.js.

    Additionally, if you did move block.json into the src folder per the webpack config, it would look for src/build/index.js instead of src/index.js, because the file:... path is relative to the src directory, not the package directory.

    I'm raising this issue here as well as Gutenberg because I believe block.json shouldn't live inside src but also because:

    1. You should document that "gotcha"
    2. The file:... values are technically incorrect but it's not being caught because wepack uses the default entry point of src/index.js
    opened by alexdelgado 3
  • Multiple blocks examples

    Multiple blocks examples

    It would be great if multiple blocks examples were added:

    • blocks-jsx/07-multiple-blocks
    • blocks-non-jsx/07-multiple-blocks

    Some (untested) references:

    • https://www.youtube.com/watch?v=O_4loYiEcbg
    • https://wordpress.stackexchange.com/questions/407748/how-to-register-two-blocks-in-the-same-plugin
    • https://github.com/ryanwelcher/twitch/tree/trunk/plugins/native-multiple-blocks
    • https://luigicavalieri.com/blog/registering-multiple-gutenberg-blocks-using-block_json-files/

    regards

    opened by thomas-price 0
  • Bump simple-git from 3.7.1 to 3.15.1

    Bump simple-git from 3.7.1 to 3.15.1

    Bumps simple-git from 3.7.1 to 3.15.1.

    Release notes

    Sourced from simple-git's releases.

    [email protected]

    Patch Changes

    • de570ac: Resolves an issue whereby non-strings can be passed into the config switch detector.

    [email protected]

    Minor Changes

    • 7746480: Disables the use of inline configuration arguments to prevent unitentionally allowing non-standard remote protocols without explicitly opting in to this practice with the new allowUnsafeProtocolOverride property having been enabled.

    Patch Changes

    • 7746480: - Upgrade repo dependencies - lerna and jest
      • Include node@19 in the test matrix

    [email protected]

    Patch Changes

    • 5a2e7e4: Add version parsing support for non-numeric patches (including "built from source" style 1.11.GIT)

    [email protected]

    Minor Changes

    • 19029fc: Create the abort plugin to allow cancelling all pending and future tasks.
    • 4259b26: Add .version to return git version information, including whether the git binary is installed.

    [email protected]

    Minor Changes

    • 87b0d75: Increase the level of deprecation notices for use of simple-git/promise, which will be fully removed in the next major
    • d0dceda: Allow supplying just one of to/from in the options supplied to git.log

    Patch Changes

    • 6b3e05c: Use shared test utilities bundle in simple-git tests, to enable consistent testing across packages in the future

    [email protected]

    Minor Changes

    • bfd652b: Add a new configuration option to enable trimming white-space from the response to git.raw

    [email protected]

    Minor Changes

    • 80d54bd: Added fields updated + deleted branch info to fetch response, closes #823

    Patch Changes

    • 75dfcb4: Add prettier configuration and apply formatting throughout.

    ... (truncated)

    Changelog

    Sourced from simple-git's changelog.

    3.15.1

    Patch Changes

    • de570ac: Resolves an issue whereby non-strings can be passed into the config switch detector.

    3.15.0

    Minor Changes

    • 7746480: Disables the use of inline configuration arguments to prevent unitentionally allowing non-standard remote protocols without explicitly opting in to this practice with the new allowUnsafeProtocolOverride property having been enabled.

    Patch Changes

    • 7746480: - Upgrade repo dependencies - lerna and jest
      • Include node@19 in the test matrix

    3.14.1

    Patch Changes

    • 5a2e7e4: Add version parsing support for non-numeric patches (including "built from source" style 1.11.GIT)

    3.14.0

    Minor Changes

    • 19029fc: Create the abort plugin to allow cancelling all pending and future tasks.
    • 4259b26: Add .version to return git version information, including whether the git binary is installed.

    3.13.0

    Minor Changes

    • 87b0d75: Increase the level of deprecation notices for use of simple-git/promise, which will be fully removed in the next major
    • d0dceda: Allow supplying just one of to/from in the options supplied to git.log

    Patch Changes

    • 6b3e05c: Use shared test utilities bundle in simple-git tests, to enable consistent testing across packages in the future

    3.12.0

    Minor Changes

    • bfd652b: Add a new configuration option to enable trimming white-space from the response to git.raw

    3.11.0

    Minor Changes

    ... (truncated)

    Commits
    • c9fc61f Version Packages
    • de570ac Fix/non strings (#867)
    • d4764bf Version Packages
    • 7746480 Chore: bump lerna, jest and create prettier workflow (#862)
    • 6b3c631 Create the unsafe plugin to configure how simple-git treats known potenti...
    • e459622 Version Packages
    • 5a2e7e4 Add version parsing support for non-numeric patches (to include built… (#853)
    • 6460a1f Version Packages
    • 4259b26 Create interface for retrieving git version information (#850)
    • 19029fc Abort plugin (#848)
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Bump loader-utils from 2.0.2 to 2.0.4

    Bump loader-utils from 2.0.2 to 2.0.4

    Bumps loader-utils from 2.0.2 to 2.0.4.

    Release notes

    Sourced from loader-utils's releases.

    v2.0.4

    2.0.4 (2022-11-11)

    Bug Fixes

    v2.0.3

    2.0.3 (2022-10-20)

    Bug Fixes

    • security: prototype pollution exploit (#217) (a93cf6f)
    Changelog

    Sourced from loader-utils's changelog.

    2.0.4 (2022-11-11)

    Bug Fixes

    2.0.3 (2022-10-20)

    Bug Fixes

    • security: prototype pollution exploit (#217) (a93cf6f)
    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Content attribute type array instead of string in blocks-non-jsx/03-editable block example

    Content attribute type array instead of string in blocks-non-jsx/03-editable block example

    I removed all the attributes in the PHP's block registration, since we have all of them in blocks.json already and they seem to be more correct (blocks.json is using a string instead of an array for content attribute type)

    Related bug: https://github.com/WordPress/gutenberg-examples/issues/220

    opened by tloureiro 0
  • Updated the incomplete data basics repo to reflect the GB handbook how-to guide

    Updated the incomplete data basics repo to reflect the GB handbook how-to guide

    The data basics app on this repo was incomplete so I went through the handbook guide from start to finish and created the app from scratch.

    I've also updated the how to guide via a separate PR: https://github.com/WordPress/gutenberg/pull/43633

    opened by dgwyer 1
Releases(v1.1.0)
  • v1.1.0(Mar 30, 2022)

    This release marks a major update to this plugin that includes completely updated block examples as well as new non-block examples.

    See the changelog below for details:

    What's Changed

    • Convert build procedure to use wp-scripts by @mkaz in https://github.com/WordPress/gutenberg-examples/pull/65
    • Upgrade @wordpress/scripts and add ESLint support for ESNext code by @gziolo in https://github.com/WordPress/gutenberg-examples/pull/83
    • Try: Add very basic unit tests to validate it works with the repository at the global level by @gziolo in https://github.com/WordPress/gutenberg-examples/pull/84
    • Update examples to use wp-scripts 5.0.0 by @mkaz in https://github.com/WordPress/gutenberg-examples/pull/89
    • Clarify start instructions for development builds by @mkaz in https://github.com/WordPress/gutenberg-examples/pull/91
    • Update variable to asset_file, matches elsewhere by @mkaz in https://github.com/WordPress/gutenberg-examples/pull/92
    • Add example block setting to show block preview by @mkaz in https://github.com/WordPress/gutenberg-examples/pull/93
    • Build: Asset files were not updated properly by @gziolo in https://github.com/WordPress/gutenberg-examples/pull/94
    • Fix 05-recipe-card-esnext by @megane9988 in https://github.com/WordPress/gutenberg-examples/pull/100
    • More help in the Development process by @laurentdebricon in https://github.com/WordPress/gutenberg-examples/pull/99
    • unifying position of add_action before function declaration by @fabiankaegy in https://github.com/WordPress/gutenberg-examples/pull/95
    • Add inner blocks example by @oandregal in https://github.com/WordPress/gutenberg-examples/pull/102
    • Chore: Update @wordpress/scripts dependency by @gziolo in https://github.com/WordPress/gutenberg-examples/pull/103
    • Add Node.js GitHub Action Workflow by @ntwb in https://github.com/WordPress/gutenberg-examples/pull/104
    • chore: Fix GitHub actions workflow file path by @ntwb in https://github.com/WordPress/gutenberg-examples/pull/105
    • chore: Add lint-pkg-json script for root package.json by @ntwb in https://github.com/WordPress/gutenberg-examples/pull/106
    • Project: Add Lerna support to make maintenance simpler by @gziolo in https://github.com/WordPress/gutenberg-examples/pull/108
    • Code style: Use wp-scripts format-js to change file formatting by @gziolo in https://github.com/WordPress/gutenberg-examples/pull/107
    • Chore: Update @wordpress/scripts dependency by @gziolo in https://github.com/WordPress/gutenberg-examples/pull/112
    • Chore: Update npm dependencies by @gziolo in https://github.com/WordPress/gutenberg-examples/pull/113
    • Chore: Update @wordpress/scripts to 9.0.0 by @gziolo in https://github.com/WordPress/gutenberg-examples/pull/114
    • Update Basic block. by @ryanwelcher in https://github.com/WordPress/gutenberg-examples/pull/148
    • Update the 01-basic-esnext block to use block.json by @ryanwelcher in https://github.com/WordPress/gutenberg-examples/pull/149
    • Update the Example: Editable block. by @ryanwelcher in https://github.com/WordPress/gutenberg-examples/pull/151
    • Update Example: Stylesheets block to use block.json by @ryanwelcher in https://github.com/WordPress/gutenberg-examples/pull/150
    • Add PHPCS and use the WordPress ruleset by @ryanwelcher in https://github.com/WordPress/gutenberg-examples/pull/154
    • Remove polyfill dependencies by @mkaz in https://github.com/WordPress/gutenberg-examples/pull/155
    • Update Example: Editable (ESNext) block. by @ryanwelcher in https://github.com/WordPress/gutenberg-examples/pull/156
    • Update Example: Controls block to use latest API. by @ryanwelcher in https://github.com/WordPress/gutenberg-examples/pull/157
    • Update the Controls (ESNext) block to use the latest API by @ryanwelcher in https://github.com/WordPress/gutenberg-examples/pull/158
    • Update Example: Recipe Card to use the latest API by @ryanwelcher in https://github.com/WordPress/gutenberg-examples/pull/159
    • Update Recipe Card (ESNext) to use the latest API by @ryanwelcher in https://github.com/WordPress/gutenberg-examples/pull/160
    • Add Prettier to the project. by @ryanwelcher in https://github.com/WordPress/gutenberg-examples/pull/161
    • Update Inner Blocks example to use the latest API by @ryanwelcher in https://github.com/WordPress/gutenberg-examples/pull/162
    • Update Inner Blocks (ESNext) to use the latest API by @ryanwelcher in https://github.com/WordPress/gutenberg-examples/pull/163
    • Block.json formatting now that prettier is integrated. by @ryanwelcher in https://github.com/WordPress/gutenberg-examples/pull/164

    New Contributors

    • @gziolo made their first contribution in https://github.com/WordPress/gutenberg-examples/pull/73
    • @megane9988 made their first contribution in https://github.com/WordPress/gutenberg-examples/pull/100
    • @laurentdebricon made their first contribution in https://github.com/WordPress/gutenberg-examples/pull/99
    • @fabiankaegy made their first contribution in https://github.com/WordPress/gutenberg-examples/pull/95
    • @oandregal made their first contribution in https://github.com/WordPress/gutenberg-examples/pull/102

    Full Changelog: https://github.com/WordPress/gutenberg-examples/compare/v1.0.2...v1.1.0

    Source code(tar.gz)
    Source code(zip)
    gutenberg-examples.zip(64.56 KB)
  • v1.0.2(Dec 19, 2018)

  • v1.0.1(Oct 29, 2018)

Owner
null
Scaffold plugin for creating and managing Blocks, Block Patterns, Block Styles and Block Editor Sidebars in the WordPress Block Editor (aka Gutenberg).

WordPress Block Editor Scaffold This project is a template repo for developing WordPress Blocks, Block Patterns, Block Styles and Block Editor Sidebar

Rareview 6 Aug 2, 2022
Query gutenberg blocks with wp-graphql

WPGraphQL Gutenberg Query gutenberg blocks through wp-graphql Usage Docs Join our community through WpGraphQL Slack Install Requires PHP 7.0+ Requires

null 270 Jan 3, 2023
📦 A zero-configuration #0CJS developer toolkit for building WordPress Gutenberg block plugins.

create-guten-block is zero configuration dev-toolkit (#0CJS) to develop WordPress Gutenberg blocks in a matter of minutes without configuring React, w

Ahmad Awais ⚡️ 3.1k Dec 23, 2022
Documents WordPress Classic Editor integration points and their Gutenberg equivalents

Gutenberg Migration Guide This repository documents WordPress Classic Editor customization points and their Gutenberg equivalents (if such exist). Its

Daniel Bachhuber 185 Nov 16, 2022
Gutenberg Custom Fields... wait what?

Gutenberg Custom Fields Gutenberg Custom Fields allows you to control the content of the Gutenberg edit screen by creating pre-filled templates. Navig

Riad Benguella 192 Dec 24, 2022
A plugin to disable the drop cap option in Gutenberg editor paragraph block. This is version 2.

Disable Drop Cap (v2) A plugin to disable drop cap option in the Gutenberg editor block editor paragraph block. Note for WordPress 5.8 With WordPress

Johannes Siipola 4 Jan 4, 2022
Curated list that contain code, snippets or examples without libraries or external packages for developers.

Awesome WordPress Developer Tips Curated list that contain very awesome and ready code, snippets or examples without libraries or external packages ma

Daniele Scasciafratte 110 Nov 13, 2022
Structured content blocks for WPGraphQL

WPGraphQL Content Blocks (Structured Content) This WPGraphQL plugin returns a WordPress post’s content as a shallow tree of blocks and allows for some

Quartz 72 Oct 3, 2022
A custom WordPress nav walker class to fully implement the Twitter Bootstrap 4.0+ navigation style (v3-branch available for Bootstrap 3) in a custom theme using the WordPress built in menu manager.

WP Bootstrap Navwalker This code in the main repo branch is undergoing a big shakeup to bring it in line with recent standards and to merge and test t

WP Bootstrap 3.3k Jan 5, 2023
A curated list of Awesome WordPress Theme, Plugins and Framework development Resources and WordPress Communities.

Awesome WordPress A curated list of Awesome WordPress Theme, Plugins and Framework development Resources and WordPress Communities. Inspired by bayand

Dropndot Limited 91 Dec 26, 2022
The Pronamic WordPress Basecone plugin allows you to connect your WordPress installation to Basecone.

Pronamic WordPress Basecone The Pronamic WordPress Basecone plugin allows you to connect your WordPress installation to Basecone. Table of contents Au

Pronamic 1 Oct 19, 2021
A WordPress plugin to suspend WordPress sites automagically. Simple and lightweight, no annoying ads and fancy settings.

Suspend WP A WordPress plugin to suspend WordPress sites automagically. Simple and lightweight, no annoying ads and fancy settings. ?? Demo (coming so

Waren Gonzaga 3 Nov 15, 2021
Twenty Twenty-Two, the default WordPress theme that will launch with WordPress 5.9.

Twenty Twenty-Two Welcome to the development repository for the default theme that will launch with WordPress 5.9. About Twenty Twenty-Two is designed

null 414 Nov 28, 2022
Easy handle APlayer on WordPress. A shortcode for WordPress to using APlayer.

Description Easy handle APlayer on WordPress. A shortcode for WordPress to using APlayer. Support [audio] tag, compatible with AMP. Requirement WordPr

Karl Chen 24 Nov 3, 2022
WordPress plugin that lets you use Discourse as the community engine for a WordPress blog

WP Discourse Note: the wp-discourse plugin requires >= PHP-5.4.0. The WP Discourse plugin acts as an interface between your WordPress site and your Di

Discourse 497 Dec 10, 2022
WordPress & TypeScript. Simple starter template for WordPress projects

WordPress & TypeScript. Simple starter template for WordPress projects that want to use TypeScript in combination with @wordpress/scripts

Make it WorkPress 11 Sep 27, 2022
Simple WordPress plugin to learn how to understand WordPress Crons and the Action Scheduler library.

Simple WordPress plugin to learn how to understand WordPress Crons and the Action Scheduler library. Import Jamendo playlists with tracks in WordPress posts.

Pierre Saikali 3 Dec 7, 2022
A PHP client for Wordpress websites that closely implement the XML-RPC WordPress API

Wordpress XML-RPC PHP Client A PHP client for Wordpress websites that closely implement the XML-RPC WordPress API Created by Hieu Le MIT licensed. Cur

Hieu Le 112 Nov 10, 2022
Automattic 10.7k Jan 2, 2023