Edgebeam Theme Blocks
Custom blocks for Edgebeam.
★ 0stars
0forks
Install
No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:
wp plugin install https://github.com/nickfmc/edgebeamblocks/archive/refs/heads/main.zipTheme Blocks
Custom WordPress blocks plugin built with wp-scripts.
Development
-
Install dependencies:
npm install -
Start development with hot reloading:
npm run start -
Build for production:
npm run build
Available Scripts
npm run build- Build the blocks for productionnpm run start- Start development mode with hot reloadingnpm run format- Format code with Prettiernpm run lint:js- Lint JavaScript filesnpm run lint:css- Lint CSS/SCSS files
Blocks
- Hello World (
gdt-ng/hello-world) - Example block scaffolded with Create Block tool
Features
Auto-Discovery
Blocks are automatically discovered from the src/ directory. Just create a new block folder with a block.json file and it will appear in the settings.
Performance Caching
Block discovery is cached for 1 hour to eliminate filesystem overhead. Cache automatically clears on:
- Plugin activation
- Version updates
- Manual clear in settings
Dev Mode: When WP_DEBUG is enabled, caching is disabled for instant block updates.
Admin Settings
Manage blocks via Settings > Theme Blocks:
- Enable/disable individual blocks
- View block information
- Clear block cache
- See plugin statistics
Structure
theme-blocks/
├── src/ # Block source files
├── build/ # Compiled blocks (generated)
├── includes/ # PHP classes
│ ├── class-block-registry.php
│ └── class-admin-settings.php
├── admin/ # Admin assets
│ └── css/
│ └── settings.css
├── _docs/ # Documentation
├── theme-blocks.php # Main plugin file
└── package.json # npm configuration
Documentation
See _docs/ folder for detailed documentation:
planning-questions.md- Strategic planning guidecaching-system.md- How caching works