the kubefirst open source platform and the kubefirst pro user interface need stronger lines of delineation throughout our docs.
gitlab has a similar problem, and use a [PRO] label in their docs when they're talking about pro stuff. i would be in favor of a similar technique, but open to interpretation to produce the best user experience
As soon as we have clear information on what will be in the PRO edition as I think it changed since our initial discussion, please update this issue, and I will update the docs.
the kubefirst open source platform and the kubefirst pro user interface need stronger lines of delineation throughout our docs.
gitlab has a similar problem, and use a [PRO] label in their docs when they're talking about pro stuff. i would be in favor of a similar technique, but open to interpretation to produce the best user experience