![]() We'll cover why your leaving money on the table NOT using web components, how we've taken month long functional prototypes down to days or hours and why Web components aren't just a stop on along the road but unlock component architecture for all projects without bloated frameworks or gigantic rewrites to existing projects. This will be making the case for web components as an approach and the future of all development, but if you've never used or heard of them feel welcome! This will be a mix of code for examples in production and demo purposes but is much more focused on policy, methodology, workflows and experiences from our team (4 people) developing 400+ web components the last 3 years. How other organizations are leveraging our web components to enhance their web properties at scale and progressively How to access and leverage our 400+ decoupled web components that we use every day as well as 100s from the wider community How you can get started with Web components and use them in any Drupal or non Drupal project, today. How our progressive headless has turned into us building our OWN headless CMS out of identical components that is entirely JSON / flat file driven How we built HAX, a completely headless authoring experience to side-step Gutenberg ![]() How we built a progressively headless Drupal based system How this helped us to not lose momentum on any project and now we work at unparalleled levels of efficiency via web component re-use How we stopped all headless development, got behind Web components and slowly pushed them into production ![]() How we started going the wrong way, picking AngularJS for a total headless rewrite and never will again. How we moved off an existing design framework in phases Specifically questions we'll answer and unveil in this talk: In this talk, I'll walk you through the project life cycle that involved the ELMS:LN team shifting from traditional Drupal JS to a progressively decoupled approach to the point that now we're able to simultaneously work on HAXTheWeb and Drupal projects while still maintaining a small team. But what's been lost is what is a legitimate way of getting there. Headless is the future, or should I say, a big consideration in the future. Then, we spoke to others at Decoupled Dev Days years ago and found something interesting: there's another way out. So we came to a cross-roads (or so we thought): We burn down our existing approaches and do them headless OR we ignore all these talks. ![]() is anyone really doing this? Like is it feasible? Does that sound like your team? Mine neither. Where we attend great events like this one and talk about Headless for almost four years yet have very few people actually doing it unless they have a large team or a lot of free time, allowing them to present at events about how great it is. We have mouths to feed and projects to tend to so maybe we can look at this when we get out from under our project load but keep dreaming." Project manager: "We have a team of 8, 3 projects in the pipeline and 10 to maintain currently, welcome to reality you two. Reasonable Developer: "Yeah and headless is totally the way to go, I can see it! I'm not sold totally on how but it DOES seem like what we should explore in the future" Super Excited Developer: "OMG JSON:API in core!? And React and JS are awesome and I CAN HAZ SHINEY THINGS in Drupal!!"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |