3 ms·
Perhaps it would be easier to go through a few typical use cases and implementations, and describe how they work with less brand naming and technical fancywords
by alienbaby 1y ago
Perhaps it would be easier to go through a few typical use cases and implementations, and describe how they work with less brand naming and technical fancywords.
I scanned the github, and your reply above, and I still don't really get it.
I imagine I would understand it better if I was more fluent in the vocabulary you use and understood what some of the platforms and interesting names did from the get go.
So yea, my 2p - break it down into some use cases from simple - intermediate - advanced, use more straight forward language and less platform / product names. Technical terms are fine, but try not to string a zillion of them together all in one go... it reads a bit too much like a sales pitch trying to cram in as many acronyms and cool sounding things as possible.
- geoctl 1y agoI honestly don't understand where the "sales pitch" part is. This project has been so far a solo effort and I am the one who basically wrote all the code. It's not like this is some VC-backed product where I am a marketing guy replying to you. I would appreciate it if you could provide me direct questions about what you don't understand so that I can answer you.
- homarp 1y agodefine all the terms. explain simple use cases. explain why you built it, how you use it. explain the 'size' of it (it requires k8s so might not be for my small homelab) compare to 'similar' offerings.
- reachableceo 1y agoI do agree with that. As a potential customer , reading over the page, it was incredibly redundant / dense. I recommend using an LLM to rewrite it far more succinctly.