Download the PHP package emulsify-ds/emulsify-wordpress-theme without Composer

On this page you can find all versions of the php package emulsify-ds/emulsify-wordpress-theme. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package emulsify-wordpress-theme

Emulsify Design System

Emulsify WordPress

Emulsify WordPress is a Timber-first WordPress parent theme for teams building component-driven sites with Emulsify Core 4, Vite, Storybook, and Twig.

The parent theme provides the WordPress runtime: theme setup, Timber bootstrapping, Twig namespaces and helpers, template fallbacks, asset loading, and optional block registration. Generated child themes provide the project layer: components, templates, source Sass and JavaScript, compiled assets, and site-specific overrides.

Installation

Composer (primary)

Track the parent theme through the site project's Composer configuration and install it as emulsify:

The Composer package uses installer-name: emulsify, so Composer Installers places it under the required parent-theme slug. Composer-based applications should also require timber/timber from the application-level Composer project so Timber loads before WordPress activates the theme. If the parent theme owns its dependencies instead, run composer install inside the installed emulsify directory.

Manual release ZIP

Download the emulsify.zip asset from the matching GitHub release, then upload it through Appearance > Themes > Add New > Upload Theme. The release ZIP already includes production Composer dependencies under vendor/ and the bundled Whisk generator source, so a manual installation does not need to run Composer.

The archive installs into the required emulsify/ directory. A WordPress.org listing and SVN deployment are planned as a future release step; they are not part of the current release workflow.

Before a public release is available, the PHP 8.3 Practical theme readiness job uploads the built emulsify.zip directly as a short-lived workflow artifact for client testing.

Use the named emulsify.zip asset, not GitHub's automatically generated Source code archives, for a manual WordPress upload. Composer distributions retain composer.json and let the site project resolve PHP dependencies; the manual asset bundles those dependencies. A direct Git clone is a maintainer checkout and intentionally contains CI and release tooling. Tagged Composer/GitHub distributions exclude that repository-only material through .gitattributes while retaining the user documentation linked below.

Requirements

Using Emulsify WordPress in a site project

Install the parent theme as emulsify and pair it with a child theme for project work. In Bedrock, that usually means:

In a standard WordPress install, use:

Timber 2 must be loaded before the theme renders. Composer-based site projects can satisfy that requirement in either place:

Activate the child theme, not the parent theme. The child theme header includes Template: emulsify, which tells WordPress to use Emulsify as the parent runtime.

Do not run root npm commands in the parent theme for normal site implementation. Project frontend work happens in the generated child theme.

Working inside a generated child theme

Run component, Vite, Storybook, and project lint commands from the generated child theme:

Command Purpose
npm run build Build Core 4 assets with Vite.
npm run vite Watch and rebuild Vite assets.
npm run storybook Start Storybook on port 6006.
npm run develop Run the Vite watcher and Storybook together.
npm run storybook-build Build assets and export a static Storybook.
npm run lint Run JavaScript and Sass linting with the Core 4 config.
npm run audit Run the Core migration/static audit.
npm run audit:twig-stories Check Twig story compatibility.
npm run inspect:components Discover components and report metadata, dependencies, configuration issues, and orphaned files.
npm run a11y Build Storybook and run the Core accessibility check.
npm run test Run project Jest tests with coverage; fails when no tests exist.

The component inspector comes from the installed @emulsify/core package and runs from the generated child theme root without requiring WordPress to be installed or bootstrapped:

Parent and child themes

The emulsify parent theme owns reusable runtime behavior:

The generated whisk child theme owns project implementation:

Bedrock and Timber

Timber is required for frontend template rendering. This repository declares timber/timber in the parent theme composer.json, so a standalone theme install can run Composer inside the parent theme.

For Bedrock applications, it is also valid to require Timber from the application-level Composer project as long as WordPress loads that Composer autoloader before the theme renders. If Timber is missing, the parent theme shows an actionable admin notice and stops frontend rendering with a clear runtime error.

Developing or releasing the parent theme

Parent-theme root commands are for maintainers and release checks, not normal project frontend development. Run them from the parent theme repository root:

Composer install creates the runtime autoloader. After adding or renaming parent runtime classes, run composer dump-autoload so Composer's optimized classmap sees the current files. The supported manual release ZIP ships that autoloader and its production dependencies; a source checkout without vendor/ still uses the Bootstrap fallback loader.

Linting and static analysis

Install the PHP development dependencies, then run the combined coding-standards and static-analysis command:

lint:php runs PHPCS with phpcs.xml.dist, followed by PHPStan with phpstan.neon.dist. Both configurations cover includes/ and the parent theme's root PHP entry points, including functions.php. Use npm run lint:php:fix to apply safe PHPCBF coding-standard fixes, then rerun npm run lint:php to confirm PHPStan and the remaining PHPCS checks.

