Wordless is a junction between a WordPress plugin and a theme boilerplate that dramatically speeds up and enhances your custom theme creation


Wordless logo

Wordless is a junction between a WordPress plugin and a theme boilerplate that dramatically speeds up and enhances your custom theme creation. Some of its features are:

  • A structured, organized and clean theme organization
  • Bootstrap a new theme directly within wp-cli
  • Write PHP templates with Pug templating system
  • Write CSS stylesheets using the awesome SCSS syntax
  • Out-of-the-box support to Stylelint configured for SCSS syntax.
  • Write Javascript logic using modern syntax thanks to Babel
  • Automatically polyfill (with core-js) and transpile Javascript based on your support inside .browserslistrc
  • A growing set of handy and documented PHP helper functions ready to be used within your views
  • Preconfigured support to MailHog mail-catcher in development.
  • Development workflow backed by WebPack, BrowserSync (with live reload), WP-CLI, Yarn. All the standards you already know, all the customizations you may need.

Helpers tests Documentation Status


Complete documentation

Read the complete Wordless documentation at wordless.readthedocs.io where you'll find - hopefully - all the informations about installation, usage guide, in depth explanation about the stack.

If you want to contribute to the documentation.

Every subsequent make documentation will refresh your HTML.

Built-in helpers documentation

You can find it at http://welaika.github.io/wordless/docs/latest/html/index.html.

If you are interested in contributing to the documentation:

  • we are documenting php files in
  • here is a list of documentation gaps :9
  • brew install doxygen
  • go and add doc following the doxygen conventions
  • compile the new doc with doxygen docs/Doxyfile (from project's root)
  • you'll have an untracked folder docs/build in GiT. Leave it alone and git checkout gh-pages instead.
  • mv docs/build docs/latest overwriting the old one
  • commit and push the branch



  • Merge your feature branch - with passing tests - in master with git checkout master && git merge --no-ff feature or by pull request
  • On master update the plugin version (SEMVER) in ./wordless.php ("Version") and readme.txt ("Stable tag") files and commit the updated files.
  • do git tag x.y.x where x.y.z equals to the previously written version.
  • git push origin master --tags to push both commits and tags
  • update the changelog for the new release at https://github.com/welaika/wordless/releases

Automations will do the leftovers, including to publish updated documentation on ReadTheDocs and the plugin on https://wordpress.org/plugins/wordless/


A changelog for each tag/relase is mandatory to be compiled at https://github.com/welaika/wordless/releases.

Additional recommended plugins and tools

Wordmove: a great gem (from yours truly) to automatically mirror local WordPress installations and DB data back and forth from your local development machine to the remote staging server;

Known limitations

  • Wordless has not been tested on Windows



Default configuration has dropped support for CoffeeScritp and for SASS indented syntax. Obviously you are free to change Webpack's config once you've created the theme, but now we officially support ES2015 and SCSS instead.


Ruby-based preprocessors and the WORDLESS_LEGACY configuration are definitely dropped. Theme's folder structure changed.


Wordless 2.5 deprecates the old ruby preprocessor support. It is disabled by default. If you need to develop an old theme you need to explicitely activate them by setting the following in your wp-config.php:

define('WORDLESS_LEGACY', true);

We plan to completely remove this support in Wordless 3.


Wordless is available in English, German, Greek, Italian and Spanish, at the moment.

The user interface was translated by Wasilis Mandratzis-Walz (German and Greek), David Mejorado (Spanish).

Your help is welcome! Add your own language using Transifex.

Need more tools?

Visit WordPress Tools.

Third Part Libraries


made with ❤️ and ☕️ by weLaika


(The MIT License)

Copyright © 2011-2019 weLaika

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ‘Software’), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.


  • can't get it working on MAMP

    can't get it working on MAMP

    Hello So i setup all like in the readme description. MAMP is also running for Apache and the Mysql, but it doesn't work, the Sass- or Haml-files are'nt compiled, it even didn't builds any of the preset CSS.

    Any Idea where's my mistake?


    opened by dirkschmid 39
  • css doesn't compile

    css doesn't compile

    everything is working fine, except that i'm not getting any css output. i'm currently running codekit to output css. please let me know what further info you need.

    opened by rvr 28
  • Wordless gem

    Wordless gem

    I think a Wordless gem would simplify many operations and bring a healthy dose of Rails culture to WordPress development.

    Some example tasks I would propose:

    wordless new mysite

    • Download the latest stable version of WordPress
    • Install the latest stable version of Wordless and create a Wordless theme
    • Automatically configure executable paths in config/initializers/wordless_preferences.php
    • Add a properly configured .gitignore (i.e. ignore wp-content/themes/mysite/theme/tmp/*)

    Some other possible stuff:

    wordless new mysite -c less: Preconfigure the theme with the LESS preprocessor, see #58 wordless new mysite -v php: Use PHP views instead of Haml views in the generated theme wordless new mysite --edge: Use master branch of Wordless instead of latest stable wordless compile: Compile static assets (see #59) wordless deploy production: Compile assets and deploy using Wordmove (or some other mechanism)

    Any thoughts?

    opened by etienne 17
  • Unable to compile Sass

    Unable to compile Sass

    OS: Ubuntu 16.04


    1. Followed the Getting started and created a new theme.
    2. wordless compile returns,
    Problems compiling /var/www/html/wordpress_wordless/wp-content/themes/wordless/theme/assets/main.js to /var/www/html/wordpress_wordless/wp-content/themes/wordless/assets/main.js
    WordlessCompileException: [0]: The path /opt/wordless/ruby doesn't seem to be an executable!
    Output error:
    PHP Notice:  Undefined variable: compiled_content in /var/www/html/wordpress_wordless/wp-content/plugins/wordless/wordless/wordless.php on line 146
    Problems compiling /var/www/html/wordpress_wordless/wp-content/themes/wordless/theme/assets/javascripts/application.js.coffee to /var/www/html/wordpress_wordless/wp-content/themes/wordless/assets/javascripts/application.js
    WordlessCompileException: [0]: The path /opt/wordless/ruby doesn't seem to be an executable!
    Output error:
    PHP Notice:  Undefined variable: compiled_content in /var/www/html/wordpress_wordless/wp-content/plugins/wordless/wordless/wordless.php on line 146
    Problems compiling /var/www/html/wordpress_wordless/wp-content/themes/wordless/theme/assets/stylesheets/screen.sass to /var/www/html/wordpress_wordless/wp-content/themes/wordless/assets/stylesheets/screen.css
    WordlessCompileException: [0]: The path /opt/wordless/compass doesn't seem to be an executable!
    Output error:
    PHP Notice:  Undefined variable: compiled_content in /var/www/html/wordpress_wordless/wp-content/plugins/wordless/wordless/wordless.php on line 146

    yarn run server generates screen.css. I tried deleting screen.css, editing a Sass file and running yarn run server again. screen.css does not reflect the change made in the Sass file.

    opened by dnguneratne 14
  • Considering replacing PHAMLP with jade.php

    Considering replacing PHAMLP with jade.php

    I've just stumbled upon https://github.com/everzet/jade.php, which is a nice Slim/Jade PHP ripoff. Seems quite nice and even DRYer. I was considering to add it as an alternative Wordless templating solution (maybe make it the default one).

    One gotcha: it's compatible with PHP 5.3+.

    Any other HAML/Slim/Jade PHP ripoffs around there?

    features idea 
    opened by stefanoverna 12
  • "environments" variable

    Add a folder inside config/ called environment in which specify configuration for different state of the theme ( development, staging, production ).

    A doubt: what is the best way to load the proper environment file?

    opened by endorama 11
  • WordLess Plugin

    WordLess Plugin

    Hello everyone! As already reported to a member of Welaika, who then rightly asked me to report a problem on the problem found here on GitHub, I encountered the problem with an error after its first installation and then after creating a starter theme with the command I went to the folder of the theme and I gave the command wp server to start the local development server, I also tried with yarn (same thing) and also with the classic MAMP for MacOS but nothing ... So I was wondering if there someone would be able to deal with the problem and then help me solve it. Thanks in advance to everyone! (place the screenshots of the error below in the issue)

    schermata 2018-06-07 alle 16 33 48 schermata 2018-06-07 alle 16 33 51
    opened by raffa96 10
  • Using page templates in views folder and resolving conflict with index.php bypass.

    Using page templates in views folder and resolving conflict with index.php bypass.

    I would like to use page templates placed in the views folder. It seems like WordPress bypasses index.php when using page templates so we need to have a workaround.

    support idea 
    opened by svenhanssen 10
  • Help with Less setup for Wordless.

    Help with Less setup for Wordless.

    Hey man. Hopefully it's alright for me to ask here.

    Can we get a little bit of guidance on how to set Wordless up to use Less?

    I feel like I did it correctly but it's not working.

    Do we set the 'assets.preprocessor' to:

    "Wordless::set_preference("assets.preprocessors", array("SprocketsPreprocessor", "LessPreprocessor"));

    Should the compass lines be commented out?

    Do we have to edit less_preprocessor.php at all? Or we can just set the path in the wordless_preferences.php file?

    Sorry for the newb q's. I'm not the strongest ruby dev ever so I may be overlooking some glaring issue.

    But this is an amazing piece of software, and I'm on a mission to make it work. Would appreciate any bit of guidance you can offer. I searched everywhere but wasn't finding anything except the pull request pages etc.

    Thanks so much!

    opened by ryanorrico 10
  • Issues with rbenv

    Issues with rbenv

    This is a followup to my previous post. I cannot get wordless working with rbenv. I followed the instructions but when wordless trying to process the assets is cannot run the executables. Any advise on this would be great as I have had my site built for a month and get get it working with wordless!

    opened by jwaldrip 10
  • No Instruction for Windows user

    No Instruction for Windows user

    I knew you already wrote that wordless has not been tested on Windows, i just have no idea with the compass and ruby path since I couldnt install RVM. Any hint?

    opened by gasatrya 9
  • WP 5.5 updated the vendored PHPMailer and our smtp config is now bugged

    WP 5.5 updated the vendored PHPMailer and our smtp config is now bugged


    Since WP 5.5 PHPMailer is no longer globally available but is namespaced as PHPMailer\PHPMailer\PHPMailer.

    We have to update the type check in the linked part of code.

    opened by pioneerskies 0
  • Error in render_helper.php file occurring in render_template func via ensure_dir func

    Error in render_helper.php file occurring in render_template func via ensure_dir func

    In render_helper.php file in function error was identified: Ouch!! It seems that the /var/www/wp-content/themes/<>/tmp

    ensure_dir function sometimes cannot override the tmp folder permission to writeable, some server forbid the chmod action. Hence we compile our files via CLI during CI build process, this generates files in tmp DIR. Now I have corrected version of ensure_dir function test in our environment to check both compiled files in tmp and also create tmp if didn't exist this applies for both scenario.

    Secondly we have filter 'wordless_environment' to override the environment.

    PR: https://github.com/welaika/wordless/pull/283

    features improvement 
    opened by arun744-newscorp 1
  • CopyWebpackPlugin config (silently) bugged

    CopyWebpackPlugin config (silently) bugged

    CopyWebpackPlugin's config in webpck.config.js has a bug at line


    because the dynamic component [folder] doesn't exists; the right way to call the path is [path] as per standard Webpack conventions. I don't know why @danielegiorgis introduced [folder] in https://github.com/welaika/wordless/commit/9f9839f3c79731fdc37025a042489530b870eb8f; I'd bet on a little distraction.

    The effect of this bug is that nested folders in src will be lost in dist, thus erroring path expectations from the frontend.

    opened by pioneerskies 0
  • 5.1.1(Jun 29, 2021)

  • 5.1.0(Jun 3, 2021)

    Added 🆕

    • PUG's filter :php is back on track
    • vanilla theme has responsive embeds support (from wordpress core) enabled by default
    • PHP8 support (thanks to @kylekatarnls)
    • Updated static rendering documentation

    Fixed 🐛

    • Validation errors are now overlayared onto the page, being visible even when inside a nested rendering process
    • Now both define('BYPASS_STATIC', false) and define('BYPASS_STATIC', FALSE) are supported
    • refactored render_template function to not waste CPU time on SHA calculation when static rendering is not required
    Source code(tar.gz)
    Source code(zip)
  • 5.0.0(Feb 1, 2021)

    Full diff from previous release https://github.com/welaika/wordless/compare/4.1.0...5.0.0

    What's new in the major version? 🆕

    • [conventions] For rendering partials and layouts is endorsed a new "pure PUG" approach instead of using PHP helper functions such as render_partial(). New practices are reflected in the updated documentation @ https://wordless.readthedocs.io/en/5.0.0/_pages/usage/rendering_pug.html
    • A new PHP helper render_static() is provided as a strategy to cache partials or whole templates as static HTML files. Usage and info documented @ https://wordless.readthedocs.io/en/5.0.0/_pages/appendix/render_static.html. This tool works only with PUG files.
    • A new class Wordless\Component is provided as a device to write visual components in PUG with validated parameters using PUG's builtins mixins. You can read ratio and usage @ https://wordless.readthedocs.io/en/5.0.0/_pages/usage/filters.html#wordless-pug-configuration
    • [vendor] Mobile-Detect updated
    • [vendor] pug-php updated
    • [vendor] Symphony validator added
    • [vendor] All javascript dependancies (node modules) updated. A special mention goes to Webpack that receives an update to the recent release 5!

    Please be sure to welcome the new "pure PUG" convention, since it will determine a serious performance improvement. Should you have problems refactoring an old theme in order to update it to the new conventions, feel free to open an issue (or ping me in private company chat).

    Warning ⚠️

    • Default pug compile options were updated. Be sure they still fit your project if you're upgrading: https://wordless.readthedocs.io/en/5.0.0/_pages/usage/filters.html#wordless-pug-configuration
    • [conventions] new file naming conventions - as endorsed in the docs - no more relies on underscore-prefixed pug partials. Partials are now called with explicit paths: no underscore magic, no extension omissions.

    Fixed 🐛

    • Fixed a bug during the the setup preventing the correct creation of the test database

    Other changes 📓

    • VSCode plugin recommendations added to vanilla theme (fd269cc)
    • Documentation was re-ordered trying to make it more focused on important things and more readable

    Upgrading from 4.1

    Version 5, while introducing a lot of new practices, naming conventions and scaffolding, retains full compatibility with 4.1's themes.

    Big ups to @danielegiorgis who put a lot of effort in this major release.

    Source code(tar.gz)
    Source code(zip)
  • 4.1.0(Sep 21, 2020)

    New features 🆕

    This release comes with only one big feature: Wordless vanilla theme now is shipped with preconfigured E2E test suite.

    Documentation is updated accordingly, so you can read more about this at https://wordless.readthedocs.io/en/latest/_pages/usage/test_suite.html

    Changes ‼️

    • Composer is a new pre-requisite
    • the installation process in slightly changed (there is a new yarn setup task instead of the old yarn install); pay attention to the documentation on your next setup

    Enjoy! 🌸

    Source code(tar.gz)
    Source code(zip)
  • 4.0.0(Mar 15, 2020)

    Full diff from previous release https://github.com/welaika/wordless/compare/3.0.1...4.0.0

    What's new in the major version? 🆕

    • Moved from SASS to SCSS (breaking)
    • Updated Stylelint rules and config to lint SCSS (breaking)
    • Moved from CoffeeScript to ES2015 (breaking)
    • Updated all the node_modules dependencies

    Warning ⚠️

    This is a major update because it's considered a breaking one. Updating the plugin from 3.x to 4.0.0 should be safe, but you cannot upgrade an existing theme with new configurations. This is true mainly due to the new default supported syntaxes (SCSS and ES2015)

    Fixed 🐛

    • Fixed 2 bugs and improved the helper to register ACF/Gutenberg custom blocks (create_acf_block)
    • Fixed a wrong path declared inside Wordless class
    • Fixed a bug in new_taxonomy with most recent WP versions

    Other changes 📓

    • Updated the logic behind wp wordless theme upgrade: now it is no more intended to upgrade from non-webpack themes to a webpack one, but simply updating theme's build configurations to the new shipped ones
    • Heavily improved documentation, clened up the main README.
    • Documentation reflects all the introduced updates about languages/syntaxes
    Source code(tar.gz)
    Source code(zip)
  • 3.0.1(Jan 2, 2020)


    • 3bf4e7c Hotfix: documentaion node - Add documentation about the node's required version.


    • e787754 Update new_post_type helper to correctly support latest WP versions. Fix #243
    • 41cdf59 update vanila theme .gitignore. Fix #242
    • d4e675f Uniform the use of Pug class to render both in dev and prod
    • d0316bd Update README.md - with new documentation URL
    Source code(tar.gz)
    Source code(zip)
  • 3.0.0(Nov 26, 2019)

    Full diff from previous version @ https://github.com/welaika/wordless/compare/2.7.0...3.0.0

    Breaking changes

    • HAML is no longer supported
    • Themes created with Wordless <3.0.0 are not compatible with Wordless >=3.0.0 due to the changed scaffold

    If you are interested in updating a project you have to study the new scaffold and update it by hand. This will be a hard work and we cannot provide an automagic upgrade for such a big change.


    • bump required node version to current LTS
    • support NVM adding nvmrc
    • Stylelint is supported and configured by default
    • coffeescript will be polyfilled and transpiled by babel by default (w/ browserslist help)
    • Add default configuration for browserslist
    • lint and update default sass (with an image to test image url rewriting done by Webpack)
    • refactor folder structure (partially fixing #239)
    • use mini-css-extract-plugin fix #236
    • readme updated
    • documentation @ https://wordless.readthedocs.io/en/latest/ updated and improved
      • added nodejs section
      • added documentation about how to use multi-entries bundles
      • updated all the references to the old scaffold
      • more! Take a look at it: it's a big effort to keep it up and good :)
    • Webpack configuration now supports multi-entries by default (starts with a single one, but ready to work with multiple)
    • updated all the JS deps
    • updated all the PHP deps
    Source code(tar.gz)
    Source code(zip)
  • 2.7.0(Jun 13, 2019)

    The main shipped feature is a new filter wordpress_pug_configuration that let developer overwrite pug configurations inside the theme. Documentation added at https://wordless.readthedocs.io/en/latest/_pages/usage/filters.html.

    Thanks to @juankk for his contibution.

    Commits highlights

    • cd37d19 Update fixtures and fix unit tests
    • 69c333e Update documentation with filters section
    • da14aa2 Remove pretty from pug config since deprecation
    • bf4fc58 Pug options are exposed through wordpress_pug_configuration filter
    • d8a2768 Update development.md documentation
    • c16722d Update travis badge
    Source code(tar.gz)
    Source code(zip)
  • 2.5.0(Oct 26, 2018)

    Wordless 2.5 deprecates the old ruby preprocessors support. It is disabled by default. If you need to develop an old theme you need to explicitly activate them by setting the following in your wp-config.php

    define('WORDLESS_LEGACY', true);

    Wordless 3 is planned to completely remove this support.

    Source code(tar.gz)
    Source code(zip)
  • 2.4.2(Oct 3, 2018)

    • 4c99e0a hotfix symphony/var-dumper

    Seems that vendor/symfony/var-dumper/Caster/ArgsStub.php has a bug and seems wordpress.org is doing some sort of static code analysis and thus breaking our deployment. Hope the hotfix will unlock this release.

    Source code(tar.gz)
    Source code(zip)
  • 2.4.0(Oct 3, 2018)

    This is a performance related update.

    • 8357d8a assume plugin's composer autoloader will behave as in production env (ref)
    • eec9872 if environment is staging or production, then switch on Optimizer (Phug ref)


    From now on if Wordless will find ENVIRONMENT set up as a constant (in wp-config.php) or as an environment variable and its value is staging or production, then the rendering optimizer will be automatically used.

    Updated the following vendors through composer:

    • Updating nodejs-php-fallback/nodejs-php-fallback (1.3.1 => 1.4.1)
    • Updating symfony/polyfill-mbstring (v1.7.0 => v1.9.0)
    • Updating phug/event (0.1.1 => 0.1.2)
    • Updating phug/lexer (0.5.21 => 0.5.28)
    • Updating phug/formatter (0.5.41 => 0.5.42)
    • Installing symfony/polyfill-php72 (v1.9.0)
    • Updating symfony/var-dumper (v3.4.4 => v4.1.5)
    • Updating phug/renderer (0.4.0 => 0.4.5)
    • Updating phug/phug (0.3.1 => 0.3.2)
    • Updating js-phpize/js-phpize (1.14.0 => 2.0.0)
    • Updating js-phpize/js-phpize-phug (1.1.7 => 2.0.0)
    • Updating pug-php/pug (3.1.6 => 3.2.0)
    • Updating mobiledetect/mobiledetectlib (2.8.30 => 2.8.33)
    Source code(tar.gz)
    Source code(zip)
  • 2.3.2(Sep 24, 2018)

    • ae175fa remove if lt IE 9 comment from vanilla theme's head ( fix #219 )
    • ff500fe update wordless.org readme.txt
    • f225513 rename readme extension and update copyright notice. fix #216

    Thanks @Youdaman for issue reporting

    Source code(tar.gz)
    Source code(zip)
  • 2.3.1(Sep 12, 2018)

    • publish https://wordless.readthedocs.io/
    • fix bug in package.json devDependencies
    • add CopyWebpackPlugin to the build workflow (this was almost a bug)
    Source code(tar.gz)
    Source code(zip)
  • 2.3.0(Jun 8, 2018)

    • 977d83f update theme's yarn.lock

    Previous locked dependencies no more worked with latests versions of node due to compilation errors

    • bd3b551 preserve tmp dir in vanilla_theme

    Themes were created w/o tmp directory - throwing the right warning, but tedious anyway :)

    Source code(tar.gz)
    Source code(zip)
  • 2.2.13(May 12, 2018)

    From version 2.2.0 to version 2.2.13 I've only had problem - and now fixed - with deployment to the wordpress plugin svn directory.

    I'm sorry for the dirty repo history, but now I managed to get it back to work, in a more robust way and integrated Travis' Continuous Delivery.

    Source code(tar.gz)
    Source code(zip)
  • 2.2.0(May 8, 2018)

    Thanks to

    • 6871dcb add subcommand clear_tmp + reindentation

    is now possible to clear the active wordless theme's tmp directory using wp wordless theme clear_tmp. Being sometimes necessary it should now be easier to clear tmp on staging and production too :)

    Source code(tar.gz)
    Source code(zip)
  • 2.1.0(Feb 22, 2018)

  • 2.0.6(Jan 25, 2018)

  • 2.0.4(Dec 16, 2017)

    Upgrade php-pug from 2.x to 3.x. This is a big change behind the scenes, but transparent from the user perspective, so just a minor version bump was done.

    Read more about php-pug 3.x at https://github.com/pug-php/pug#new-in-pug-php-3

    Source code(tar.gz)
    Source code(zip)
  • 2.0.0(Dec 16, 2017)

    This is the first stable release of the all new Wordless.

    • abandoned Ruby/Compass/Haml (but maintains backward compatibility for old themes)
    • embrace Webpack/Phug and all the new bells and whistles
    Source code(tar.gz)
    Source code(zip)
Craftsmen of Ruby on Rails, Elixir, JavaScript and mobile apps. We are a web and mobile development team, located in Turin, Italy.
Automattic 10.7k Jan 2, 2023
Création du thème "mytheme" WordPress from Scratch

<!DOCTYPE html> <html lang="fr"> <head> <meta name="viewport" content="width=device-width" /> <meta http-equiv="Content-Type" content="text/html;

Jules Eulalie 0 Dec 27, 2021
Wordpress advance plugin with multi purposes features like live chat, custom post type, custom forms, word count etc

What is this? This is wordpress plugin which is created for the multi purpose uses. How to use? Simply install the plugin. Go to the plugin settigs pa

Amir Liaqat 2 Jun 23, 2022
This WordPress Plugin Boilerplate is meant for you to develop your own plugin on.

WordPress Plugin Boilerplate This plugin boilerplate is meant for you to develop your own plugin on. Support & collaboration Features OOP plugin core

richardev 2 May 10, 2022
A WordPress package for updating custom plugins and themes based on an API response from a custom update server.

WordPress Update Handler A WordPress package for updating custom plugins and themes based on an JSON REST API response from a custom update server. Ch

WP Forge 7 Oct 5, 2022
Custom WordPress theme for DotOrg

wd_s Debt Collective Theme Table of Contents Introduction Getting Started Prerequisites Quick Start Advanced Setup Development Contributing and Suppor

The Debt Collective 1 Oct 31, 2022
WordPress entities creation library (CPT, CT, native option page, ACF option page, user role, block pattern category, block category…)

WordPress entities creation library (CPT, CT, native option page, ACF option page, user role, block pattern category, block category…)

Loïc Antignac 2 Jul 25, 2022
🚀WordPress Plugin Boilerplate using modern web techs like TypeScript, SASS, and so on... on top of a local development environment with Docker and predefined GitLab CI for continous integration and deployment!

WP React Starter: WordPress React Boilerplate DEPRECATED: WP React Starter was a "research project" of devowl.io for the development of our WordPress

devowl.io GmbH 344 Jan 1, 2023
WordPress plugin boilerplate using React and Block Editor components.

PluginWP Foundation ?? UNDER DEVELOPMENT ?? This code serves as a starting point for building a WordPress plugin using React and the block editor comp

JR Tashjian 5 Dec 8, 2022
WordPress Plugin Boilerplate

This repository, developed by the team of Plugins & Snippets, offers an open source WordPress Plugin Template with many useful functions, specially to prepare basic widgets, short codes and settings page. The aim of this Boilerplate Template is to save time for WordPress Developers in building high-quality plugins.

null 3 Dec 15, 2022
Word Count (Custom WordPress Plugin)

word-count (Custom WordPress Plugin) Followed a tutorial to create a plugin that adds word count infos to the frontend (Posts only). I then modified t

null 1 Feb 4, 2022
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
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
WordPress plugin working (almost) like a child theme.

Step child Description TL;DR: WordPress plugin working (almost) like a child theme. Sometimes the project you're thrown into doesn't have a child them

Johan Jonk Stenström 2 Jun 10, 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
Tema boilerplate WordPress

WordPress boilerplate based on _s Hi. I'm a starter theme called _s, or underscores, if you like. I'm a theme meant for hacking so don't use me as a P

Victor Ribeiro 1 Dec 16, 2021
Create custom WordPress routes and redirects, restrict access by roles and/or capabilities. Routes made simple

Create custom WordPress routes and redirects, restrict access by roles and/or capabilities. Routes made simple

Joan 9 Oct 10, 2022
A custom update API for WordPress plugins and themes

A custom update API for WordPress plugins and themes. Intended to be used in conjunction with my plugin-update-checker library.

Yahnis Elsts 717 Dec 31, 2022
A PHP Class for creating Wordpress Custom Post Types easily

N.B I've released an updated version of the project to a new repository, PostTypes. WP Custom Post Type Class v1.4 A single class to help you build mo

Joe Grainger 412 Nov 25, 2022