[Suggestion] Usage of GitOps

[Zeratoxx]

Hi!

I found your Add-On as I needed it the most and love it since then.

I saw, there are no GitHub Actions. I think, this would improve the workflow on this Add-On as it makes possible to for example automatically build a new release of the Add-On and publish it to the various market places.
It would be also possible to build the Add-On in the state of a Pull Request so that it is easy to verify if a PR is working properly.
There are many more options and possibilities.

I offer myself to implement it.. after it is clear if and what should be implemented :D

[FallenMax]

Hi @Zeratoxx ,

Thank you so much for your suggestion and offer to contribute. We really appreciate your interest in this project and agree that automated release processes can greatly improve the workflow.

However, at the moment, Smart TOC includes both free and paid features and the latest code is not open-source. I'm trying to figure out the best way to open-source it (perhaps making it completely free). My current plan is to open-source a general headless TOC component (in vanilla JS), to allow more websites to quickly create a usable TOC that can benefit a wider range of users (even those who don't use Smart TOC).

As for the Smart TOC itself, I personally prefer to keep it small and simple instead of full-featured and complete. I also have no plans to hard-code TOC heading rules for different websites in the code that are not respecting HTML standards. Of course, this is not set in stone and I am open to hearing more user feedback and suggestions.

I would love to learn more about your specific needs and ideas for improving the Add-On. Could you please share more about your use case and what changes you would like to see?

Thank you again for your contribution and suggestion!

[Zeratoxx]

@FallenMax I see your points, well then.

I am using Smart TOC on sites where the navigation is somehow rough or not intuitive.

I searched for something like Smart TOC because a documentation site was too long and had an inadequate TOC (documentation of Strimzi, a Kubernetes Operator for Strimzi, to be exact).

With Smart TOC, I am happy now :D