I've had a few people ask, and no, this isn't an ad, I just really like Astro a lot and thought I'd share it with you. If ever I do a sponsored video, it'll be marked as one and I will also mention it during the video... but I also don't do sponsored content anymore. Most I'll do is maybe have an affiliate link if the service has one, and it's a product I actively use and believe is good.
Hey Kevin, just wanted to let you know that I seriously appreciate all the effort you've put into making these videos. Sending warm greetings from Denmark! 💗
@@codokit I never remove any comments from my videos, with maybe a rare exception of something that's offensive, which luckily doesn't happen often at all. If a comment doesn't show up, it's been filtered by YT automatically.
What I like about this video is Kevin has gone into more detail with examples (the only way I can learn) and would love to see building a multiple website using templates and more components.
I’d be interested in more videos re building with Astro. I’m particularly interested in how I could use data files like Jason or csv and how I would handle multiple image files for responsiveness and performance and using a cdn. Hooking it all up to a CMS would be cool too.
Holy crap I didn't realize that Astro did this! I started with React and all but don't really take advantage of a lot of it, so I usually just use it to make components and scoped styling. Turns out Astro is right up my alley:)
As someone who started working with React 3 months ago, it now feels way easier to understand, while watching the video I was like « Okay, this makes sense because in React… » Sometimes, looking at someone coding really helps getting the hang of a concept, plus you’re a wonderful teacher Kevin, thank you for your hard work !
Nice to see you jumping into a framework. I really appreciate you keeping it vanilla & simple in most videos, but a component-based environment with props is a must-have for web dev. Astro looks very lightweight, which is great!
Event though I know some Vue, Astro is still a better choice for some kinds of websites (like the one I mentioned in another comment); specially performance-wise.
I love Astro! It has transformed how I work on websites, nice to see you looking at it! One thing I want add though: At about 6:40 you talk about just using element selectors in your components and how Astro keeps the specificity low using :where. This has actually bit me in the past, because the order of CSS from different components is not really guaranteed. So you might have your global ul styles overwrite your local component styles, which can be really nasty to debug. That's why I stick to using classes within my components still.
I like 11ty but as simple as it is, it can take some learning to get set up. These days most people know React or Vue, what Astro does well is go a step beyond 11ty and allow you use patterns you are already used to in React or Vue. I really like it. It feels like less to learn, like I already know how to use it. Thanks for the quick overview.
Hi Kevin, Like yourself, lean towards writing vanilla HTML, CSS and JS. I'm generally dubious about frameworks and libraries. They take time and effort to learn, and then they add technical debt to a project - anyone coming to the project (even if it's yourself 6 months down the track) has to understand the framework and what it's doing to the code or they'll mess up what you've done. That said, you have sold me. Astro looks light enough and useful enough that it definitely merits further investigation. Thank you!
Before even watching the video, I want to point out that Astro is awesome! Been using it in productions for the last 2 months and I can't be more happy about it!
Thanks for the awesome tutorial. If you would do more tutorials about Astro, that would be just amazing. For example, it would be interesting how to integrate a headless CMS like Directus into Astro. PS: I love your channel :)
I love this! I wanted something with reusable components that was easy to update for my personal website. This solution is much more lightweight than React and is insanely easy to update! The ability to add markdown so effortlessly is pretty cool as well.
Wow another framework! Thank goodness, lets all switch over now, it will never become obsolete to be sure, change all your code right now - because it is soooo much easier - the game has finally been changed!
I come from the world of wordpress and advanced custom fields. A lot of process and structure felt very familiar and I absolutely love astro! If at any point a client want something light and static it's my go-to!
Astro is a fantastic tool, I fell in love with it right away 🙂. I would love a video about content collections, as I seem to struggle getting it to work.
Been hearing about it so much lately, but I was hesitant to use it because I'm still improving my vanilla js/css and html skill. But this looks nothing like other frameworks, and not much different from the vanilla. Passing parameters between components kinda reminds me of Ejs, I like it, I may try Astro for my next side project. Thank you for this video.
Hey Kevin, your video + the one from developedbyed are really complementary, thank you so much for your content and sharing your (awesome) knowledge !!!!!!!!!!!!!!
Perhaps I am being dim, but I really don't see what the advantage of using this would be. We've taken a very simple and straightforward design and added a bunch of extra complexity. I would think that creating the page using plain old CSS JavaScript and HTML would be faster and easier to understand than doing it this way. If you had a larger project with more complexity and dynamic data, well you would probably be using a tool like React and sourcing the data from a service API. So, it seems like it's too complex for small projects, and not robust enough for large projects. At least that's the way I see it. Other opinions are available 😊
A single pager like this might not be the best use case, but it had a few quick examples I could look at so I used it. It's an ssg out of the box (though it can do more), so any multiply-page site could easily use it. I had .md for those little things, but each one could be a full blog post based on a template layout. Just having templates for the nav, footer, and other repeated things so easily is a big win too. The amount of simple sites that I see that are using React, that have *no* need for it and just ship tons of JS to the client for no reason is nuts. I'm not saying this replaces React (you can even use react components in Astro), but it fills that middle ground.
@@KevinPowell "The amount of simple sites that I see ... " Kevin, I could not agree with you more! I've worked on plenty of small projects for local businesses where the most advanced functionality is a contact form that winds up sending an email to the owners inbox, and someone decided that they needed React, or Vue or . That sort of gets to my point about Astro. I agree that it's not the same level of overkill as React, but at least from the examples in your video, you make a component out of the list, which is cool, but now instead of one piece of HTML and one CSS file, we have locally scoped CSS and additional non HTML files that get transformed into HTML at load time. This probably has minimal impact on the client side, but for the developer, it just feels like adding extra complexity to the site, and extra thinking time. I find that I spend a lot more time reading code as opposed to writing it, and I like to keep things as simple and readable as possible. Now, I'd be lying if I said that I have never been caught out by the bug of "I updated the entire site except for that one file...", and I can definitely see the value in using templates, especially from the perspective of keeping redundancy and repetition to a minimum. But you can do that already with a bit of vanilla JavaScript. And yes, that JavaScript adds some complexity as well, but at least it doesn't also add an additional dependency on a third-party tool. I admit that my workflow isn't the same as others, and I can totally see how somebody could look at this tool and feel like it's a good solution for their needs. Especially if JavaScript isn't their strong point. Horses for courses. I just wanted to say that I wasn't having a go at you or the video. It's great to see new ideas and technology, even if I personally am not going to be using this. I really appreciate your work and the fact that you took the time to respond to me as well.
A framework that is being praised by Kevin Powell himself, is a framework worth using. I skipped astro because I was already learning sveltekit at that time, but looks like I have to make try it out for my weekend projects.
A lot of frameworks like Vue and Angular have "slots" which does this. I do like the simplicity with its notation though. The Globs and md support was also intersting
Astro is shipping a waaaay smaller bundle to the client though. You can solve any problem with just about any tool, it's always a question of right tool for the job.
Astro has slots as well, I just didn't see a good usecase to use them here. I guess I could have for the jobs, but I liked having them all in one place. And the .md stuff is great, but even better is using .mdx, cause then you can do the same type of thing, but with other components within those files instead of just basic markdown as well... I really looked at just a few of the very simple things here. It does *a lot* of what people are doing with things like React and Vue, but without having to ship a ton of JS, which is so nice. I see it as a great way to fill that middle ground for small and medium sized projects that don't really need all the bells and whistles of those libraries.
This was amazing - I would love to see more. - I have used React, Vue but I really dont think they compare to my bread-and-butter - which is Rails. - Astro reminds me of web-components. - For content that should not change after deploy - this seems like a perfect choice. How about a contact-us page video, with Email provider integration, or anything where you are requesting data from or posting data to an API.
Thank you for the video, Kevin! I would love to see more Astro videos from you. You explain things so well! I've started using Astro and love it, as well. One challenge I've found is: responsive images. Specifically, out-of-the-box responsive images. I'm always looking for a modern replacement to use for a Jekyll site, however, that replacement needs a responsive image setup that supports markdown use along with page-based use (.astro files, .mdx, etc). Anyway, do you have recommendations around creating a solid responsive image setup in Astro? I know Cloudinary is an option, but I'd prefer local asset image optimization and re-sizing.
Thank you for the awesome tutorial! What is the best way to make responsive layouts on Astro? media query on each components? It can be confusing when you have many small components to reuse them later... ?
I wish Svelte worked like astro by default. I am building a simple static website and I wish I could use svelte components and syntax to generate pure JS less HTML files if you dont use any reactive features
OMG ! Just the content i was hoping you'd do someday ❤ It's been quite some time i'm using Astro now, and i'm loving it. A pleasure to see it featured here so many people can discover and make things with this great tool
Obviously you have to do all sorts of terminal build stuff with this. Can that all run alongside my standard sass build too? I've not really delved in to frontend frameworks, but the annoyance of duplicating headers and footers in to multiple HTML pages makes we want to use it. I was just concerned I couldn't run astro builds at the same time as my sass build in terminal.
When using the markdown files - did you find it more advantageous to use them over say a JSON file where you can map through the JSON? Just wondering - first time I have seen md files being used like this and found it really interesting. Just installed Astro this week and want to play around with it and this tutorial has really helped - appreciate it
Kevin please make a video about PRACTICAL APPROACH of becoming better in front-end A.K.A. escaping tutorial hell. I know you have some kind of the videos but they are 99% about plain static HTML\CSS which is cool but who wants it? In other words please make ESCAPING TUTORIAL HELL video for REAL WORLD ( means with JS and frameworks\libs )
18:56 I thought it was solvable with slots, but I guess we're not jumping on LightDOM/ShadowDOM bandwagon here... That's the thing with UI frameworks - they have a different vision on impementing this: React lets you inject reactive HTML (inside... a paragraph?), use compound components or Slot component, Vue and Svelte compile the pseudo- tags.
@@KevinPowell Well, what I tried to point out is the confusion between a compiled slot in X/etc framework and in Custom Elements for injecting LightDOM tree. I wish there was a reference implementation to avoid replacing one with another. In any case, I love using those, so much rich content unlike trying to stash everything in prop and JSX your way through it. 😉
Could you give some examples or make an explainer video about when you'd need to use a static website vs a mon-static website? I still don't even truly know what a static website is or what the differences are or when you'd need o use one vs when not.
Can you pass variables to components? For example, let's say you want to share that list component across pages, but highlight a different item on each page? In other words, bring in the list component and color the "HTML" item blue (like a navigation where the current page is highlighted).
For me who use Vue in my profession, this video was really easy to understand. I am looking for something more close to plain html/js/css and was looking into Svelte but this seems to be a great alternative for sites that are not too logic heavy. What about dynamic content with ajax from a database? Possible or just static content?
Would you mind explaining why you used set:html on a tag? (timestamp 19:45) If set:html behaves like element.innerHTML, wouldn't generate a paragraph (and a heading, had you left the corresponding md in the content file) nested within another paragraph?
I've had a few people ask, and no, this isn't an ad, I just really like Astro a lot and thought I'd share it with you. If ever I do a sponsored video, it'll be marked as one and I will also mention it during the video... but I also don't do sponsored content anymore. Most I'll do is maybe have an affiliate link if the service has one, and it's a product I actively use and believe is good.
It looks like ad because other opinions are cleaned from comments.
Hey Kevin, just wanted to let you know that I seriously appreciate all the effort you've put into making these videos. Sending warm greetings from Denmark! 💗
@@codokit weird logic. Also, they're just buried under new comments, nothing's cleaned.
@@NECOdes Thanks for letting me know. Dont know about this behavior.
@@codokit I never remove any comments from my videos, with maybe a rare exception of something that's offensive, which luckily doesn't happen often at all. If a comment doesn't show up, it's been filtered by YT automatically.
What I like about this video is Kevin has gone into more detail with examples (the only way I can learn) and would love to see building a multiple website using templates and more components.
I’d be interested in more videos re building with Astro. I’m particularly interested in how I could use data files like Jason or csv and how I would handle multiple image files for responsiveness and performance and using a cdn. Hooking it all up to a CMS would be cool too.
Holy crap I didn't realize that Astro did this! I started with React and all but don't really take advantage of a lot of it, so I usually just use it to make components and scoped styling. Turns out Astro is right up my alley:)
As someone who started working with React 3 months ago, it now feels way easier to understand, while watching the video I was like « Okay, this makes sense because in React… »
Sometimes, looking at someone coding really helps getting the hang of a concept, plus you’re a wonderful teacher Kevin, thank you for your hard work !
Nice to see you jumping into a framework.
I really appreciate you keeping it vanilla & simple in most videos, but a component-based environment with props is a must-have for web dev. Astro looks very lightweight, which is great!
Super easy and simple for who's (like me) don't know react/vue.
Seems very easy to understand and use.
Event though I know some Vue, Astro is still a better choice for some kinds of websites (like the one I mentioned in another comment); specially performance-wise.
@@shayanzamani9907 can i make a webapp like a chatapp with astro ? is it recommended or go with sveltkit
I love Astro! It has transformed how I work on websites, nice to see you looking at it! One thing I want add though: At about 6:40 you talk about just using element selectors in your components and how Astro keeps the specificity low using :where. This has actually bit me in the past, because the order of CSS from different components is not really guaranteed. So you might have your global ul styles overwrite your local component styles, which can be really nasty to debug. That's why I stick to using classes within my components still.
MOARRRRRRR!
This was great and I'd love more videos using Astro starting from scratch with examples of different types of templates we could use.
Love to see you making a vid on Astro, thought it'd be in your ballpark, not too divorced from plain HTML
Yeah, feels like a really nice natural progression instead of a steep learning curve, which I really appreciate :D
Bro makes 22min feel like 5min, i totally enjoyed the video, same goes for ur other videos.
I used Astro once and instantly fell in love. Its simplicity is such a breath of fresh air compared to the other frameworks out there.
You explain complex javascript topics so well, looking forward to more framework tutorials in the future!
Best astro intro!
Man, how i love your content, definetly the best frontend youtuber we have! Thank You!
I like 11ty but as simple as it is, it can take some learning to get set up. These days most people know React or Vue, what Astro does well is go a step beyond 11ty and allow you use patterns you are already used to in React or Vue. I really like it. It feels like less to learn, like I already know how to use it. Thanks for the quick overview.
I've never saw Astro in depth before. It was nice to know it from your clean and calm explanation... Thankz
Very good content. Keep going!
I just started with Astro and as an experienced developer I like its concepts.
Hi Kevin, Like yourself, lean towards writing vanilla HTML, CSS and JS. I'm generally dubious about frameworks and libraries. They take time and effort to learn, and then they add technical debt to a project - anyone coming to the project (even if it's yourself 6 months down the track) has to understand the framework and what it's doing to the code or they'll mess up what you've done.
That said, you have sold me. Astro looks light enough and useful enough that it definitely merits further investigation. Thank you!
Before even watching the video, I want to point out that Astro is awesome! Been using it in productions for the last 2 months and I can't be more happy about it!
so glad you introduce this astro man, I am gonna use it to create my personal project's documentation.
🎉 YES! Let's dig into Astro!
Great intro tutorial. I'm excited to start working with Astro.
Kinda nice to see what the possibilities are using Astro. Thanks a lot for the great explanation! As always, very clear and easy to understand :D
Thanks for the awesome tutorial.
If you would do more tutorials about Astro, that would be just amazing.
For example, it would be interesting how to integrate a headless CMS like Directus into Astro.
PS: I love your channel :)
This is so cool. Im learning React a few weeks and seeing how everything related and linked with Js actually so useful!
I love this! I wanted something with reusable components that was easy to update for my personal website. This solution is much more lightweight than React and is insanely easy to update! The ability to add markdown so effortlessly is pretty cool as well.
Kevin! you made my design life just a little bit less frustrated. Thank you for simple explanation.
Wow another framework! Thank goodness, lets all switch over now, it will never become obsolete to be sure, change all your code right now - because it is soooo much easier - the game has finally been changed!
I come from the world of wordpress and advanced custom fields. A lot of process and structure felt very familiar and I absolutely love astro! If at any point a client want something light and static it's my go-to!
Astro is a fantastic tool, I fell in love with it right away 🙂. I would love a video about content collections, as I seem to struggle getting it to work.
I like the initiative eventhough the projects I am involved in requires much more complexity yet for simple things I will give it a try.
Why is astro not popular yet, it looks Amazing and easy to use
Great video! I've been meaning to look at Astro for a while and this was a really nice intro. ✨
By far the clearest and well paced tutorial of Astro. Subscribed!
Great as usual. Would be interested in a short on points you might have for using Eleventy vs. Astro.
I love both. I just think Astro is easier to get started with, since you don't also need to learn a new templating language.
Oh this is awesome. I had previously been using Express + EJS for this, but this looks like a good modern alternative.
Well, I'm sold!
Great video Kevin. Astro hopefully will shift the mindset of devs that over-engineer the most basic of projects.
This is the peak of tutorials.
Thank You, this is actually what I needed to know about astro and you actually explained Props in a way I could understand.
Astro is one of my favorite frameworks. Simple and easy to use. Love your videos👍👍
I've been using Astro since it became stable. It's amazing!
Kevin, please do more Astro content. Show how to use astro islands. please make video to build Blog website with CMS. thank u 🙏
I actually use Astro to learn and build scratch HTML + CSS sites, and even SASS/SCSS lol - it's just so convenient!
I'll definitely have fun with Astro
Been hearing about it so much lately, but I was hesitant to use it because I'm still improving my vanilla js/css and html skill. But this looks nothing like other frameworks, and not much different from the vanilla. Passing parameters between components kinda reminds me of Ejs, I like it, I may try Astro for my next side project. Thank you for this video.
This is a lot like Vue, but even easier. That's great!
Hey Kevin, your video + the one from developedbyed are really complementary, thank you so much for your content and sharing your (awesome) knowledge !!!!!!!!!!!!!!
We loved it we need more Astro content
Astro is pretty cool! Thanks!
The whole Astro structure looks like Vue to me a lot!
That's why it uses Vite.
I really struggled getting the content out of markdown files. Glad to see it's not as straight-forward as the frontmatter bits!
Definitely more videos on Astro!
Will you make a small project video on Astro with Svelte framework? It will be helpful for me and also for those who're interested in astro.
Perhaps I am being dim, but I really don't see what the advantage of using this would be. We've taken a very simple and straightforward design and added a bunch of extra complexity. I would think that creating the page using plain old CSS JavaScript and HTML would be faster and easier to understand than doing it this way.
If you had a larger project with more complexity and dynamic data, well you would probably be using a tool like React and sourcing the data from a service API.
So, it seems like it's too complex for small projects, and not robust enough for large projects.
At least that's the way I see it. Other opinions are available 😊
A single pager like this might not be the best use case, but it had a few quick examples I could look at so I used it. It's an ssg out of the box (though it can do more), so any multiply-page site could easily use it. I had .md for those little things, but each one could be a full blog post based on a template layout.
Just having templates for the nav, footer, and other repeated things so easily is a big win too.
The amount of simple sites that I see that are using React, that have *no* need for it and just ship tons of JS to the client for no reason is nuts.
I'm not saying this replaces React (you can even use react components in Astro), but it fills that middle ground.
@@KevinPowell "The amount of simple sites that I see ... "
Kevin, I could not agree with you more!
I've worked on plenty of small projects for local businesses where the most advanced functionality is a contact form that winds up sending an email to the owners inbox, and someone decided that they needed React, or Vue or .
That sort of gets to my point about Astro. I agree that it's not the same level of overkill as React, but at least from the examples in your video, you make a component out of the list, which is cool, but now instead of one piece of HTML and one CSS file, we have locally scoped CSS and additional non HTML files that get transformed into HTML at load time. This probably has minimal impact on the client side, but for the developer, it just feels like adding extra complexity to the site, and extra thinking time. I find that I spend a lot more time reading code as opposed to writing it, and I like to keep things as simple and readable as possible.
Now, I'd be lying if I said that I have never been caught out by the bug of "I updated the entire site except for that one file...", and I can definitely see the value in using templates, especially from the perspective of keeping redundancy and repetition to a minimum. But you can do that already with a bit of vanilla JavaScript.
And yes, that JavaScript adds some complexity as well, but at least it doesn't also add an additional dependency on a third-party tool.
I admit that my workflow isn't the same as others, and I can totally see how somebody could look at this tool and feel like it's a good solution for their needs. Especially if JavaScript isn't their strong point. Horses for courses.
I just wanted to say that I wasn't having a go at you or the video. It's great to see new ideas and technology, even if I personally am not going to be using this. I really appreciate your work and the fact that you took the time to respond to me as well.
So it's like React for dummies :) Now seriously, Astro looks great. I wanted ot check it out but didn't have the time. Great video ( as always).
react is for dummies, dunning-kruger dummies ;)
Great video! And yes, I'd like to see some more content on Astro.
A framework that is being praised by Kevin Powell himself, is a framework worth using. I skipped astro because I was already learning sveltekit at that time, but looks like I have to make try it out for my weekend projects.
Seems like you can do everything astro do with svelte, looks very similar just little different on the syntax(?)
A lot of frameworks like Vue and Angular have "slots" which does this. I do like the simplicity with its notation though. The Globs and md support was also intersting
Astro is shipping a waaaay smaller bundle to the client though. You can solve any problem with just about any tool, it's always a question of right tool for the job.
Astro has slots as well, I just didn't see a good usecase to use them here. I guess I could have for the jobs, but I liked having them all in one place. And the .md stuff is great, but even better is using .mdx, cause then you can do the same type of thing, but with other components within those files instead of just basic markdown as well... I really looked at just a few of the very simple things here. It does *a lot* of what people are doing with things like React and Vue, but without having to ship a ton of JS, which is so nice. I see it as a great way to fill that middle ground for small and medium sized projects that don't really need all the bells and whistles of those libraries.
This was amazing - I would love to see more. - I have used React, Vue but I really dont think they compare to my bread-and-butter - which is Rails. - Astro reminds me of web-components. - For content that should not change after deploy - this seems like a perfect choice. How about a contact-us page video, with Email provider integration, or anything where you are requesting data from or posting data to an API.
Thank you for the video, Kevin! I would love to see more Astro videos from you. You explain things so well!
I've started using Astro and love it, as well. One challenge I've found is: responsive images. Specifically, out-of-the-box responsive images. I'm always looking for a modern replacement to use for a Jekyll site, however, that replacement needs a responsive image setup that supports markdown use along with page-based use (.astro files, .mdx, etc).
Anyway, do you have recommendations around creating a solid responsive image setup in Astro? I know Cloudinary is an option, but I'd prefer local asset image optimization and re-sizing.
Thank you for the awesome tutorial! What is the best way to make responsive layouts on Astro? media query on each components? It can be confusing when you have many small components to reuse them later... ?
I wish Svelte worked like astro by default. I am building a simple static website and I wish I could use svelte components and syntax to generate pure JS less HTML files if you dont use any reactive features
Just saw developedbyed's video about Astro. I guess the RUclips algorithm really wants me to use Astro
Wow, what an amazing video, thank you sir!
The first part (with the components) looks a lot like how Pug (formerly known as Jade) works, just without the nicer syntax :P
OMG !
Just the content i was hoping you'd do someday ❤
It's been quite some time i'm using Astro now, and i'm loving it. A pleasure to see it featured here so many people can discover and make things with this great tool
I'm in love with Astro!
Thank you for this! Could you (or have you) done a video about front-end frameworks, comparing them and which one should you use as a beginner?
Ooooooh Luv this Astro is SO cool!
man i really do love Astro, thank you for making a tutorial about it,
It's a really nice framework. Can astro really get us out of framework hell?
i really did learn alot of new things everthing in this video is new to me
You're a good man.
Super awesome, I can't wait to try astro
Big fan, always an inspiration
Bruh it looks 🎉🎉🎉
So this is the first framework you created a video with.
Obviously you have to do all sorts of terminal build stuff with this. Can that all run alongside my standard sass build too? I've not really delved in to frontend frameworks, but the annoyance of duplicating headers and footers in to multiple HTML pages makes we want to use it. I was just concerned I couldn't run astro builds at the same time as my sass build in terminal.
love it sir. big fan of yours
Just blown my mind 🤯
When using the markdown files - did you find it more advantageous to use them over say a JSON file where you can map through the JSON? Just wondering - first time I have seen md files being used like this and found it really interesting. Just installed Astro this week and want to play around with it and this tutorial has really helped - appreciate it
Kevin please make a video about PRACTICAL APPROACH of becoming better in front-end A.K.A. escaping tutorial hell. I know you have some kind of the videos but they are 99% about plain static HTML\CSS which is cool but who wants it?
In other words please make ESCAPING TUTORIAL HELL video for REAL WORLD ( means with JS and frameworks\libs )
18:56 I thought it was solvable with slots, but I guess we're not jumping on LightDOM/ShadowDOM bandwagon here... That's the thing with UI frameworks - they have a different vision on impementing this: React lets you inject reactive HTML (inside... a paragraph?), use compound components or Slot component, Vue and Svelte compile the pseudo- tags.
You can use in astro as well :)
@@KevinPowell Well, what I tried to point out is the confusion between a compiled slot in X/etc framework and in Custom Elements for injecting LightDOM tree. I wish there was a reference implementation to avoid replacing one with another. In any case, I love using those, so much rich content unlike trying to stash everything in prop and JSX your way through it. 😉
So now do you prefer Astro to Eleventy? I remember that you used that for a project!
And what if I actually need JavaScript for a few components?
finite!!!
more Astro videos, please
Could you give some examples or make an explainer video about when you'd need to use a static website vs a mon-static website? I still don't even truly know what a static website is or what the differences are or when you'd need o use one vs when not.
a simple answer is, when JavaScript comes to the scene " like JS Variables " - is a signal that dynamic content has come up \o/
@@OsvaldoNetoTomaz-et5yt I appreciate you taking the time to reply mate. That makes sense. Thank you.
Can you pass variables to components? For example, let's say you want to share that list component across pages, but highlight a different item on each page? In other words, bring in the list component and color the "HTML" item blue (like a navigation where the current page is highlighted).
Yup yup!
Looks similar to php! Thanks
5:23 Skills & Experience 🙂
Can we get more Astro video please?
Cool stuff, thank you! What‘s the difference to something like Hugo in your opinion?
Very similar to JSX and React. Components, and Maps..ect. I'll stay with Js and React as it gets too complicated mixing Astro with React and Js.
wow thanks
For me who use Vue in my profession, this video was really easy to understand.
I am looking for something more close to plain html/js/css and was looking into Svelte but this seems to be a great alternative for sites that are not too logic heavy.
What about dynamic content with ajax from a database? Possible or just static content?
Hi Kevin, when are you going to publish your sass course again? I've been waiting it for very long.
Has this not been done by riotjs for yearsss. I feel like riot doesn’t get recognition it precedes svelte and svelte gets all the glory
Would you mind explaining why you used set:html on a tag? (timestamp 19:45)
If set:html behaves like element.innerHTML, wouldn't generate a paragraph (and a heading, had you left the corresponding md in the content file) nested within another paragraph?
Good point! I should have inspected the elment there to see what was going on, might have been a small mistake there 👀