I finished the last part of my @getkirby series about how to build a component based #styleGuide.
https://flokosiol.de/articles/component-based-styleguide-kirby-cms-3
I finished the last part of my @getkirby series about how to build a component based #styleGuide.
https://flokosiol.de/articles/component-based-styleguide-kirby-cms-3
Found a really useful kirby plugin for debugging https://github.com/Treast/kirby-debugbar
Drupal and Joomla are fairly heavy solutions themselves. Depending on your needs, you might look at #KirbyCMS. It's PHP-based, very dev-friendly, and uses files & folders—no database—so always quick. Not free, but live-site licensing is pretty affordable, and the in-house & community support is great.
I really love Kirby CMS but I struggle a lot with debugging things in it.
Often if somethings not working it's very hard to figure out why. I either have a data structure wrong or I don't know what fields are in the structure.
The documentation also misses a bit. It reads more like a manual than a true reference. I would expect a single spot with every possible option listed but it's broken up into small sections and sometimes doesn't even list a possible setting.
🚀 Mein VSCode-Plugin Kirby Snippet Opener hat ein Update bekommen – danke an @medienbaecker! 🙌
👉 Jetzt im Marketplace: https://marketplace.visualstudio.com/items?itemName=zntgrf.kirbysnippetopener
Ideal für alle, die mit Kirby CMS arbeiten und Snippets schneller öffnen möchten. Feedback ist wie immer willkommen!