GitHub Open Source Friday, 16 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Tips for documenting your framework with Astro - Open Source Friday

Description

In this video, Dan Jutan shares with us how to develop better documentation for new open source projects. We also get to learn about different strategies that Astro takes for its documentation.

0:00 - Introductions
2:10 - What is Astro?
5:50 - What makes good documentation?
13:40 - A look at the Astro documentation
28:59 - Why he joined the Astro team
36:27 - Fun Chit Chat

Join @blackgirlbytes live for Open Source Fridays at https://www.meetup.com/github/.

Thanks!

Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github

About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
Chapters

A

Hey everyone thanks for joining in I, see there's a few listeners so far. If you don't know what this is. This is open source Friday, where I chat with a maintainer or a core contributor about an open source project. So we can learn more about different open source projects together.

A

um If you're listening in in the comments feel free to say where you're watching in from um and interact with us as well and also I'm joined by Dan today um from Astro and she's here to talk with us about Astro documentation which I'm super excited about, um Hey Kevin uh feel free to introduce yourself Dan um and tell us who you are and what you do.

B

Hey yeah I'm Dan um I work at uh the Astro technology company, which is the company behind the Astro, open source project um and I sort of split my time between docs on one hand and like product on the other, which means a lot of like connecting dots between the documentation team and the engineers and also sort of tracking feedback and trying to make sure we're we're acting on those. um But yeah. That's a little bit about um uh who I am I'm.

B

Also a core team member on solid.js, which is another open source project and I. Don't know. I uh I like to sing.

A

B

Right right, I'm, like I'm, lokia, devrel, I, I, love, I, love, going on streams and talking to people and um I think the idea is like if you're extroverted enough, you might just be labeled to devrel. So.

A

It might just happen if you, if you talk enough on Twitter like or.

B

A

Up on Twitter introverts.

B

Could be devrels too, don't get me wrong.

A

Yeah I think I think I'm integrated so.

B

A

But how about how about you tell us a little bit more about what Astro is for anybody who doesn't know about it?.

B

Yeah Astro um has recently announced its 1.0 release um about a month ago and it's been sort of circling around the twitterverse, so you might have heard of it, but it is a Content focused site Builder. So it helps you really easily build blogs or marketing sites or any sort of like highly um sort of stuff.

A

B

Distracted by chess I was like documentation, no um any any sort of site that has a content-based static aspect to it. So um the sort of magic feature of Astro is that you do most of the work on the server to arrange all the content and present it. And if you do need interactivity on the browser you can choose any front-end framework. You want react spell view solid for those interactive parts. So the idea is that this is super efficient, because most of your site is just static HTML.

B

um It will send no JavaScript by default, so your site will show up super quickly and then, as you need more interactivity, you can opt into that and send just that to the browser, so that might have been long-winded, but basically it's a cool way to make websites. That's what it is not.

A

Long-Winded at all, it was a perfect description. I've I've used it a little bit. I really want to get a chance to use it more, but I will attest to the fact that it was way faster to develop with Astro like I did a project um comparing like next JS. What astral and some other like Frameworks, that I'm used to and I was like yo I'm, getting real fast with Astro. It was just like plug and play with different components. So I did love that factor.

B

Yeah we used to have a tagline build fast sites faster, which is a little cheesy, but I kind of like it, because yeah the whole idea is, it's not just you know a super performant tool. It's also easy to get started with, and that's what really attracted me to it is that, like I, want to work on tools that are accessible that are easy to learn and easy to teach and easy to wrap your head around and uh Astra sort of felt. That way to me.

A

Yes, yeah and I I want to highlight Kevin's comment. He said want to be cool use, Astro, I, agree.

B

Is one of our docs maintainers so shout out to him for for for coming along for the ride? He um um he sort of is part of the open source community and the way Astro works is that community members who contribute a lot can get recognized as maintainers, and then they have GitHub access and special special roles. So Kevin is one of those maintainers who focuses a lot on Docs.

A

B

A

Didn't know what area his Focus was in, so this is awesome and he said I can break dogs now yeah.

B

He has a GitHub merge button foreign.

A

So I'm curious: why don't? Oh actually I forgot about this question? I really wanted to ask you this about like what makes good documentation in your opinion, I always see you like talking with um Anthony. Well, I've seen you once maybe not always, but I've seen you talking about Anthony once about like um semantics and different things. So it seems like one of your passions and I'm curious like what is your thoughts on like what makes good documentation.

B

Yeah I talk a lot about audience, so every piece of documentation is going to be read by someone um and depending on who you're aiming to reach with a certain piece of documentation.

B

Your aims will change, but it's not just the background of the person who's reading, so that that's one idea is that um if you're writing documentation that you know is meant to be picked up by beginners who are starting to use your project, you want to use as basic terminology as you can.

B

You don't want to use terms that assume a certain level of knowledge, um but on the other hand, if you're adding a piece of Doc docs that are going to be read by like a really experienced user, like it's more of a a reference guide or or a really technical detail, then you might kind of sound patronizing if you use the most basic terminology.

B

So having that um having that um match between the the authorship and the reader is, uh is super important, so um yeah I I think the the first thing to do is to improve your docs is figure out who you're writing for, um and you can have different parts of your doc site geared towards a different person. So oftentimes you have a beginner tutorial um and you want to be writing that a lot differently than a reference guide.

B

uh Another thing is that not just about the matching to the background of the person who's reading, but the goals of the person who is reading at that moment. um So there's this idea of content types, so I mentioned like tutorial and reference guides. Those are each gearing towards a different goal. A person has so with the tutorial. The idea is I want to learn something from the ground up, walk me through it.

B

You don't really have to explain every single thing in tutorial, because the idea is to get up and running really quickly and learn from nothing, um whereas something like an FAQ or a troubleshooting guide there. Your aim is hey, I'm um I ran into something I ran into trouble and that's what I come to dots with I have this this problem and I need to solve it?

B

um Then you might have like a concept guide or an explanation or a discussion, and there the person is coming to docs with the goal of I've heard of this thing, I kind of get it but I don't get why it's here, I, don't really understand deeply.

B

So we have like, on the Astro, docks a MPA versus Spa page and what's the idea of that page, if you've heard of one one or both of these terms- and you have you sort of know what it means, but you don't really, you can click on that and get a full background of MPA versus SBA, so yeah. If there's two like like uh lessons that I would suggest for getting started.

B

Writing docs is understand that you're writing for different people, probably and gear different docs for those people and also you're writing for different purposes or different expectations, depending on what the user is doing at the time. So, there's my uh you know my docs. My docs rant.

A

I really really like that, um because I think that's kind of the way that I um approach, my content and I got that from Kurt Campbell. But maybe you all you both have like similar approaches or you learn from similar resources, but kind of talk to me about like making sure I understand my audience and who it is and not being patronizing if it's like a more high level audience or not using super technical terms and then um on you use the word like reference and stuff like that.

A

I think he had talked to me about like the difference between a guy or a tutorial or a reference or explanation and stuff like that, um so I or exploratory I think yeah.

B

A

That that kind of really aligns- and it's interesting to see that you use that same concept for good documentation, yeah.

B

We might and I can pull this up. We might even use the exact same framework here. um So there's a really popular um framework or outline called the.

A

B

um So this is something I first learned about I, don't know. Maybe a year ago and I never moved past it like it's, always sort of helped me um you don't have to so let me just run through it. There's these four content types and the- and this gets back into that different purpose of the guide or expectation that someone's looking for so for for the tutorials.

B

um It's learning oriented and you see on the axes it's under serve our study, I mean you're, trying to learn something um and it's it's very practical, meaning sort of what I was explaining before, like you, don't literally have to explain all the concepts as you go through the tutorial, because the idea of the tutorial is it's practical. You want to get something out of it, but the overall. The overall goal is to learn the framework, um and then you know below that.

B

We have these explanations, which are still about learning the overall framework, but it's no longer so practical anymore. We want we want to have a discussion. We want to really dive deep into a concept and then as we as we loop around the circle on the bottom right, we're still in that explanatory area that that knowledge base, rather than than you know, action area.

B

um But now we are more focused on the you know: information oriented, it's very specific, very detailed and specific to all of the different parts of the Frameworks, whereas on explanation side it might be the overall Concepts. It's like every single API piece um and it serves our work. The access has changed. It's because usually you'll go to a reference. When you see a specific function or something the framework lets, you do, and you want to learn more about it um and then the last one is the how-to guides where it's task oriented.

B

So you sort of know you want to accomplish something, but you don't know how and we're back into the Practical area, um but the goal is no longer to learn the overall framework, it's to learn how to I, don't know, use Astro to connect with a CMS publish Astro to GitHub. You know that kind of thing.

A

Yes, yeah, this looks exactly this is not the website. He showed me, but this is the exact like picture that he gave me. So it is probably like the same. Like methodology, I love this and I've been able to like I've, been able to not just use it for like if I'm writing, a blog post or documentation I've been able to use it for like making videos or doing a talk, and even even what my talks realizing.

A

Is this going to be like a workshop style talk, or is it just like a talk where I'm like showing something? You know what I mean so.

B

A

Think people should apply this yeah.

B

I, like that, a lot a lot of conference talks are in the bottom left, where they're very like explaining A New Concept, but some of them are more on the top right, like I figured out how to do a specific thing, and let me walk you through all those steps so yeah. This is great for for talks and workshops.

A

Yes, love it love it all right, let's make the pivot. If you're, if you're.

B

A

Into looking, especially since your browser's.

B

A

Looking at the Astro documentation and learning more about it,.

B

Yeah, so this is um this: is the the Astro docs themselves. This is um a local branch. So if you, uh if you are very familiar with the astrodoc, you might see something in the sidebar that is not on the live site, but I'll leave that as an Easter egg but yeah. These are our documentation you can get to this by going to docs.aster.bill, they'll use the live.

A

B

Now um and um so far, it's really only split up into two. We have the learn section and the reference section.

B

um We are planning a big restructure and lots of stuff coming up for the docs, um but so far it's structured as like. Hey we have this. How do you get started with Astro really quickly um and then the rest is really focused on each Astro feature that you want to learn, and it's very well um and I.

B

I can't really take credit for most of this work because I'm new, um so I, you know I'm giving uh I'm giving credit to uh to to Sarah who's the doc's lead and and the huge number of contributors to the docs which you can see in this ginormous. Oh, it's a lot yeah, but they they put a lot of thought into the order of this like. If you go through the basics um on their own, you can sort of read each introduction um and and get a little bit further in the right order into Astro.

B

um We also have some um some special um pages so like for the Astro Integrations um Chris and the team built this really cool like button layout um and what what this does right now is each integration lives in a different GitHub repository, so it actually pulls the documentation from the readme using uh a GitHub, a GitHub nightly action. So if I click on like the SSR adapters, like the node one, this is what you use to publish Astro to a node deployment.

B

This content is actually in the node integration, readme, and so our doc site currently pulls from that um yeah. So we have these core concept Pages too, which I really like these explain some of these overarching you know reasons to use Astro and and they're, basically deep Dives. So you know if you're in the the web framework space you've probably seen these terms a lot. um This is probably my my favorite place to to to to go deep into what an MPA is, for example,.

A

I, like I, do like how there's that separation, um especially even between the learn and the reference, because sometimes documentation can seem a little bit junky and you're like I. Don't know where to look but I like how you all have it all categorized um I would often put in you on the spot here so feel free to be like you're, not sure, but I did scroll on Twitter and I've. Seen people talking about Astro, Islands, yeah I, don't know what it is. If.

