Alternative Frontends

[ghost]

Hi searxng maintainers. Thank you so much for such a POWERFUL launching point. I have created truly something I find wonderful in my daily life - your documentation is unbelievable, the docker container is so well thought out, and truthfully from the bottom of my heart, thank you for your work.

I have been building a next.js frontend instead of using searxng's built in front end. I was wondering:
-if i cleaned it up, is this something that is of interest to give user alternative? my front end isn't the best, but I have it running locally off json user settings store, took care to keep all stuff local, and it provides some very simple local integrations for Obsidian, Tartube (in case users maintain their own front end and don't like public instances), Obsidian, I added a "quick links module" to show on the roots page, it auto favicons, and I have some fun AI RAG work where I have an LLM take user query and select between engines dynamically. Oh and, currently stuck on YACY, Mealie, and FreshRSS integrations - something about API calls across docker containers through my backend as middleware is catching me I think - can't tell if it is searXNG docker interaction in my limited knowledge though.

Plus, tech isn't there yet for inference time to be acceptable outside a "deep research" or gamified "tower defense" style "build your own adventure" search, but I am having fun with it and am interested in what your take is on that sort of thing and if forking or the content posted in a certain format would be of interest. I work in AI, and am in the process of obtaining a 5090 to test these modules I built on some real hardware.

BUT I am to the point where I am at the advanced use - and interested in some guidance on YACY and other docker containers on the same "sear_net" I set up. I just can't get the ding dang things to serve my API and cannot determine if it is a me thing or if I'm improperly setting it up in searXNG. I created a "engine loadouts" system in mine as well for quick engine profiles (some of this is prolly already in the other front end), but I took care to include everything I could and even worked around some server/client side updates to settings.yml for personal users that don't run searxng front ends. It'd be awesome to get a quick moment/glance from the peeps who made searXNG. Feel free to ignore too but:

Let me know if you have time, I'd love to donate you some cash as a sponsor and pick your brain. Name your price. I will contribute to the docs with a large section on "making your own front end" with things like "dockerside settings.yml settings vs settings you can overwrite", "how to troublesheet between searxng, custom front end, settings stores, backend/middleware between container and front end and how to handle/what might happen" how to "store user profiles through the front end locally when self hosting", "how to handle local integration/storage communication with users if publically hosting this off the beaten path approach", things like that. Some of this might already be taken care of by your container, it's sometimes hard to grasp how effective and wide your tool spans so forgive me if I missed some simple things. Both repos (FE and BE are on my profile - slysearch)