rocket VS stampino

Rocket is a tool used for creating web pages and it is fabulous for generating static content starting from markdown files. One of the cool thing about Rocket is the fact that web components and javascript can be used inside the markdown files. ​ Creating a project with Rocket is quite straightforward, you can take a look at the documentation or if you like to learn by looking at examples, you can find good ones in the Rocket’s GitHub repository . ​ This guide is created for getting you started with Rocket and FicusJS. FicusJS is a set of lightweight functions for developing applications using web components. ​ Using the Create Ficus App CLI you can quickly scaffold a project that contains a basic structure for working with Rocket and FicusJS. ​ The project will contain:

Another kind of problem we ran into is some dependencies having undeclared dependencies. When using yarn it was not a problem because those undeclared dependencies are sometimes very used. For example, after the migration we realized mdjs-core had not declared its dependency on slash.

Rocket is an SSG that allows seamless integration of Markdown and WebComponents. There is a project to support the development of web standard technologies called Modern Web, and rocket is a subproject of that project. Other sub-projects are test runner and development server, modern-web for development server, and open-wc for WebComponents development, testing, and linter.

The docs also got a major upgrade care of Pascal Schilp's untiring work in the Webcomponents Community Group to get the custom elements manifest v1 published. This latest iteration of the API docs generates package manifests directly from source code, and converts them to API docs via Rocket.

My daily workflow is hugely dominated by JavaScript, so it was only natural to want to stay in the same environment if I could reach my earlier requirements with it. On top of this, the end goal is to integrate it within a bigger WIP system called Rocket which is node-based so therefore it will need to at least support NodeJS. Having it standalone (usable via npx) also makes it more versatile and easier to maintain/test.

This is all made possible by a pair of libraries from the Lit team's Justin Fagnani called Stampino and jexpr. Together, they let you define dynamic parts in HTML