You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This discussion started here, but I'd like to continue it outside of that issue to increase transparency and to prevent the technical discussion from getting sidetracked.
I'd also like to float the idea of making custom prefix/tag names a premium option, as many (most?) "white-labelers" will be using this feature to bring Shoelace into their org's design system. This might seem like a big assumption, but I haven't seen any other use case for needing to change tag names. If you're using Shoelace that way, I think it's more than fair to ask for a reasonable license fee since even one component can save your company a significant amount of money in design/engineering expenses.
I appreciate that this might be disappointing to some folks, but I'd like to spend more time on Shoelace and, in order to do that, I need to be able to justify it as more than just a free side project. I have a handful of amazing sponsors, but it's not nearly enough to drop my other obligations. A premium option like this could solve that.
By the way, this month (July) marks the two year anniversary of Shoelace 2.0's release!
If the white-labeling option is approached as a paid option, and you setup like subscriptions and accounts for consumers, then that would enable you to generate each special version of shoelace for every account according to their settings whenever shoelace changed and still be able to host those custom versions on a CDN if you wanted to.
If there was a subscription plan/membership thing, then i can imagine that each subscriber gets their own custom CDN url for shoelace that would serve up their specifically generated version in case they wanted to use shoelace from CDN.
Maybe the combination of both CDN hosted custom shoelace versions AND the shoelace generator would be a good offering to justify the subscription cost?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This discussion started here, but I'd like to continue it outside of that issue to increase transparency and to prevent the technical discussion from getting sidetracked.
A great suggestion came from @michaelwarren1106:
Beta Was this translation helpful? Give feedback.
All reactions