Title: Source <a href="https:&#x2F;&#x2F;github.com&#x2F;dashborg&#x2F;hibiki" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;dashborg&#x2F;hibiki</a> | Interactive Tutorial <a href="https:&#x2F;&#x2F;playground.hibikihtml.com&#x2F;tutorial&#x2F;" rel="nofollow">https:&#x2F;&#x2F;playground.hibikihtml.com&#x2F;tutorial&#x2F;</a><p>I love JavaScript, but for many projects -- especially internal tools and prototypes -- setting up a full frontend JavaScript stack (npm, webpack, babel, create-react-app, redux) and all of their configuration files, folders, and scaffolding is overkill.<p>Hibiki HTML incrementally plugs into any backend, using any template language (even static HTML files) with a single script include.  It includes a built-in frontend data model, Vue.js-like rendering, built-in AJAX integration, and a full component&#x2F;library system.<p>It is also <i>fully scriptable</i> from your backend AJAX handlers.  Anything that Hibiki HTML can do on the frontend can be done with a remote handler by returning specially formatted JSON <i>actions</i>.  This allows you to write frontend logic (that would normally be JavaScript code) in your backend handlers.<p>Background -- Hibiki HTML is a standalone, open-source, more powerful version of the frontend language that I had built for my internal tools startup Dashborg over the past year.  It is a reaction against the extreme amount of scaffolding and configuration required to set up a new frontend project, especially when you&#x27;re a backend&#x2F;devops&#x2F;data engineer who isn&#x27;t a JavaScript expert.  As more Hibiki libraries are written, the advantages will hopefully become even more clear.<p>I&#x27;d love to get all of your feedback, questions, and comments.  Would love a star on Github if you like the idea.  Also, feel free to email me, and&#x2F;or join the Slack workspace I set up (contact info on Github or the tutorial).
Upvote: