How eighteen73/pulsar works
Project type and purpose
• This is a WordPress “block theme” starter project called Pulsar. Its purpose is to provide a modern development workflow for building and delivering a custom WordPress theme that uses the block editor, theme.json, custom blocks, patterns, template parts, and asset pipelines (JS/CSS).
File structure
• Top-level theme files: style.css (theme header), functions.php, theme.json.
• Config folder: block and pattern configuration for the block editor.
• includes/: PHP classes and bootsrap (autoload.php, Setup, Enqueue, Editor, Tools, ThirdParty integrations).
• parts/ & template-parts/: static HTML/PHP fragments (header, footer, etc.).
• patterns/: predefined block patterns and 404 template.
• src/: source assets
• src/js: application JS, block filters/styles/variations, editor plugins.
• src/css: Sass partials organized by settings/elements/generic/components, etc.
• src/blocks: a custom “template-part” block with block.json, edit.js, index.js, render.php.
• Build and config: package.json, webpack.config.js, babel.config.json, postcss.config.js.
• Playground and demo support under .playground/.
README for additional insights
• Confirms it’s a WordPress >=6.6 theme requiring PHP >=7.4 and Node >=16.
• Describes npm build commands: start a dev watch (with Browsersync) and production build.
Elements
• Dev Tools / Build System
• Source Assets
• Compiled Assets
• Theme PHP (includes, template-parts, patterns)
• WordPress Core & Database
• Browser / Client
• External Integrations
• From Source Assets → Dev Tools → Compiled Assets
• From Compiled Assets + Theme PHP → WordPress Core
• From WordPress Core + Database → Browser
• Any callbacks or hook integrations (e.g., Block Editor → Theme Editor classes)
• Another for theme source & runtime PHP
• Another for WordPress Core & DB
• Another for external integrations