[marccantwell]

Completely valid. I should have been more direct, but that wasn't the intent. Since you took the bait, I take issue with the seemingly flipant manner in which words are assigned new meanings, and existing concepts are relabeled. While the concept of archetypes is intellectually really fun to consider, it makes more difficult the ultimate project of speaking a common tongue. This is not an orthodox point of view, this is primarily economical. Far too much cognitive effort is required to learn new paradigms that turn out to be fresh takes on old ones, so best to identify them early and move on. But we should be critical as a community to self-regulate, as the marginal utility of each moment of learning is weighed against a million other potentialities.

[alexgrigoryan]

Happy to receive feedback, do you have suggestions on what we should call it?

[marccantwell]

You might do just fine substituting archetype with template. The readme for https://github.com/electrode-io/electrode-archetype-react-ap... reads: "This "app archetype" provides for common patterns across all app projects so that each app project can standardize on common development behavior and patterns. Its essentially pre-made patterns for build scripts." "A pre-made pattern" sounds a lot like a template. The majority of the documentation focuses on applied concepts, with familiar terms. The only reference to archetypes is found in the first paragraph of What is Electrode, and I think it distracts and confuses more than it helps. If it is a core concept, then it might be good to link to https://github.com/FormidableLabs/builder, but I don't yet see where or if builder is included as part of electrode.