Today I’ve been fixing more bugs in the compilation process, particularly with recursive/nested includes and css tags.
But more interesting (to me at least) was that I wanted to create a PoC for a very specific use case for Hammer that fits with our new direction for Forge - Plugin Development.
I created the first of what will I hope be a number of optional utility tags to support plugin development on all the amazing platforms that are out there (and those to come).
I’ve started with Miro, the visual collaboration workspace.
The <!— @miro —> tag will unlock the magic:
- It will automatically add the necessary Miro SDK and Mirotone CSS files to your html page and initialise the SDK by generating a Miro specific js file that is added to your assets/js folder.
- It will generate a Miro test environment wrapper via a mock.html file and companion js file that will give you the option to load your plugin in a mocked UI to test it out, simulate and debug SDK requests and payloads, so you don’t have to actually run it in the Miro app, saving a lot of time during development.
- When/if you decide to remove the Miro tag, Hammer cleans up after you removing all the files
- If you’re using Cursor editor, Hammer extends your .cursorrules file with content specifically tailored to development of Miro plugins using Hammer, so you can get AI to help you write code and test faster.
Next up I’d like to explore passing arguments to the Hammer tag for more fine tuned control, especially for the setup - probably starting with specification of the extension point being used (panel, modal, background)