> Yep! As long as what you're building is some sort of actual website and not a derivative component library, theme builder, or other product where the primary purpose is clearly to repackage and redistribute our components, it's totally okay for that project to be open source.
> Yep! As long as what you're building is some sort of actual website and not a derivative component library
The license itself doesn't seem to have clear relicensing/sublicensing terms, so it's not clear at all how it works for either open source or proprietary products. If it actually does allow downstream open source licensing, then while it prevents the direct licensee from creating a component library, it doesn't prevent a downstream licensee of the open source product from doing so; if it's usage restrictions (which on their own would prevent a project from being open source) continue to apply to downstream users, then it cannot be used on open source projects.
while im not a lawyer, that does sound extremely far fetched.
you're also allowed to publish code with an MIT licence which can only be used with a 100% proprietary binary blob which can only be acquired by paying a third party.
the specified licence only applies to the published code after all.
said code might be useless without a licence to use that binary blob, but that has no meaning wrt the published open source code.
> Yep! As long as what you're building is some sort of actual website and not a derivative component library, theme builder, or other product where the primary purpose is clearly to repackage and redistribute our components, it's totally okay for that project to be open source.
https://tailwindui.com/pricing