Build One Custom Gutenberg Block with Code-Splitting — $200 Fixed

I need an experienced Gutenberg developer to build a single custom block for a WordPress site. Clean code, code-split build, ready to ship. The block A content card block that displays a curated list of items pulled from a custom post type. Editor controls: - Select source CPT (dropdown) - Filter by two taxonomies (multi-select) - Number of items (range control) - Layout variant (grid / list, ButtonGroup) - Show/hide thumbnail, excerpt, meta (toggles) Frontend: server-side rendered via `render_callback`. Editor: live preview using `useSelect` against `core/store`. **Requirements** - Built with `@wordpress/scripts` (wp-scripts) - Code-splitting configured — editor bundle and frontend bundle must be separate, with shared code extracted - Block registered via `block.json` (block API v3) - Uses `@wordpress/components` for all controls — no custom UI library - PHP render callback, no client-side rendering on frontend - Proper i18n (`__()` everywhere, text domain provided) - PHPCS-clean against WordPress Coding Standards - ESLint-clean against `@wordpress/eslint-plugin/recommended` **Deliverables** - Plugin folder, ready to drop into `/wp-content/plugins/` - `package.json` with build scripts - `block.json`, `edit.js`, `save.js` (or dynamic), `render.php`, `style.scss`, `editor.scss` - README with build instructions and any decisions made - Git repo (GitHub or GitLab) with clean commit history **Budget and timeline** - $200 fixed price - 5–7 days from kickoff - Two milestones: working block in editor (50%), code-split build + cleanup + handoff (50%) **To apply** Do NOT send a generic proposal. Send: 1. A link to a custom Gutenberg block you have built (repo preferred, live site acceptable) 2. One sentence on how you would configure code-splitting in `wp-scripts` — what entry points, what gets shared 3. Confirmation you can work to PHPCS WordPress Coding Standards Proposals without these three items will be rejected without reply.