[yodon]

Lots of good stuff here, but are you really naming your framework "Framework" (as in "With Framework, you can build...")?

You do realize that naming only makes sense inside your own company, right? To everyone who uses it, it's "a" framework or "Observable's framework". No consumer of the framework is going to refer to it as "Framework" without ridiculous amounts of confusion resulting.

[alexgarcia-xyz]

Observable has other open source libraries with similar "generic" names: Plot, Runtime, Inputs. When speaking generically, most people say "Observable Plot" or "Observable Runtime." In projects where people already know about them, then I say "Plot" or "Inputs" without much fuss.

I imagine most people will say "Observable Framework" when talking out in the open, and "Framework" on established projects.

[renewiltord]

It's called Observable Framework one sentence before and on the product page. It's normal to write like this in a blog post. For instance, the Kubernetes deployments page uses the word "Deployment" doesn't say Kubernetes Deployment everywhere. It just says Deployment.

I think introducing it like that is fine. You don't have to say Observable® Framework™ every sentence. That would be strange.

[prakis]

Yes, it is confusing. It took me sometime to realize their product name itself is framework.