B

You do if you're not ready.

A

To explain sorry I didn't prepare.

B

You for this I'm totally ready to explain. Actually we were just talking about how this picture could use some some realism, rather than being a bunch of squares, um but the idea of the island is that an island is a part of your page, that's interactive! So um if we look at this docs page itself, um an interactive part could be you know, maybe this um this sidebar. Actually, that's not really true, because all of this was made using HTML and CSS like.

A

B

Javascript needed, but the idea is that, if you're looking at um a mostly static site like in this example, the sidebar is HTML. The the body of the content is just text and images, but you need an image. Carousel JavaScript.

B

um Islands ship, the JavaScript needed for just that image, Carousel yeah um and everything else is just shipped at the very beginning. Without JavaScript and you can do you can use Astra Islands to do some really cool stuff like um Astro lets. You configure this image Carousel so that the JavaScript needed to make the image Carousel Works only get sent when you scroll down to it. So if it's not visible, there will be no JavaScript for it and then, when you get there, it'll show up.

B

So the image Carousel might be built with svelte, yeah and svelt will not be loaded at all. If you never see the image Carousel and that's what separates Astro from something like svelte kit or nexjs, those ones send a framework like reactors felt from the beginning for Astro. You write all of your your boring static components using a special syntax called Astro, syntax astrophiles, and you only have to choose a JavaScript framework for the islands and.

A

I'm, assuming this helps with like performance because, like you, just have to load up that profile or the the static content and wrong when, when it's needed it loads up the JavaScript and um that way it's not loading everything all together and and killing the performance exactly.

B

Okay, cool actually, beside aside from performance, I've, seen a lot of people really like the Astro syntax. So like an astro component, looks like this. You have this little front matter here where you can put some setup work and then you just have HTML, and you can you know, do a similar thing, as in other Frameworks, where, like you use a variable, but another benefit to this besides performance.

B

Is that if you're, someone who doesn't really like using react or so like any of these front-end Frameworks, a lot of people feel this sense of like fatigue that there's so many Frameworks and they're so complicated the Astro syntax um lets you use a more basic, um a more just, JavaScript and HTML way to constructive components.

A

Yeah I definitely liked that it didn't seem like it was a lot for me to learn or switch over to your context, which I was like okay. This is like familiar to me, even though I'm never really written Astro before that. I'm like this is pretty familiar like um cool anything else. You want to demo, because I think this was really good. If not yeah,.

B

I appreciate I mean this. This is basically it someone asked if we, if you can use angular components, you actually can it's not an official integration but Brandon Roberts who's, a big.

A

B

Yeah yeah I, wanna, I, wanna, I I owe him a stream. I said hey. If you can finish this angular assay integration, I will stream myself learning um angular and I never did it, so uh he is um I believe on the app right team and he's also a big angular user, and he just figured it out like how to get how to get it all working in Astro.

A

That's awesome shout out to Brandon yeah I know he does a lot with like ngrx and stuff like that, so um wow, yeah and I'm sure he understands you have a full-time job. Now, like the the streams, are hard to always get get.

B

Yeah I mean I I, didn't fully understand, I'm like so wiped after the end at the end of the day, um but I I love going on streams like this. This is the first stream I've done in like three or four weeks so um yeah, it's fun. Well,.

A

I'm honored that you came on um so actually I have a a few follow-up questions. Now that we got to see the Astro documentation and um uh my first follow-up question is like how can people contribute? I will say that I think the contribution process is not too hard because I did it before but yeah.

A

Let's show people a little bit Yeah.

B

So like, if you wanted to contribute to the exact page that that you did um you, you know you go to the page that you want like one one way in what I'm saying is you're reading the docs and you realize, there's an improvement. You want to make or a type you want to fix. You can hit edit this page and it will take you to where you need to go.

B

