Building the primitives   T H E   P L A T F O R M   should have had the whole time.

A common thought within companies about headless libraries, or "generic libraries" _at all, is that there is a fear of choosing a library, and over time, that library becoming abandoned. This has happened all over open source, and can be a motivator for folks shying away from open source, and re-implementing everything themselves.

To help alleviate this fear, the Universal Ember org has been created to help share ownership of libraries, to improve the bus factor beyond 1 person, or 1 company.

If you have a project that you'd like to share the maintenance burden of, message me in the Ember Discord @NullVoxPopuli, and we can help improve the busfactor, and help companies feel reassured in the decision to use a library under this org.

All libraries within this org conform to these goals:

• SemVer and SemVer TS Compliant -- upgrade without surprises
• Native npm packages (or v2 addons) -- allowing the addons to contain any number of components without cost to those who don't use every component (tree shakeable)
• Fully glint compatible -- typed templates are the future, guiding folks to passing correct arguments and using the correct yields from a component
• gjs/gts first -- when building components this way, components tend to be smaller, lighter, and easier to work with. from the consumer side of things, this means easy imports without lots of paths to manage
• Derived Data focused -- whenever possible, components rely on derived data to manage state. No extra renders triggered by ember's equivelent(s) of useEffect.
• Builds on the latest platform features -- no one wants to maintain code, so when browsers ship something that make something easier, these libraries adopt it.

These projects meet the above tech goals

Bring your own styles for...

• Form
• Table

These projects have similar design goals in augmenting The Platform, but may not have the same goals. Still good projects, but different goals.

• headless-ui

Any library that provides UI abstractions without styling. These sorts of libraries cover many concerns that T H E P L A T F O R M has known were issues, but have not solved for us.

Capabilities can include:

• common behaviors
• common UI patterns (select, dropdown, tables, etc)
• correctly ensuring that a screen reader works appropriately for all possible text (even dynamic)
• and more!

The goal is to aggregate and build an SDK of libraries that we all wish the web provided for us. We bring our own styles and additional use-case-specific behaviors on top of those libraries.

flowchart LR  
  ember-primitives-->preem
  kolay
  reactiveweb-->ember-primitives
  test-support
  
  subgraph "@universal-ember"
    kDocs[kolay's Docs]
    epDocs[ember-primitive's Docs]
  end
  kolay-->kDocs
  kolay-->epDocs
  test-support-->kDocs
  ember-primitives-->epDocs
  test-support-->epDocs

  click tutorial "https://tutorial.glimdown.com" _blank
  click ember-primitives "https://ember-primitives.pages.dev" _blank
  click kolay "https://github.com/universal-ember/kolay/" _blank
  click reactiveweb "https://reactive.nullvoxpopuli.com/" _blank
  click test-support "https://github.com/universal-ember/test-support" _blank
  click preem "https://github.com/universal-ember/preem/" _blank

All of the projects in @universal-ember can be used outside of this organization.

flowchart LR  
  subgraph "General Purpose"
    ember-primitives
    kolay
    reactiveweb-->ember-primitives
    test-support
  end

  ember-primitives-->preem

  tutorial["<template> Tutorial"]
  kolay-->tutorial
  ember-primitives-->tutorial
  reactiveweb-->tutorial
  test-support-->tutorial
 

  click tutorial "https://tutorial.glimdown.com" _blank
  click ember-primitives "https://ember-primitives.pages.dev" _blank
  click kolay "https://github.com/universal-ember/kolay/" _blank
  click reactiveweb "https://reactive.nullvoxpopuli.com/" _blank
  click test-support "https://github.com/universal-ember/test-support" _blank
  click preem "https://github.com/universal-ember/preem/" _blank

This org has the same philosophy, maintenance strategy, and contribution model as Adopted Ember Addons and is not meant to be a competitor. The difference is that this org is focused on UI primitives that can help build out design systems. This org will/does likely consume addons from Adopted Ember Addons, as there is a lot of really good stuff over there. Additionally, as time goes on, libraries from Universal Ember may be transferred to Adopted Ember Addons.