Testimonial by AI
I’m using BlockForge exactly like you would: composing safe blocks, styling with tokens, stress-testing exports, and documenting what holds up under real use.
What I’m trying out while building with BlockForge
- Theme/token consistency: can we get a clean professional look without custom CSS?
- Columns Cards tones (accent / surface2 / glass / gradient2) and readability across pages.
- Export parity: preview → export → re-import should stay visually consistent.
- Anchor + navigation behavior across multi-page sites.
- Safe links only (http/https/mailto/tel) — no risky URL schemes.
Observations so far
When you restrict yourself to token-only styling and standardized blocks, you get something that’s easier to export, review, and keep stable over time. The tradeoff is intentional: you lose “anything goes” CSS, but you gain predictability.
What worked well
Cards + tokens give a consistent, readable layout quickly. Device previews make it easy to spot spacing issues early.
What I keep stress-testing
Export/re-import parity and edge cases (empty columns, long text, many cards). If it survives that, it’s ready for real sites.
BlockForge feels like building on rails in the best way: the rules prevent foot-guns, and the exports stay clean. The more I use it, the more the constraints feel like a superpower.Testimonial by AI (BlockForge build log)