um So that's that's one way to do it, and here you can go and hit the edit button and and be full in on um on GitHub um or what you can do is head over to our docs Repository.

B

So this is with Astro, slash docs on GitHub, and then one thing you can do if you want to explore more of the infrastructure side like how all the components work, um you know you want to make some nav bar improvements. You can clone this locally um or, if you want to, you, know, check out um some content um highly recommend. Looking at our issues, um you know we we actually just this morning, made a bunch of more like help, wanted and good for first issue tags.

B

So um sometimes we get a lot of what we call unsolicited PRS, where someone's just like I have an idea and to write something. Let me submit that as a PR. Some of those are good. A lot of those are sort of out of left field.

B

um So, if you want the highest chance of, like you know, being helpful and getting your contribution merged definitely check out the existing issues, um you can, you know, sort by um help wanted and it's like. Oh look, there's all these little gotchas I bet I can help um document.

B

um I, don't know this first one- and this is me this is me being like just click this link to this discussion. We need to document something, um but the idea is you can read the thread you can decide to um uh to contribute and then you can go and and Fork it and make a PR.

B

So yeah check out the issues and we really really love. um You know open source contributors, everyone who's working on the docs team, now started outside the project as an open source contributor and just and came in and eventually like um joined the team. So um this is a very homegrown, like you know, feel we really want as many contributors as we can especially translators.

B

um So we have six or seven language efforts. um So if you go to the top, you can see we have all these different languages and there's two ways to contribute.

B

um You can make a PR for a page that hasn't been translated yet or you can review and open PR. So there's a document I believe it is here translating.md- and this explains everything you need to know about working on translations for the Astro docs um and one of the things you'll learn here is that joining us on Discord is the best way to coordinate work, um but there's this huge, huge guide for for helping out and um and contributing a language.

B

um And if you look at our PRS you'll see um tags like this. One is um Chinese, um I, believe traditional Chinese and you can. If you see one of these and you want to check someone's work like let's say you speak Chinese, which I wish I did um you can go and read their work, leave a comment. So that's just something I wanted to emphasize. Is that reviews are also super valuable? You don't you don't just have to be the one to write. You can also review a PR.

A

Yes, I love this stream so far, we're talking like all about like non-code contributions, it could be in the form of a review, could be in the form of documentation or translation like this is good um I love that y'all have that and I know. We have a couple of people from like Guatemala and Argentina tuned in so if you did want to um to to contribute and and help improve like the Spanish translations and stuff, like that, it would be a big help, I'm sure and.

B

Kevin has really been spearheading the Spanish effort himself and he's in the chat. So you know it's very. We got a thumbs up so um yeah very, very helpful that uh that um Kevin's here yeah.

A

And you, you gave some good advice too about, like don't do 's less of a chance. I think my PR was broke, so don't listen.

B

A

But like uh that's like across the board from also you find the open issue or maybe if you create an issue and see yeah.

B

A

B

Can always make your own issue and then create a PR after the issue got some discussion yeah and we have a super active Discord community. So that's um astro.build, slash chat.

B

um If you go to this link, maybe I shouldn't hit it because it'll open up some private, DMS or whatever. But um what I love about this Discord? Is, you know a lot of times you're, not so sure about? What's going on? It can be kind of daunting to go and open up a PR for a project. But if you come, hang out um uh hang out on Discord, you can, you know, learn the ropes, learn some some some some names and and uh and start joining the community.

B

Oh my God, we love your PR I've broke the reviews.

A

Know it because of all the mistakes everyone's like change, this change that, but thank you and I did put um the the link to joining the Discord Astro dot, build, slash, chat and then also again for joining or looking at their documentation on GitHub or that repo. It's github.com yeah I.

B

A

Your discord's, pretty good I, have a um I, sometimes talk to mayank and he's always like talking about like yeah. The community is so great and like he feels like he's part or they feel like they're part of it, sorry um so yeah. If y'all y'all are looking for a welcoming Community, that's Astro.

A

um Let me see a few more questions. We're really nearing the end, um I'm just curious about like what your motivation for getting involved in Astro was.

B

Yeah I thought so I originally discovered Astro as um a way like this. This cross framework way to build sites.

B

I could use any framework I wanted, including solid, um which is this other front-end framework, I've involved in and then I just sort of like fell in love with it, um especially the community I think the Discord um Community really hooked me I'm, like oh, these people like actually care about Astro um they're, not just here, for support like they care about each other and they care about improving the project, and that was a big motivator um and then yeah.

B

Eventually, um I got involved as a contractor um and yeah I took the opportunity to to work full-time at open source. I never want it to seem. Like oh I'm, you know I do this for free, because that's misleading, like I, do work as my job on um on Astro, um but I. Originally, you know was just super interested in in the community and it just came from that.

A

Yeah and it sounds like like what you said that happened to a lot of people where there were a lot of court s through valued them and decided hey. Why don't you come on as a full-time member or a contractor and I? Think it's good to shout out that, like you are getting paid because a lot of times, people think open source is a free thing.

A

um Someone said a question: they joined late and they're, not sure if it was mentioned it wasn't. um But how would you compare Astro with Hugo interesting.

B

Yeah they start off similar. You can use both of them to generate static sites. They both have this idea of templating, which is like um you know, I pulled that Astro page example on screen.

B

um They both sort of have a language for producing HTML depending on some data. So that's sort of the commonalities. You can use both of them to build a bunch of static, static pages that you can then deploy using like GitHub, Pages or whatever. But after that they start to differ. Astro lets you use, react or spelled or other front-end Frameworks in your project and Hugo doesn't I mean Astro.

B

Also has this SSR mode where, instead of building to a bunch of static pages, Astro has a mode that can build it to a server, and then you can run this server and on the Fly respond to requests, and in that way it's a bit more like PHP or next.js than something like Hugo, so I've also never used Hugo. So.

A

It sounded right, I've never used Hugo either, but it sounded it's not.

A

And my little experience with Astro wow cool, uh you I know you were showing me some GitHub actions. We don't have to go through each and every one of them, but um if you can just like give us the overall like.

A

um I, don't know the words lost my mind, but basically just tell us what what GitHub features that Astro tends to use. Yeah.

B

We can we can look, look at the at the sidebar and and get an idea like the format code, one formats code automatically.

B

um We have a really cool one that I don't know which one it is, but if you are referencing, if, if you have a link in your page that is broken, um it will show up on your PR and be like this link is broken or if the link isn't formatted correctly, like with an ending slash, it will also say like fix the link first, um so that's that's super cool and every night, um this uh GitHub um nightly action runs to take the information in the integration readme.

B

So this is what I was explaining about how some information in our docs lives outside our docs, but is then brought in and that allows the like documentation for a given integration to be in its own repository.

B

um So that's um something else that we use. Github actions for um and I, don't know what the pull request. Labeler does exactly I guess we could read it um uh it just what is it? What does this do?.

A

It it's just label because that's a it's using another action.

A

Once you all label it with something else, maybe um it maybe moves it into a project board or something I don't know. Do you all use like issues in Project? Well, you use issues, but you use.

B

The projects Yeah, we actually also use a project board, but we do have to manually um do.

A

That okay I'm not sure what it does yeah.

B

That's that's super fun, highly recommend, um GitHub project. Oh wait! It's private! Maybe I shouldn't show it, but there's nothing. There's nothing private about the contents of that. It's just like us, organizing what we're gonna you.

A

Know yeah I get it cool awesome so like overall, it's from what I've seen y'all use. Obviously GitHub issues, GitHub projects, GitHub discussions, maybe and GitHub actions. We.

B

Tried we tried getting the discussions off the ground, but because we already had Discord yeah um people didn't really want to have the discussions here and that kind of makes sense. It was a fun experiment, but where we do heavily use discussions is the rfc's repository. So we have a special.

