Avoiding duplicated documentation

[xabbuh]

Especially for the Form component, we have many things documented twice (in the book and in the components part) as @weaverryan stated in #4085:

It's difficult because the form component has a significant amount of duplication, in part because we thought that we might try to make it work for both the component and framework all in one page (but I don't think that makes sense anymore). Ideally, I'd like to find a way to duplicate less.

This may not only be true for the Form component, but may also occur for other components and they should be checked accordingly. Therefore, this issue is to discuss whether or not we can overcome these duplicated descriptions and if we agree on avoiding duplication how exactly this can be achieved.

[wouterj]

I believe we should move slowly to the concept that we tested for the past year with the Translation component: Documenting component usage in the component docs and using the book article as a quick intro to the component docs and to document framework specific things.

[javiereguiluz]

This definitely seems the way to go. I recommend to close this issue because it's too generic and not actionable. Then, when the 500+100 Challenge period finishes, we can open new issues to make the transition for each component.

[wouterj]

I think this a nice place to talk about this feature. The open issue list is a list of things we have to think about or have to fix. Imo, if an issue is closed it's either fixed or will never be fixed.

We don't have a clear plan on how to fix this, this is a general problem with the docs. I don't like my option, since it means you'll move a round a lot between components and book and people might get confused by other things in the components. Maybe we have to change the complete structure of the docs...

[javiereguiluz]

I think we can close this issue because it's too generic. Besides, we are already committed to reduce duplication in lots of places.