Thank you for considering contributing to h2b!
- Check existing issues - See if the bug has been reported
- Create detailed report - Include:
- Input HTML/CSS
- Expected Bricks JSON output
- Actual output
- h2b version
- Error messages
- Check existing feature requests
- Open issue with:
- Use case description
- Example input/output
- Why it would be valuable
We welcome new working examples!
Requirements:
- Must use flat structure (ID-based relationships)
- All required fields present (id, name, parent, children, settings, label)
- 99.5%+ native properties
- Test in Bricks Builder
- Include README.md with features demonstrated
Example structure:
examples/04-new-example/
├── component-name.json
└── README.md
- Fix typos or unclear explanations
- Add examples to reference guides
- Improve SKILL.md clarity
JSON formatting:
- 2-space indentation
- Flat structure (no nested children objects)
- Required fields order: id, name, parent, children, settings, label
Bricks JSON requirements:
{
"id": "unique-id",
"name": "element-type",
"parent": 0,
"children": [],
"settings": {},
"label": "Display Name"
}- Fork the repository
- Create feature branch -
git checkout -b feature/new-example - Make changes following style guidelines
- Test in Bricks Builder - Ensure JSON works
- Commit with clear message
- Push to your fork
- Open Pull Request with:
- Description of changes
- Why it's needed
- Screenshots/examples if applicable
Before submitting:
- ✅ JSON is valid
- ✅ Flat structure used
- ✅ All required fields present
- ✅ Paste works in Bricks Builder
- ✅ No console errors
Open an issue or reach out to @iamfilipp
Thank you for contributing! 🎉