A

Repository for oh you're about to say, oh.

B

Yeah RFC stands for request for comments and um what that means is, if you have an idea of a feature Astro could have.

B

um It doesn't make sense to put these feature ideas as issues for Astro, because issues are more for bugs, but what you can do is submit a document to the rfc's repository that sort of explains your proposal, um and we often before people do a full proposal.

B

They often go to the discussions Tab and you can see this is pretty active like six hours ago. um You know five days ago, Etc so yeah GitHub discussions is, is super fun, yeah.

A

And it makes sense that, like for certain parts of your your project, it doesn't work for the community, but other parts. It does.

B

Yeah I think when it comes to rfcs, people want to say a lot at once and so having a big post form that works great, whereas on Discord, when you're, organizing docs ideas, it's often shooting back and forth really quickly. That.

A

Makes sense that makes sense all.

B

A

All right so basically we're doing all the technical questions and now I'll I'll uh encourage the audience to still ask us a few questions. We did get a couple, but if you have more feel free to type it in the chat, but I have two non-technical questions for you and that's like: what's your favorite food and what's your favorite Beyonce song or song in general,.

B

I, don't even know what my favorite food is. What what what a question that I should have an answer for um I really I have I've had a banana every day for like years, so, okay.

A

B

Have one every day, I probably really like it, but it's also a very lame favorite food. No.

A

You're healthy, you know apple a day. It's a banana. They keep stuff.

B

Choose your fruit: have it every day and keep the doctor away? um Someone says: try, tacos! Okay, um that's my new answer.

A

You didn't have a favorite Beyonce yourself, so favorite song You're, a musician I'm.

B

Gonna shout out an album that just came out that I've been listening to, which is panic at the disco's new album. They.

A

Still make music.

B

Yeah um I mean it's: it's just the front man Brendan Yuri at this point doing his own stuff, but uh I, really like it. um It's a cool album that sounds very Queen very, like classic rock and it's been fun to listen to.

A

That's perfect: that's perfect! No I, love, I love Panic at the Disco I, don't even know the name of this song but like when we were in, like probably Middle School, that panic at the disco song that came out and they're like haven't you people ever heard of whatever.

B

A

My one panic at The Distance.

B

So I Write Sins Not Tragedies, the one everyone knows how to sing along to for some reason.

A

If I ever needed to memorize a song or say the words to a song of memorized, it would be that, and someone said their favorite is Beyonce's. I mean their favorite Beyonce song Is Love on Top, good choice, love, it love.

B

It I'm glad we got a real Beyonce answer.

A

You have a lot of knowledge, I mean, of course you work there, but still it was pretty helpful to see um and I hope. This was helpful for other people who were listening in I want to like re-encourage y'all, to contribute, um and even like re-watch this, if you needed to double check on like how to do it, but go ahead and contribute. The repo is github.com then gave me a lot of good advice about like even what makes.

B

A

Documentation and then also, if you wanted to chat with the Astro Community they're super warm and welcoming, go to astro.build, slash chat and it will lead you to a Discord. Is there any last things you wanted to add or promote? Should people follow you? Oh.

B

uh Sure um they can follow me on on Twitter. You can follow me everywhere. It's jutanium, um which I should have put in my little stream yard header.

B

um That's it yeah, sometimes sometimes I'm pretty active on Twitter. Sometimes I give Twitter up for like a week at a time because it you know, gets in my brain, but if you always want to make sure you can reach me, the Astro Discord is probably the place and you can tag me jutanium there um and I. Will you know pretty much always answer so come hang out.

A

Awesome awesome and thank you so much Dan for taking the time to to hop on the stream and we've got a lot going on you're busy and also thanks to the Astro team for hanging out in the chat and watching us and supporting and retweeting appreciate that um I will say goodbye to everybody now bye, y'all thanks for joining.