The .husky/pre-commit hook runs npm run lint, which delegates to this PHP check. A normal npm install installs Husky 9 hooks in clones and worktrees. After installing with npm ci --ignore-scripts, enable local hooks with npx --no-install husky.

Command Purpose
npm run lint:php Run PHPCS and PHPStan across the parent runtime.
npm run pr:check Run the practical, stubbed pull request validation suite.
npm run release:check Run release-readiness checks.
npm run build:dist Build the installable dist-artifact/emulsify.zip release archive.
npm run publish-test -- --no-ci Run a local release dry run after meeting the prerequisites.

Every pull request to the configured branches runs two visible fast readiness jobs: practical smoke checks and dedicated PHPCS/PHPStan analysis. Pull requests targeting main or release-2.x additionally run the MySQL-backed WordPress fixture and Whisk Storybook accessibility audit. The PHP 8.3 practical lane builds emulsify.zip; the WordPress jobs verify and extract that same archive, confirm its packaged generator and Whisk source, and set WP_SMOKE_REQUIRED=1, so missing WP-CLI/MySQL prerequisites or route render failures fail the job instead of producing a skip. They also audit seven actual WordPress routes, including YouTube and Vimeo posters, with explicit WCAG 2.2 AA axe tags and save rendered HTML, results, and navigation evidence. The sole target-size exclusion reflects the unstyled parent; projects own target sizing and focus/helper styles. See accessibility checks.

Practical checks block on PHP 8.3, 8.4, and 8.5. The WordPress fixture blocks on the minimum 6.8 and on latest, resolved at run time with the downloaded version logged; nightly coverage is advisory. The theme is tested through WordPress 7.1 (the current stable fixture resolved to 7.1.3 on October 23, 2026).

The Whisk job selects and verifies the runner-installed Chrome with its sandbox enabled, copies an accessible CI-only story and Vite entry into the otherwise component-agnostic starter, runs seeded project tests, and then builds Storybook and runs axe. Storybook coverage supplements the actual WordPress route audit.

Weekly scheduled runs repeat the WordPress fixture and Whisk accessibility audit. Manual GitHub Actions > WordPress Theme Readiness runs can select either extended fixture with the wordpress_fixture and extended_checks inputs. Local release:check still skips the database fixture when prerequisites are unavailable unless WP_SMOKE_REQUIRED=1 is set. Release publishing also requires the full WordPress fixture path before semantic-release can publish.

Generate a child theme

Generate a project child theme from the bundled Whisk starter with WP-CLI:

WP-CLI must point at the actual WordPress core directory so WordPress can load the active theme and register the command. In a Bedrock/DDEV project with core at web/wp, add path: web/wp to the project's wp-cli.yml, or run ddev wp --path=web/wp emulsify "Acme Site" --dry-run. See the WP-CLI guide for the complete configuration and troubleshooting steps.

The generator copies <parent>/whisk to a sibling child theme directory, updates WordPress theme headers, package metadata, Emulsify project metadata, and visible starter labels, then optionally activates the generated child theme. --parent=<slug> selects a different installed parent theme directory; it defaults to emulsify.

--force only replaces an existing destination when its WordPress platform, generatedFrom: "emulsify-wordpress" lineage, generated version, parent template, and machine name all match the requested generated child theme. The replacement is staged atomically so a copy failure leaves the existing theme intact; use --dry-run --force to inspect replacement intent without deleting files.

For Emulsify CLI integration, the standalone starter repository is https://github.com/emulsify-ds/emulsify-wordpress-starter. It represents the generated child theme layer from whisk/, not the parent runtime theme root, and generated projects still declare Template: emulsify so WordPress loads the installed parent theme.

Documentation

This README, UPGRADE.md, and the guides in this repository are authoritative for the WordPress 2.x workflow. The Emulsify documentation site also covers older tooling and other platforms; check a guide's platform and version before using its commands.

License

Emulsify WordPress is licensed under GPL-2.0-only. See LICENSE.

Contributing

Read the contributor guidance for repository ownership, both child generators, validation commands, and release rules.

Code of conduct

Read the Code of Conduct before contributing. File bugs and feature requests at emulsify-ds/emulsify-wordpress.

Committing changes

This repository uses Conventional Commits. Commit messages drive semantic-release, so the type determines the next version:

The .husky/commit-msg hook validates the format with commitlint after local hooks are installed. See docs/release-process.md for the full version strategy.

Release readiness

Before opening a release pull request, run the local checks:

docs/release-process.md documents the release checks, CI coverage, and the publish gate.

Author

Emulsify® is a product of Four Kitchens — We make BIG websites.

Contributors


All versions of emulsify-wordpress-theme with dependencies

PHP Build Version
Package Version
Requires composer/installers Version ^2.3
php Version >=8.3
timber/timber Version ^2.3
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package emulsify-ds/emulsify-wordpress-theme contains the following files

Loading the files please wait ...