![]() 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" It’s here, and you can start using it with test-covered and OOP modules like RESTful and Zariz.Super Excited Developer: "OMG JSON:API in core!? And React and JS are awesome and I CAN HAZ SHINEY THINGS in Drupal!!" Everything is implemented in a slick Angular based UI - one that users enjoy using. In Gizra we already have projects where we don’t use any node form to create or edit content. captionDetailed errors are part of the JSON response Inline errors, provide a better UX And of course the endpoint itself is handled by RESTful which does a lot of the heavy lifting by taking care of authentication, permissions, CSRF tokens, exposing the RESTful resource etc.ĭevelopers would appreciate the very little code needed to declare the validation and the RESTful resource.Īs a benefit, since RESTful spits out structured error messages, displaying error messages inline is really simple. The tricky part is the server side validation, which is now handled by Entity Validator module. The example module shows how all the HTML, CSS, and JS are bundled together in an Angular App, and Drupal simply ng-includes it. Angular forms are great, but Angular forms are hard too - you need to write your own custom endpoints and server side validation.īut now that RESTful integrates with Entity Validator, I would change the equation and simply say something rarely heard in the Drupal community: Forms are Fun! This form is not Form API, it's angular!.Form API is great, but Form API is hard when you try to do fancier stuff - like wizards and other things that clients often want.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |