Primer ViewComponents v1.0

[manuelpuyol]

As our README states:

This library is under active pre-1.0 development. Breaking changes are likely in patch releases.

We've discussed a few times about taking PVC to v1.0, but we never decided what the library needs to take that step.

Where we are now

• We currently have around 50 components, most of them in Beta status and a single stable component.
• We are starting to define what each status means.
• We have basic documentation for all components.
• We are shipping linters to improve component adoption.
• We are improving the PrimerCSS coverage in the project.
• We updated our components not to use deprecated APIs from view_component.
• We started shipping behavioral components.

What is missing

Even with all our achievements in the past months, there is still work to do!

Stable components

Updating PVC to v1 means that we expect hubbers to use our components in their day-to-day work, and we can't do it if we don't have enough stable components.
Right now, only Box is in that state.

Classify

Classify is extremely hard to understand. It also isn't clear what arguments it supports and what CSS classes they generate.
@jonrohan wrote more about it here.

Improvements to linters

We started shipping linters that only count the number of offenses without showing the user how to correct them.
If we want to make the transition as easy as possible, we need to guide them on how to do it, and automating the migration with linters could be a solution.

Status definitions

Even though we made some progress, it still isn't clear what each status means and what is needed to navigate through them.

Next steps

I'd love to get opinions from you about what specific goals we might set for the v1 release!

cc @joelhawksley @khiga8 @koddsson @jonrohan