Display Byline Request with airSlate SignNow

Resent byline

thank you malcolm uh you were one of the best interns we had uh legendary so uh thank you for the intro and thanks for the invite to be here um i'm currently on the east coast uh so i'm a little bit later so that's why i've got my virtual background on and the light is uh shining down from me trying to keep my dark room in here very light for you all um bonus points if you can recognize where the virtual background is from i've been watching netflix at all uh so i have my slides did i think maybe some people probably arrived after we shared the link so i'll throw it back in the chat again because i'm yeah shit's creek exactly it's the motel i've been enjoying those reruns lately um okay so uh whatever you're watching that right now too oh really yeah it's good it's so good it's officially on our rewind list you know it's it's been i needed some levity i felt like i can't do serious shows right now so um so what i wanted to do let me uh close out my chat and make my screen a little bit smaller and a smaller screen uh so what i wanted to do for this talk was to share with you all some of the latest developments that's going on in the r markdown system uh ecosystem where we're in the process of updating a number of our packages and we're kind of going through some uh some processes for making the various packages more consistent cohesive and easier to use um so you know one of the awesome things about our markdown if you've kind of dabbled in that ecosystem is that there's always new packages that give you maybe entree into some some new kind of output format some new kind of thing you can make which is like really fun and empowering and yet a lot of times you've already subscribed to a previous package that does sort of similar things and you might not be quite ready to switch so and for good reason so we've been trying to go back in time and see those kind of packages that we know people are using and want to kind of make them a little bit easier to use and hopefully easier to maintain so a lot of the stuff i'm going to be talking about a lot of the new improvements is not so much aimed at new users about at improving quality of life for existing users so but maybe when you hear some of those improvements if you haven't tried one of these packages yet you might be more empowered to do so because hopefully you'll realize that we're spending a lot of time thinking and working about how to make the lives of all users a little bit easier so let me go ahead and share my screen now you have the slides let's see there we go oops oh awesome there we go okay so recent developments with our markdown um as malcolm said my name is allison hill uh here's some of the links so you can learn more about my work i'm a data scientist and professional educator at our studio a lot of my work is open source some of it is in public github repositories under my personal account but i also work on a lot of the public repositories under our studio and our studio education github organizations i'm pretty active on twitter and i try to use that as a nice feedback channel for uh pretty enthusiastic adopters of our packages to find out things that are gelling and not gelling when they're using them so you can usually find me on there um and i have a non-well updated at this point website allison.orbind.io um i am an infrequent blogger uh i would like for there to be some kind of system for like impact factors for blogs that you have empowered even by not posting myself but hopefully i've paid it forward by encouraging other people to start their own blogs so uh one of them being malcolm i think oh no malcolm i didn't train you you already had yours you were an early adopter so in the our markdown ecosystem we have about 20 packages um so some of these might be surprising to you when you see them kind of all on a list but we're actually a little bit bigger as an ecosystem than even the tidy verse and for me as an educator when i taught tidy models i felt like that was a lot of packages but when i started looking at the our markdown ecosystem i was like gosh that's a lot even just the ones under the our studio organization so this list shows you the github organization on the left and then the name of the package on the right even just the ones alone in the rstudio organization there's quite a lot so we have our markdown which is sort of like the granddaddy package of all of these they're all built on top of that we have distill flex dashboard the learner package tufty book down block down markdown articles page down reveal js and then schrenjen for making slides is in eway's private github and then nidar as well which i'm sure many of you are familiar with if you've used our markdown it's kind of one of the building blocks for being able to include our code in your arm markdown documents and then a lot of these are kind of more under the hood very important things that you may or may not interact with but are there nonetheless in all of those packages so we have quite a large suite of packages that we're maintaining that relate to this ecosystem but the ones i wanted to share with you about today were the ones that we've been working pretty hard on improving the usability of so the first one that i wanted to tell you about and maybe share some new things about is the distill package and this one is got the most updated version currently on crayons so if you install packages distill from crayon you're going to get the most up-to-date version with all the bells and whistles that i'll be talking about here and i'm going to do a demo to show you guys a little bit more about the experience of using distill now so distill if you haven't heard about it it's a output format for our markdown that's optimized for scientific and technical communication so what does that mean that means that it has some nice places to add some metadata that a lot of scientists and people who do technical communication care about like being able to add your orcid id being able to have a creative commons license statement being able to link to the source code for any kind of blog post a lot of these kind of nice things that you might have thought before when you were working with any kind of html based output with our markdown that like oh that would be kind of nice or maybe you've seen it on somebody else's site and you thought oh how did they do that distill has tried to build in those features for you so there's less friction for you to be able to make something that's easier to share this still also has nice css which means it has like kind of nice styling right out of the box and i'll show you an example in a second so you can see what i mean um for the most part uh we we hope that it's not something that you want to change a lot of but i'll share with you some of the improvements that we've made along the way recently in the next in the latest version [Music] and one of the primary benefits of distill is that there's no extra dependencies so it still allows you to make html based outputs including full websites with no additional dependencies like any kind of static site generator so if you've ever built a website and tried to use jekyll or hugo or any other static site generators there's a lot of flavors of them you may have been dissatisfied and thought i just want to host some html pages on a website and be able to share them and link to them easily so i think distill is a pretty good answer for being able to do that if you've ever used our markdown the actual base package of our markdown does have a built-in site generator and so it still essentially wraps that up with our markdown package you could have made websites pretty similar to distill before but distill again has some additional bells and whistles that make it really optimized for scientific and technical communication so i'm going to show you real quick just the actual documentation site for distill see it's taking a second to load uh so this site is built with distill so you can see that it has a built-in site search which works pretty nicely so i'm going to do a search for theme and you can see that what pops up are a few different pages so you can see that there's just still basics distill for a markdown creating a blog creating a website and you can also click on orchid ids for each of the individual authors you can see their affiliations uh you can see a citation that's automatically generated and that's going to be consistent with google scholar citations so people can search for your article um there's this nice appendix at the very bottom so that was the very top of the article that's that header at the very bottom you've got this nice little like reproducibility appendix that has the ability to add acknowledgements you get footnotes with distill and they are hoverable but they linked down to here so if i click on this little link right here it's going to take me back up to where it is and you can see that that's actually a hoverable footnote uh you also have the ability to add this attribution citation the bibtex citation and a lot of other bells and whistles that we think make distill really nice for being able to publish research or more you know data science code related blog posts or articles you can render figures kind of nicely going across and outside of the article margins so this is a website that's built with distill it's just a collection of distilled articles so distill articles are the html format for single distill rmd files so you can knit to a single distil article but if you want to have a full website then you'll knit a few rmd documents to distill articles and distill also offers you the opportunity to have a blog which allows you to have a really nice listing page so i'm going to show you the rstudio ai blog which is a great example of this so when you go to the rstudio ai blog you can see that there's this nice listing page which is sort of like a menu of all your different blog posts shows you a nice little preview image some metadata some categories and then you click on each individual article to be able to see the individual blog posts so that's a really nice benefit of distill so if you wanted to make a simple website that has this kind of upper navigation bar the ability to have drop down menus and some nice metadata and some nice out-of-the-box css styling i think distill is a really good option for people who really want kind of no must-know fuss but they want something to look really polished and nice for being able to share publicly and we know that a lot of teams actually use distill for team blogs as well so it's really nice for collaboration too but what we heard frequently from users was that they just wanted to change like the fonts the colors the size a lot of people actually wanted to use distill to be able to make internal knowledge repositories for their their companies for their meetup groups um uh and even just for their personal websites uh and that was really one of the legitimate knocks against distill for us as developers was that we we knew that it was hard to customize even if you knew css some of the things were a little bit difficult to figure out uh so what we did with this latest release was we developed something called the themer so i'm going to do a short demo and show you how to use that now so i'm also going to show you the documentation for theming so you can actually theme an individual distil article or a distilled website i'm going to show you how to do a website i'm going to use the documentation to guide me so i'm going to start a new project in my art studio and i'm going to pick a distilled website and i'm going to create my project you can see that a lot of stuff is happening it opens my nice new project and i do have some pretty custom things set up on my desktop so i apologize i i at night i switched to the cupcake theme so that's why it's very pink so you can see that i have an index.rmd file over here in my files pane you can see a little bit more about what all populated here so if you've ever made an our markdown site before you have an underscore site yaml so this is really kind of driving that upper navigation bar so that's where the name and the title the website come from and you can see that i've got a home button an about button um and then this output distill article tells it that all the individual pages are going to be output to that same output format so i'm just going to render this site really quickly so you all can see what it looks like out of the box so i used the build tab in our studio ide and i built the website and you can see in the viewer pane i'm gonna pop it out into a big window that i've got my nice little website right here with a home page and an about page so that's straight the distal site i'm going to demo know how to theme new themer so if i go to console i'm going to minimize that so you can see a little bit better is my font big enough can somebody give me a thumbs up hopefully it's big enough excuse me library distill you can read it okay good okay so in distill i'm going to do uh create theme name and i'm going to call it la rug so we're going to run that function and you can see it gives me a nice little created css file at theme.css to do customize it to suit your needs to do add theme entry to your site article yaml okay and then it gives you a little link that says see docs at and that's what i'm going to lead you through right here so what opens up also is this new css file that i just created called la rug.css and it gives me some base variables that have to do with the css custom properties for this site so what we've essentially done is given you a way to override what the defaults are but we've also revealed to you what the defaults are so if you're sitting there looking at your site and you're thinking ugh the font size for the body is just like too small for me i can't read it um you can see why it's 1.06 rem here which is uh relative units for relative to your normal default browser which is usually 16 pixels so if you wanted to increase the body size you can change that number and same with any of the other numbers that you see those are all in pixels currently you can also change main font colors so if you know the hex color that you want for the title color for example or the header or the body color any of these things you can change those quickly and you can also specify custom fonts this is a little bit clutchy because you also have to import any fonts through google fonts and so there's a little bit at the top where it says optional and better custom fonts here with an import statement so if you go to the documentation there's some good examples to show you how to do all of those things so what we've shown you how to do is to take this default page here which is pretty similar to what we're looking at on my desktop and i take you through the steps of being able to import a few fonts and i'm just going to copy and paste from here and i'm going to place those oops wrong repository i'm going to place those at the top of my la rug so i'm going to import them all all those fonts from google fonts and i'm not going to spend too much time talking about that but if you've ever imported google fonts before this should be familiar and if you haven't used google fonts before this is probably one of the lowest um uh hanging fruit ways to be able to get it into your site without locally hosting it and then i'm going to map those fonts onto a few of the different custom properties in this file so i'm going to change the heading font to the omiri font um the mono space font to one called dm mono the body font to better and the navbar font to a miri so i'm going to scroll down here i'm just going to replace those so so far i've changed the fonts i haven't changed any colors yet i might go ahead and change these website header and footer colors because they're really easy to see when you go through it and i know that those are down at the bottom of this page so there's all kinds of different properties in here for you to change people like changing all kinds of things but hopefully what we've done is scope it out so that you don't have to do all the spelunking around in the css divs themselves looking at the hosted website and doing inspect element for every single thing that you want to change we tried to pull out the most common elements that you'd want to change and give you the variables to override them so at this point i should be making a site that looks like this the pink background and slightly different fonts the only thing i haven't done yet is i have not applied my theme so i need to add the theme to my my top level site yml file so i'm going to go back to the site yaml file here and show you that right now i have this output distill article oh i'm not putting it under there i'm putting it at the top level so i'm going to add it maybe it doesn't matter where i put it and i called mine la rug so i'm going to say theme that's the new key here and it has to be a css file and it's expecting it to be in the project root of course it doesn't work let me see no said file directory i'm not sure why that says that let's see if it'll go okay it worked all right so i don't know what that error was about but if i open it up in a new browser you can see that it looks like a very different website and actually all i did was change the fonts and then i changed the colors around the the header and the um and the title here so just a short demo to show you that the the documents are there and we hope what we've given people is a way to quickly experiment and play around with things i know that there's actually a few people that i saw enter the room that have used the distill themer and have come up with really beautiful sites so that's exciting for us to see um and we hope that what that does is enable more people to make distill sites for maybe all kinds of different organizations or personal websites even we see it used a lot for personal blogs now because it's so easy to use and because the only thing you need to worry about is your code actually running which is not always the inconsequential thing but maybe that's the thing that you should be focusing on instead of having your site be able to build so that is kind of in a nutshell what the distilled themer does for you um let's see so there's a little bit more about what's the latest with the distill package on our studio blog we just published this on monday and this gives you a little bit of an overview about the package itself sort of reintroducing it and telling you about the output formats a little bit more about the single article html format which i didn't talk too much about and links to the features and how to find out more about them on the documentation sites and then a little bit more information about websites and blogs how to add site wide search and then a little bit more about the femur as well other highlights from this new version are that headings provide anchor links when you hover so if you can see there like if i wanted to link you to the specific section to apply the theme if i click on that anchor there then you can see that my url changes to be hashtag apply theme at the end and then i can copy and paste and send you the exact link to tell you how to apply the theme we also have an approved default syntax highlighting theme and that is designed specifically to meet wcag 2.0 guidelines for contrast accessibility which actually a lot of the syntax highlighters do not meet so previously when you made a website maybe with distill or really any um of our markdown output formats and used one of the bulletin syntax highlighters a lot of times if you ran the diagnostics on the website you would come up with warnings for low color contrast on your code and that was kind of a hard thing to be able to change so we designed the syntax highlighter to be able to kind of take that pain away and so all colors in the syntax highlighter are above the 4.5 minimum threshold for color contrast compared to the normal background color of your code we've also improved the handling and display of article categories for blogs so on our studio ai blog for example you can now see that you have uh it's visible which individual categories for every article are applied it used to be that there was just this category listing over to the right which was sort of helpful because you could click on it and you could see everything say related to bayesian bayesian modeling but if you were on the main listing page you couldn't see that this article you know maybe included the tabular data category or that this one included the torch category so we think we've made it a little bit more usable and a little bit more flexible for people i also want to share that there is the the link is in my slides there's a new package down site for the package that has this examples gallery here and so this was uh really helpful to be able to see people in the community who made distilled sites and allowed us to link out to them so some of these are personal sites and some of these are also for teams that collaborate so for example the open source football blog is powered by distill it's a highly customized website and it's a really beautiful version of something where a lot of different people contribute to the blog and they do it all through github and um and powered by the distill package so we hope that we've given you a lot of places to explore and maybe get excited and get started with website making with our markdown and maybe taking some of the pain away from feeling like you have to be a web developer or you have to know anything about static sites to be able to have a website with a blog it's just a collection of html pages but it can look really nice and it can be manageable and something that you can easily maintain and if you want to post every six months no shame in that it will always build when you come back to it so that's really a nice feeling as someone who has subscribed to the blog down model of blogging i can say that when i finally get up the energy and the time to actually write a blog it's a real bummer when the site doesn't fall or when i have to deal with troubleshooting errors so that's one nice thing about distill i think it's an easy workflow so the next package that i wanted to share with you about was blog down and so i'm curious i don't know if anyone here in your meetup has ever done this but um if you go to um the participants link at your in your zoom the bottom where that will allow you to see like all the um the names of all the people that are attending um in that view you can find a little button that would allow you to do like a thumbs up or a clap or something like that um so hopefully i'm not sure if you guys can actually see my zoom when i'm screen sharing so hopefully i'm explaining this well um but what i'd love for you to do is if you've tried blog down before i would love for you to give me a thumbs up over here so if you click again on participants on your zoom menu and you can see that there's a few different options um i'm going to give myself a thumbs up so i see emil john peach okay i'm scrolling okay i see a few people oh i see jenny richmond here hi jenny kelsey gonzalez yes certified trainer at our studio okay sylvia of course shelby okay so it looks like actually not a lot of people have sampled this uh um blog down um so you may not feel immense pain and understand how much work we've done to decrease the pain or maybe you were really smart and you decided to hold off on blog down until we really got uh all the details worked out to make it more user-friendly and less scary so either way you know maybe these um maybe these new developments will give you some courage to try blog down if what you were thinking when you saw distill was oh that's really great but i need something that's a little bit more personal or i need something that has a little bit more flexibility and i'm not too scared about doing some kind of web development or css tweaking here and there and maybe learning hugo as well so blog down is a kind of more our most like high-powered website making tool and it's really um geared towards giving people ultimate freedom and flexibility to make a lot of different kinds of websites whereas distill is really optimized for being a collection of individual articles with the possibility of adding a blog blog down depending on the theme that you choose can give you all sorts of access to all kinds of different looking sites that are pretty spectacular and i'm always amazed at the things that people make in block down as well and so the developments i'm going to share today are still in the development version of block down so you'll need to if you want to use any of these features you'll need to install from github from our studio blog down we're still doing some testing on the current version which is version .22 but it should be on crayon before before the global conference in january i imagine so we're still working out some of the kinks on this so hopefully if you have any feedback if you do end up trying any of this after um our meet up tonight i would really love to hear about it we're trying to really make blog down a little bit easier for people including ourselves we got a lot of internal feedback as well so if you're a little bit unfamiliar with the blog down package the benefits are really that it gives you the power of hugo which is a static site generator so it's a dependency and it's one that you need to manage you may not necessarily need no hugo as a templating language but you will need to interact with hugo at some level if you choose to go the blog down route so you should know its name and get to know it a little bit better but hugo is a static site generator that really allows for markdown first content so it's really nice for our markdown users because you can knit your content from our markdown into a markdown format and then hugo builds your site from that and it's a pretty beautiful system and i actually really love the hugo templating language the more i've learned about it but in hindsight looking back at younger me when i first learned blog down i knew nothing about hugo but i knew i really wanted to make a cool looking website and i was in a computer science department at the time and i thought what a shame that i'm sitting here with no website and i made a better website than a lot of the computer science people with blogs down so you can use block down without knowing all of hugo so don't be super intimidated to start if you're feeling scared about hugo it's not that bad but we've tried to make it better another one of the powerful things about blog down is that you have access to a ton of themes and i didn't include a link to this but i'll take you to the hugo themes site right now this is the complete list it's themes.gohugo.io and any of these are hugo themes that you can use with blog down so blog down essentially gives you access to these huco themes and allows you to use the rstudio ide to build your website and to include content that has our code chunks in it because you can use our markdown that's really what blogdon does for you and historically block down didn't add a lot more to the user experience we've tried to add a little bit more in to help folks to be able to fall into the pit of success a little bit easier and not the pit of paralysis and despair with their sites so if you scroll through the hugo themes you're bound to found one that looks tempting to you um i often advise people if they're just getting started with blog down to try to pick like your top five um and then don't be afraid to try individual themes start tweaking them and don't be afraid to just you know chuck them just just trash them if you don't enjoy working with it because you're going to be working with the theme for a while and it's pretty hard to switch themes once you've already committed to one but they do give you a lot of flexibility and power you can also get subdirectories so one of the really tempting things for a lot of people when they're looking to move past distill in our markdown sites and even book down sites to some extent is that blog down allows you to have sub directories of content and you can have any kind of content that you want in a blog down site so it's really nice to be able to have those sub directories and be able to be a little bit more organized whereas a distilled site just ends up kind of having a lot of rmd files in it and it can kind of be a little bit difficult to manage once you have a lot of those so one of my favorite sites is malcolm's personal site actually which i don't know if many people here have explored lately this is built with the hugo academic theme it has a really nice like kind of landing page and you can see it's got really nice i forget what this part is called it's like a it's not the parallel x it's the um the slider uh feature carousel thank you thank you um so i really like that i actually integrated on my site after seeing malcolm using it it was so cool um but you can see that this just looks a lot more custom than the distilled site so whereas a distilled site you can change the colors and the fonts really easily and and we made that easier for you with the themer a lot of block down sites even if you use the same theme end up looking pretty different to me so they always look very custom and like malcolm's site for example is very malcolm so it's a nice way to get to know somebody it's a nice welcome mat and especially if you're going to be going on the job market at any point it's a really nice way to put your portfolio together online and my own site is also built with the academic theme but just to show you how different it can look this is the exact same hugo theme but just styled very differently and there's my little carousel as well i have a little bit different content a little bit different headers we have a lot of the same features uh and then one of my passions i stole some tricks from you too it's one of the benefits of all using the same theme um and then uh one of my interns um two years ago desiree uh made this site this is using the hugo academic theme also um so and i solo i think thanks from desiree when she started to play a good thing she's a css wizard uh so this is also using the hugo academic theme so just because you're using even the same theme doesn't mean that your site's all gonna look alike you can really the possibilities are endless um really the main limiting factor is how much time you're willing to devote and how much css you want to learn and how much you go you eventually want to learn but we did hear from a lot of people including internal teams you know my blog down hugo site is broken um and i had this happen to me several times especially once you start building multiple sites or even if you just have the one it's very possible for your hugo build to go down and it's a little demoralizing when it happens so our solution has been to try to make your blog down unbreakable uh and this has involved a lot of steps and a lot of internal discussions on the our markdown team but i think we're to a place where we've at least tried to empower users we can't necessarily promise it won't break but we've tried to change some of the default behaviors and empower users to better be able to figure out what is the thing that broke or how can i prevent breakages in the first place i'm going to lead you through some of the things that we've been working on now so uh some of the things that can go wrong two of the main things that can go wrong um and i think of them as these little cats creating total mayhem hugo versions it can be mayhem it is a static site generator and it does have versions and it does have things that become deprecated certain functions in hugo it adds certain functions and you may not be using hugo yourself you may just be using a theme the trouble is the theme is using hugo and so themes can have hugo dependencies as well so you end up having really when i say hugo version i kind of mean hugo and theme versions so that's two dependencies right there that can get out of whack and can cause you problems and make it kind of painful to figure out what's going on and how to save your site the second thing that can go wrong is your are packaged versions so if you've been doing this for a little bit and you have a few different blog posts some things might change in the packages that are underlying your code and the problem is that most times if you have any kind of our markdown generated content it's probably likely to be in your blog posts and you are probably wanting your blog posts to just stay the way they were when you published them so if you're not updating them you probably want them to just stay frozen you want them to be a fossil um and that's not necessarily how the default behavior of block down worked um previously so in past versions sometimes block down would kind of try to re-knit old rmd documents it was due to some some defaults in the package that we have now engineered away for you all but that was part of the pain that many of us experienced especially those of us who have kind of longer running sites and collaborate on github so how do we tackle the hugo versioning problem this was one that really really hits many times i feel that pain so if you install the dev version of blog down you should be able to check your hugo version now this was actually there before so this is not necessarily a new function but you should always be able to know how to check your hugo version so you should always know even if you don't feel like you're interacting with hugo you're using a theme and you've definitely installed it when you've used blog down so at some point you've installed hugo you can check your hugo version here and the hugo version looks like usually digits like uh let's see i'm going to close out this it's usually like a a number a decimal two numbers a decimal and then another number at the end um so let me show you just what this looks like i'm going to open up my personal site which is thankfully still running but i feel like my time clock is running out and i need to i haven't actually adapted to this new version of log down yet on my personal site um because it's still a global pandemic and i don't have a ton of free time i have a three-year-old so i thought i'd use it as a great example to show you all what uh what changes we can do here so i'm going to do a library block down and i'm going to type hugo version okay um so you can see that i've got version 0.78.2 running so this turned out to be actually really important and it matters for my theme and it matters from my deployment plan for being able to publish so you want to know what kind of huge version you're running locally but you'd also like to set it and forget it and so this is something new and this is within projects so if you do have multiple blog down projects you do this for every single project but it's really a total game changer and i haven't done it yet for my site so i'm going to do it now so in the development of version of log down you can use this config underscore r profile function and god willing it works it says you know some information here it says the file our profile exists so i will not overwrite it with this content but it does tell me that a few options to customize the behavior of blog down are listed here and i didn't find the option hugo blogdown.hugo version on our profile so i will append that option to it okay so that was a lot of stuff let's actually just look at the file so what it does here this top bit uh is required if you've ever not worked with our profile files before what this does is you can have a global our profile file um on your computer but then you can also have one per project and so what this does is it looks for a global our profile first and reads that in and then appends this so it doesn't try to replace that so you can see that i actually already had my our profile set up to have a few options for block down setup but i did not have the hugo version set up so it appended it at the bottom i'm going to clean this up and move it up to this larger chunk so now i have my blog down version hugo version frozen to be 0.78.2 so that means that blogdom will always build my site locally with that version of hugo which is really important to me because there's a lot of other sites that i run where i have to have different hugo versions running simultaneously and previously i had no way to version my hugo versions and that was a real uh a real sticking point for me and being able to manage multiple blog down sites so set it and forget it for every project now you can also tell netlify and forget it and now this was always the case but we didn't necessarily surface it for users very easily so there's a new function called config underscore netlify and so i'm going to use that right now to show you that it opens up my existing netlife tomo tomophile and it tells me a lot of stuff in there it says the current existing nutella phytomophile is the new netlophytomol will be and so it essentially is asking me permission to overwrite the existing netliphytomol so it looks like it's basically respecting what my existing tomopha look like looks like it's just replacing all my 0.71.1 with the 0.782 so this is how i control what netlify actually uses the version of hugo the network i uses to build my site and it's really important to keep those two in sync so you want your local version of hugo when you're building your blog down the site to match the nullify version so i'm going to actually tell it no i do not want it to rewrite and i'm going to do this manually because i i like the formatting and it looks like it's going to mess up my formatting all right so that means i've frozen my r profile i've frozen my blog down version and i've frozen my hugo version uh in netlify and usually you only need to set it once in this build environment variable uh a final thing that we've added with hugo versions is that you can now manage because now that there's multiple versions of them how do you see what you have and i actually have a mess of huka versions it turns out i've got three and i had no idea so i have 71.1 now that's for a site that i know of so i want to keep that and then 78.2 is my current version and i think that's more of the up-to-date version and then i have this number one this number three here use our local bin hugo i don't really know what that is and i think i've been advised that i can remove it so you can use a new function called remove remove hugo and i'm not sure if this will work i have not tested this yet because i didn't want to i had such a perfect worked up block down repo that i thought i'll give it a shot no i can't do it there okay i probably can't figure this out live i tried looking at the documentation for remove hugo it requires a version and don't know what the version is for that one so i'll leave it but if i wanted to remove 71.1 i could probably use remove hugo to do that but i do not want to do that because i want to keep and then our package versions uh that is the other thing that can get out of sync and you would like to be able to freeze maybe the package version that you used when you knit your document now we don't necessarily have some kind of package management system for block down but what we did do was we made it so that you could have the option to always knit your own content yourself so one of my favorite commit messages by e-way was make the knit button great again um so this was a very exciting day for those of us who've used blog down so if you've ever used blog done before and you've accidentally had that muscle memory to click the knit button and experienced all kinds of weird errors that you couldn't debug it was because you couldn't knit uh use the knit button to knit to the right output format with block down we've since fixed that so you can actually knit now so when you're working on any kind of our markdown content in a blog site you can click the knit button just as you normally would and it will render to the right output format so you don't need to have that fear of using the knit button again so that's one way to help you manage your own your own r content is to make sure that you're the one doing the knitting now if you want to be the one doing the knitting you also have to actually tell blog down not to be a knitter so the way you do this is to go back to that our profile file i may have no i didn't leave mine open um [Music] so it's another option that we add to our profile file it's this block down knit on save equals false so the current default behavior of block down is that any time i have an r markdown document open when i save it it'll automatically knit it so i really recommend to run knit on save false because that means that you can kind of work on a document a little bit easier you can run it in interactive mode where you're running code chunks and maybe testing out the code but you're not trying to knit the full document and rebuild your site every time you save which is what would happen in the previous behavior and then i also really recommend setting this option this files filter uh it's a little cryptic and i apologize for not having time to explain this more but this was part of one of the reasons why if you ever used block down with github that you might have gotten into various stages of paralysis with your um websites where our where blog down was detecting that certain uh posts needed to be re-knit and they didn't actually need to be renet i know that happened to us many times on our education site um so what this does is it basically um uh tells blog down not to use timestamps anymore because if you're pulling and pushing from github the timestamps are known to kind of not be very reliable and that was actually the issue with the previous behavior so i really recommend setting this files filter md5 some filter it essentially creates a file hash and allows you to work off that then rather than time stamps so both of those should help people be able to keep their r package versions just the way you want them and if you have a knitted file in your content directory you'll know that it's just going to stay there and blog down's not going to try to force you to re-knit that file uh so i know i covered a lot of our profile options which might be a little bit new for people in terms of being able to interact with a package so here's a kind of larger healthy r profile for happy blog down users so having whatever blog down hugo version set here is some is equal to what you locally have you want blog down to know that version you want to kind of freeze it um you don't want it to knit on save you'd like to do the knitting yourself and especially now that the nip button works you can click knit to knit that makes life a lot easier setting that block down doesn't use time stamps to figure out when to knit it instead uses file hashes and then there's some other nice to haves here too i'm not going to spend too much time on these they're slightly documented in the blog down book but we're working on improving that as well we did change a default so that now all blog down sites start with page bundles and if you're working on a very old site with blog down and you're thinking to yourself what on earth your page bundles we're improving the documentation right now and we also included a new function to help people bundle a site that is unbundled so look for the bundle underscore site function it's currently in the development version if you're sitting there wondering oh but i actually really liked the previous behavior of blog down where sometimes it would try to re-knit all of my our markdown documents in mass you can still do that you can use the build site function and the argument is build underscore rmd equals true so what this will do is it will in mass knit all of your arm markdown content and build your site at the same time so be careful this is a warning um but if you liked that behavior you can keep that behavior uh and this is because blockdown build site no longer recompiles our markdown files by default because it may be expensive and often undesirable to compile rmd files that have been compiled before oops if you don't want to recompile if you do want to recompile the files use this um so a really good example is the tidy models site for example this is a website built with blog down that i made that had dependencies of a lot of packages that i actually couldn't install that required our stan and we were having immense troubles because blog down would try to re-knit those posts that max had written and max had all the stan installations complete on his computer i did not um and we ended up having to go through some uh saving of the files and an external project and bringing them back in because i couldn't build my site because it kept trying to rebuild so this is a really important one for me but i recognize that it's also important sometimes to be able to rebuild everything at once and just torch the whole site and rebuild it so you also still have that option if you're an old school blog down user like myself you might be wondering now when i render my site what happened to public um so what used to happen is in your files pane when you did a local preview of your site it created this public directory and that was actually what the the site was that you were um you were building and previewing we're actually switched to a different renderer so it's not generating the public site anymore but you can force it to generate the public site by doing this build site function so if you're missing public and you want it back that's how to get it back so i know that was a lot um and you may not even know where to start with this menu um so let me throw one more thing at you we added something that we are trying out with blog down um we're thinking of it as like a pre-flight checklist so we now have some checking functions that will hopefully help you be able to have some sanity in your blog down sites but also we think better work with collaborators so if you have somebody who's doing like a guest authored post for you for example or somebody who doesn't know all of blog down and they're trying to contribute to your site but you're thinking oh no there's so many landmines there's so many ways that things can go horribly wrong we added this these pre-flight checks to hopefully help you so that you could at least tell them to be able to install the block down package and run these checks and make sure they come out clean and it'll hopefully help you help guide you through how to do the right thing so you can check your entire site by doing check underscore site and what it will do is it will wrap all of these individual checks below it so that's a shortcut i'm going to show you them one at a time real quick so check config is checking your configuration file for your site so if you open up config tomo or sometimes it's a yaml file it looks like this it's a lot of content there but there are a few landmines that we know of that we can help you prevent so i'm going to show you what check config looks like right now in my console so you can see that it's checking my config tomo file it actually opened it up for me here i checked in my it checked my base url setting made sure that there was actually something there sometimes when you have a demo site with blog down it has just a forward slash and you don't want that in production and checking the ignore files settings so it's telling me that i do need to change some things in my ignore ignore files field i'm recommended to ignore more items in my ignore in my ignore files field um and i'm recommended to remove the underscore files dollar sign in my configuration tomo and then it also checks to make sure that the unsafe option for goldmark is um uh used and this is due to a breaking change in hugo a while back where they changed the default markdown renderer for hugo and that made a lot of people's sites not show up anymore which was a fun change so hugo versions matter so it looks like i need to remove this part um and it looks like it wants me to add a lot more to my ignore files but i'm just going to remove the thing that it told me to uh so that's the first one that's check config let's do my check get ignore uh so it checked my git ignore and what it was doing was it was actually making sure that we've seen a lot of people who had in their get ignore um ignoring the rendered files sometimes that can cause problems my getignore is actually pretty clean i'm ignoring my public folder and my resources folder because i'm actually doing a continuous deployment build through netlify so it's creating my public folder for me so it looks like my check my get ignore is coming out clean check hugo i think i should have fixed that right now so it says checking hugo using hugo 0.78.2 you're recommended to set the version of hugo via options in our profile okay i did that it looks like it's not reading that correctly i might need to restart it for that to work uh check netlify it's checking my netlify file what it's actually doing is it's making sure that my public my publish directory public matches what's in my config tomo file and it's checking to make sure that my hugo version here matches the same hugo version and the r profile file so it's not very chatty right now we're going to work on how that looks to users to make it a little bit clearer and then the final one that you can run is check content so check content does a lot of stuff for you but it's all checking that content folder so that's usually where you would put all of your stuff so content is where i have my blog posts it's where i have all of the stuff that you see on my actual site and so what it's doing is it's searching for posts with future publish dates because we know that these end up not getting rendered on a published hugo site and this is optional gotcha for new users so we're screening to see if there's any posts or any content with future publish dates and it flags one of them but i know that to be there and it's intentionally not published yet um so that's good that it found that it's also searching for draft posts so draft is one of the yaml keys in a blog down post that you can use if you want to sandbox your content for a while but it's often confusing because people when they go to publish forget to remove the draft true key and they're yaml and so they're wondering why is my post not coming up and it's because it's marked as a draft so we also screen for those to help cat you catch those we also check for our markdown posts that have not been rendered so because now um if you're not knitting on save um and if you're knitting with intention it is possible that you could try to publish something and you just have the rmd file um in your repository but you haven't you forgot to knit so that's essentially what it's checking for is did you forget to knit or not um checking for our markdown posts that have both md and our markdown and html output files so this is checking for duplicate content and this is a real gotcha for people uh who um who might be using the nip button and then also kind of be working interactively sometimes you can create different artifacts of the same post with different file extensions and the way hugo renders is it chooses the html first so this is often confusing if people decide to switch and want to create a markdown post instead um they'll be confused about why the content that they're seeing published isn't updated and it's because hugo has grabbed the html first and maybe you forgot that there was an html file in there so this is checking for duplicate rendered output files uh checksfor are marked on posts that are older than their output files so this should flag ones that maybe look like they might be out of date and it also checks for bad html files generated with old versions of block down so when you use the nit button when the nit button didn't work it would have created an html file that would have looked really odd or possibly not rendered when you publish so it also checks for that so it does a lot of screening for you and we hope that this helps kind of create a little bit of a safety net and a little bit more of a feeling of empowerment for users to be able to feel like they can be more proactive instead of reactive when they get build errors or when they see things surprising on their website or when they don't see something that they're expecting to be seeing there's all kinds of things that can make you feel really powerless when you're first starting to work with blog down and if it's one of your first experiences working with html based outputs and websites and static site generators and we know it's a complicated field so we tried to build these build these pre-flight checks to be able to support anybody who's also teaching blog down so that you can really help lead people through all the different elements because there are a lot of moving pieces even just looking at these checks you can see that we have to check the interaction with github our configuration file hugo netlify and then finally our markdown content so there's a lot of moving pieces and we hope that we've given people a bit of a road map to be able to problem solve on your own and also help you be able to find better documentation to help you and not feel so paralyzed if your site doesn't build or if you see an error so i basically tried to do the our profile and pre-flight checks demo while i was talking um i have a learn more with a grimace emoji um we are in the process of updating the blog down book but um we did put a note from the authors at the top of it that some of the information and instructions in the book are now out of date because of changes to both hugo um hugo changed a lot after we published the book originally and then now the blog down package um hopefully in the better direction but we know that we are working on that so we do have a link there if you go to the blog down box suggestions for improving the book and please file an issue in the github repository i'm going to show you what that looks like right now we've um [Music] so if you google blog down book it's the first link that comes up if you click on the link there it'll take you to a place to make a suggestion for documentation improvements this would be really helpful for us as we're starting to work we're going to be trying to make documentation improvements um as we wrap up these new developments um new developmental features that we're testing out so please feel free to make any requests if you've tried to learn blog down before and you've gotten stumped over something and you felt like the book needed more coverage of something this is exactly where you can file your grievances and we will find them and we will try to address them anything that you enter here will also be automatically labeled with the documentation label for us so it makes it easier for us to be able to keep track of it and close the issues as we're going through and start updating the book if you've had any other issues with using blog down when you go to the new issue in github link you'll see that we've created a little bit more of a github template for issues so you can now choose bug reports documentation improvements feature requests or you can link to an unanswered question so we do have some rules about whether you put questions in the github for example because we really try to rely on forms like stack overflow and the community site for that but if you have an unanswered question for 24 hours we do give you the option to link us to that so that we can have the possibility of trying to either address it or it might stem from something that we can fix on our end so we have that option as well and then we have links to an issue guide and we also have the links to ask a question on our studio community or to asking question on stack overflow there so time check is 9 28. i won't have time to go into book down or syringe and blog down ended up taking up we had a lot of improvements to go over one of the major things about book down that's changed is that there's a new output format for html based books it's called a bootstrap four book bs4 book it's developed by hadley wickham you can see a pretty awesome example of it in production here this is very stylized but still very nice looking version of the bootstrap 4 book it's got really nice search actually the search is the same as in distilled it's powered by fuse.js and so like let's see what psychology brings up if i do that the search works much better than the default search with book down if you've ever used that before this is also currently in production at artford data science as well the bootstrap for book it is also in production at ourpackages.org so you can see all kinds of different versions of this it's not yet on cran um but it is on its way so that's the newest output format for book down and then sure engine um the biggest news on sure engine if you have been a user and you've been blocked by this we now have the ability to help sell uh self-contained slides this was actually the third issue filed in the shrinking repo a long long time ago let's look at the date uh it was originally written in december 2nd 2016. it was closed september 24th i think so um i think uh it was kind of a a real difficult tricky problem to solve but uh if you've ever worked with sringen and been blocked by needing to be able to be connected to the internet when you built your your slides then you might want to look into that new feature it's not well documented yet but we are also working on that as well so i will stop sharing my screen now and i'm happy to