Not everything is a component (#7074)

Author: mperrotti

contributor-docs/principles.md

@@ -34,6 +34,5 @@ There's often more than one way to do things, and there aren't always best-pract
 - A little verbosity is better than clever code. Avoid implementations that reduce the ability for people to contribute.
 - Automate and abstract when repetition is a hindrance.
 - Seek feedback on implementations as often as possible.
-- Everything is a component.
 - Provide flexibility, but within the boundaries of the system.
 - Assume that people will break the rules, and provide safe ways for them to do so.