6 ай бұрын
8 ай бұрын
8 ай бұрын
Жыл бұрын
Жыл бұрын
Жыл бұрын
Пікірлер
@KevinPowell 20 сағат бұрын
Thanks for having me on, was a lot of fun!
@JanErikTöpper 2 күн бұрын
Lovely people and a great show 🙂↕️ Thank you for the stream ☺️
@VideoNOLA 15 күн бұрын
I'm really curious why the Anchor Position demo I created in CodePen works there (viewing with Chrome latest w/o Experimental Web enabled), but does *not* work on my test website (again viewing with Chrome latest, even w/ Experimental Web enabled!). Does CodePen have some secret sauce when it comes to presentation of experimental CSS??
@VideoNOLA 15 күн бұрын
Also: How does this excellent demo video only have 600-ish views in 6 months??
@wingingitoddbird Күн бұрын
Good question! As far as I know, CodePen doesn't do anything special that would impact this. It's hard to say without a link, but I've had this happen when the wrapping element in your CodePen example is different somehow from what you have on your site, which breaks the anchor discovery algorithm somehow.
@philip9677 Ай бұрын
This is good, gona try grid to stack instead of absolute
@NoScriptShow 2 ай бұрын
Yes please for a part 3 . These are pure gold!
@zettadam 3 ай бұрын
If I understand it correctly, to use a custom element (say web component) that I created, doesn't the browser have to download extra JS code and register it using DOM API (that is JS, again)? How is this better when it comes to loading performance than using a React component?
@JamesStuckeyWeber 3 ай бұрын
You're correct that you have to download and register the custom element, but when you use a React component, you also have to download and run React. So overall, the download size should be much smaller, and you should need to run much less code overall, when using a custom element. I haven't seen a benchmark comparing the two, but I'd love to see one!
@ZachLeatherman 3 ай бұрын
Additionally, it should be noted that shared library code for Web Components is an order of magnitude smaller than React + React DOM, if you don’t want to go full dependency-less like I aim for
@tobiasfedder1390 3 ай бұрын
Miriam and Zach are going to build a W3C Web Annotation Web Component; that's what I heard - I'm definitely not misconstruing what has been said here. All we need to do is find unlimited resources. Great conversation. I like the idea of a web component taxonomy as well as differentiating between standalone custom elements - meant to be available to every website - and bundles of custom elements with shared dependencies coming from design systems - meant to be used together.
@Islandstone89 4 ай бұрын
The stream starts on 28:00 👍
@DavidWaumsley 4 ай бұрын
Bravo. This was great. Thank you. After ditching a page builder framework I started with grid before diving deeper into flex. Even though I have used everything covered here I got much out of seeing examples and your thoughts. Having started with grid I made my pages a grid and used flex within that as needed. After a better understanding of flex I started to think every thing should be normal flow and grid and flex should takes us out of that format as needed. I'm still not sure what my strategy should be. I think Miriam said she may start with grid when she knows the layout she is creating. I am moving toward designing in the browser more where I'm not sure what (or even if anything) needs to breakout into columns. Often the content will change as the document is being styled. Thanks again. You can not do too much on this subject as far as I am concerned.
@MiriamCodes 4 ай бұрын
Hi! Designing in the browser is excellent. I think I left out some nuance in what I meant there. It's not about knowing the layout before I start coding - but about determining where things go from the outside. If I want to specify how things get laid out, I generally reach for grid. I'm imposing a layout from the outside, even if it's only columns or only rows - and even if I'm experimenting as part of a design process. That's what I mean by 'knowing' the layout I'm creating.
@DavidWaumsley 4 ай бұрын
@@MiriamCodes Thanks so much. I am sure you have much going on. That was helpful. I think one of the issues with grid is knowing when to use it. Although there is no shortage of examples of it being used to layout a header, main, footer and (apparently popular again) sidebar there is not so much arguing (probably out of respect) the case to start with grid. As someone finding their feet with CSS again I started convinced everything should start with grid. I discover every-layout.dev and drifted away from that. This has probably switched me back. I'm planning some content for others like me wanting to get back to CSS. My wintering on is me trying to find my own position so I don't overload an audience with options and uncertainty.
@SchalkNeethling 4 ай бұрын
Love, love love, this. Thank you so much. Also, I might have just fallen in love with grid-template :) Also, yes to a part 2 ✌
@wingingitoddbird 4 ай бұрын
Glad you enjoyed and it helps to know you would like to see a part two. We could talk about grid for days.
@AdamArgyleInk 6 ай бұрын
love it y'all, great walk through!
@wingingitoddbird 6 ай бұрын
Thanks Adam, glad you enjoyed it. And we love the work you do as well.
@SchalkNeethling 6 ай бұрын
Oooooh, this is super exciting!
@AnaMarquez-y5u 7 ай бұрын
Awesome ♥ Thanks !
@FM_2002 Жыл бұрын
I’ve been doing some experiments with Ruby on Rails + AlpineJS + HTMX. Delightful experience so far! 🎉
@dmenisdevdevelopment7158 Жыл бұрын
HTMX and Django templates can be a good match. Wouldn't it be awesome if JQuery were to be replaced with HTMX in Django admin 😬
@BradPitcher Жыл бұрын
Loved it! As a backend-first developer (who randomly peppers the CSS with !important to resolve specificity conflicts) this is a major improvement that I am excited to use!
@wingingitoddbird Жыл бұрын
We are also excited. We've used it on a few production sites and it feels a bit magical when you first work with it. Hope you find it helpful in your next project.
@LaurenLozy Жыл бұрын
Big slay 😋