- From: GL <notifications@github.com>
- Date: Mon, 25 Jun 2018 05:13:50 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 25 June 2018 12:14:12 UTC
This is a great thread. As a developer who is just considering using Web Components, I just wanted to add a point of view that I think has not been made yet. I'm not sure; I had to skip some parts of this thread. Most of the discussion centers around the reuse of components by JavaScript developers. Is there any discussion yet on how Web Components would affect onboarding of potential HTML/Markup authors, specifically the effects in documentation and ease of adoption? It seems to me `<table is="sortable" />` would be easier to adopt, and better leverage existing docs resources for those new to web development or those that would only work with Markup syntax, such as content authors. If I were to build a component for this audience, I could more bridge understanding and would save a lot of work referring to existing docs when onboarding potential HTML/Markup authors. I'm not against `extends`, inheritance, nor mixins, etc. I'm happy to be educated and hear all contrary points. Please don't answer using metaphors. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/509#issuecomment-399930155
Received on Monday, 25 June 2018 12:14:12 UTC