Isso VS view_component

I deploy my static blog via rsync. I also have Isso [0] on it. No need for a back-end web framework or anything.

[0] - https://isso-comments.de/

I use Isso myself, which is pretty easy to implement into a site created with Hugo.

Hugo even has a disadvantage when it comes to blogs. There is no comment function by default. I therefore additionally use the Isso commenting system.

I just use isso (https://isso-comments.de/). It's simple and elegant, easy to integrate, and just works without requiring people to login/signup, and allows moderation.

If I were you, I would consider whether a self-hosted solution such as Isso Comment might also be an option. I personally don't like it when my comments are stored at third parties.

I would use one of the static website generators for such a page. I use Hugo myself. If you want a comment function, Isso would be worth a look.

Isso (Self-hosted, Python) (tutorial)

As a comment system I use Isso.

When searching for examples of table components built with the ViewComponent gem, I was surprised to find none. After some inquiries, I came across examples that worked like this:

View components offer two primary ways to interact with the component: passing arguments to the initializer and using slots:

For example, splitting out views into partials? Or the new ViewComponent feature that's becoming quite popular - https://viewcomponent.org/

I used to do "pure ruby" approach to that -- but basically wound up realizing I was re-inventing github's view_component. Their design goals were similar enough to what I was trying to do, that it made more sense just to use that, rather than try to re-invent it myself.

ViewComponent

The linked one is my Rails implementation, written for ViewComponent. The official version uses Nunjucks.