text
stringlengths
0
1.17k
[1583.90 --> 1590.10] i would never have thought to do um so he and you know he scheduled all of that he flew out from dc
[1590.10 --> 1596.74] um to get to san francisco just for this um and it was a it was a really cool experience so he's been
[1596.74 --> 1602.14] he's been an advisor a serious very serious advisor of this project um partly because i think he sees
[1602.14 --> 1608.74] the potential of static site generators and the because jekyll's already on github pages the amazing
[1608.74 --> 1616.66] potential for um open data for um open source websites in general um the bootstrap website the
[1616.66 --> 1623.38] ratchet websites are both open source and on github pages um and so and the you know it's an
[1623.38 --> 1629.54] alternative to to wordpress in many ways because it is very content focused though it's less focused
[1629.54 --> 1634.90] about how does my theme look um it's more focused on what are the words that i'm putting out there to
[1634.90 --> 1643.56] for the world to see um it he's sort of been an evangelist in many ways of jekyll um and a wonderful
[1643.56 --> 1650.52] supporter of it let's pause the show for a minute give a shout out to our sponsor snap snap is a
[1650.52 --> 1655.64] hosted ci and continuous delivery service that goes far beyond letting you do continuous deployment
[1655.64 --> 1662.36] don't waste your time set up your own ci box under your desk use snap snap has first class support for
[1662.36 --> 1667.16] deployment pipelines with snap you can push any healthy build to multiple environments automatically
[1667.16 --> 1671.72] or on demand this means with snap you could do things like deploy to your staging environment today
[1671.72 --> 1677.88] verify it works and later deploy the exact same build to production snap integrates deep with
[1677.88 --> 1683.24] github has great support for lots of languages databases and testing frameworks snap deploys your
[1683.24 --> 1690.84] application to cloud services like digital ocean heroku open shift aws and many more you can also use
[1690.84 --> 1698.20] snap to push your ruby gem to ruby gems and snap is always free for open source projects try snap for
[1698.20 --> 1707.08] free for 30 days today sign up at snap ci.com slash the changelog i never really thought about the i mean i
[1707.08 --> 1711.96] guess it's it seems kind of obvious and logical but i never really thought about the impact to
[1712.68 --> 1719.40] increase the level of open source whether it's code content or whatnot that jekyll's actually had the
[1719.40 --> 1723.72] impact of i always kind of i guess i really just never thought about it like that because i mean
[1723.72 --> 1729.40] we covered chicago's open data about a year ago when they first started to publish a lot of their
[1729.40 --> 1734.04] open data and whatnot they're leading the way in a lot of ways for local governments to do that kind
[1734.04 --> 1740.68] of stuff and then what you mentioned too about just documentation and then twitter bootstrap and other
[1740.68 --> 1746.68] sites that are kind of put out there and they're open right like even even your site your your blog is
[1746.68 --> 1751.80] open on github it's you know it's it's kind of like it just seems like a natural thing and it only
[1751.80 --> 1757.96] helps uh bootstrap and bolster this open open source ecosystem we all kind of desire to be in
[1758.76 --> 1766.36] exactly and one of the main tenants of of jekyll um has always been to to as much as possible and
[1766.36 --> 1772.52] github pages helps with this tremendously as much as possible open source your website um yeah let let
[1772.52 --> 1778.68] other people learn from it there's a great uh page on the wiki the jekyll wiki called sites and it we
[1778.68 --> 1784.60] have this one one rule you post the link to your site but you must post the source for your site as
[1784.60 --> 1789.00] well so if your sort if your site isn't open source it can't be on the sites page and there's something
[1789.00 --> 1795.00] like a thousand almost a thousand um sites with their sources linked directly next to the to where the
[1795.00 --> 1800.36] page is so if you go to see a site that you really like then the source is right there for you to look
[1800.36 --> 1806.44] at um so it's a great learning learning tool and anyone who has a site anyone who has a github
[1806.44 --> 1814.20] account can edit it so it's it the the jekyll community has been hugely a huge proponent i guess
[1814.20 --> 1819.08] of open source and making sure that they can learn from each other the way that open source champions
[1820.20 --> 1825.96] before we uh i guess before we turn away from i guess maybe newer topics more topics
[1825.96 --> 1830.84] uh i want to ask you a bit more detail if you can share it about the conversation that ben
[1831.32 --> 1837.24] had with you when he kind of enlightened you about the overarching ecosystem of jekyll like
[1837.24 --> 1840.84] what was that conversation what were some of the things he kind of fed you to help you really get
[1840.84 --> 1844.12] the aha moment and and kind of be able to tackle what you've done
[1846.12 --> 1851.96] the so it's been sort of an ongoing conversation it's it's you know comments here and there in in
[1851.96 --> 1859.08] the github pages repo and on jekyll um as well as at that nano summit but the the overarching or
[1859.08 --> 1867.08] sort of the aha moment that i had was um when when ben said two things two things that i really i
[1867.08 --> 1871.88] really cared about one was um be the pull request that you want to see in the world which is really
[1871.88 --> 1877.08] cliche but really awesome and goes along with the um let's make jekyll the coolest thing that that
[1877.08 --> 1883.16] it can be not because we want it but because everyone wants it um and and because everyone
[1883.16 --> 1888.60] can contribute to it if they if they wish um and the second thing is make it as simple as possible
[1888.60 --> 1896.04] absorb complexity as much as possible that is that is the way to a good product um and that i've sort
[1896.04 --> 1902.36] of you know github itself um the organization and all of its employees champion that that concept
[1902.36 --> 1906.36] if you're not you don't make your your user interface simple if you don't make the process
[1906.36 --> 1910.20] simple then people aren't going to use it people aren't going to do do what you're asking them to do
[1910.84 --> 1915.88] so um he's really molded this product into something that is as simple as possible
[1916.44 --> 1924.12] um and that's you know sort of where it's been an ongoing conversation but um sort of where we get that
[1924.12 --> 1931.96] that that heightened sense of simplicity from i guess since uh this might be a good time to talk about
[1932.36 --> 1937.80] um you know i guess earlier um i'm almost forget which month it is sometimes but i guess it's
[1937.80 --> 1942.20] earlier this month because it's it's the the last day of the month we're recording on may 30th by the
[1942.20 --> 1947.32] way um because the show doesn't always come out the same day we we actually record it but earlier this
[1947.32 --> 1955.80] month um you released um jekyll 2.0 but you know kind of flipping that on its head last year you were
[1955.80 --> 1963.72] releasing 1.0 a lot's changed you got a lot of newfound vision because of this history and and
[1963.72 --> 1969.48] all that what is what are some of the core things that change from jekyll 1.0 to jekyll 2.0 and then
[1969.48 --> 1974.84] also i guess to maybe make sure that the those who have been using jekyll for the last five years
[1974.84 --> 1982.36] don't have breaking sites right so to answer the first half the question what has changed um we
[1982.36 --> 1988.68] introduced a lot of things that that a lot of new concepts and a lot of um support for technologies
[1988.68 --> 1994.04] that people were using so the two main concepts that i really enjoyed working on and really enjoyed
[1994.04 --> 2001.16] uh releasing i was really excited to release were um collections and uh yaml front matter defaults
[2001.72 --> 2011.00] um so collections allow you to define a series of documents um all collected into one one entity as it
[2011.00 --> 2016.76] were um so one of the reasons or the reason that we originally wrote this um this feature was
[2016.76 --> 2024.52] actually because during the jekyll nano summit mislov said i'm writing for zepto the api documentation
[2024.52 --> 2031.72] i want to have one page per document or rather one page per method in the or function in the api
[2031.72 --> 2039.08] and i don't want to have to mangle jekyll you know monkey patch it up the wazoo in order to actually
[2039.08 --> 2047.40] write write write out individual pages for um for my um uh excuse me form for the api
[2048.44 --> 2055.72] and i don't want to mixing up the pages um or posts and i don't want to use posts for it etc etc
[2055.72 --> 2061.40] so he wanted a lot more customization um he wanted to be able to take the take the the documents and
[2062.20 --> 2068.60] import them into collection or into pages as well so include them um and write them out so he needed
[2068.60 --> 2074.44] them to be to some insurance to make sure that they were processed beforehand etc he wanted them to be
[2074.44 --> 2080.36] to be custom um he didn't want to necessarily have to have them write out as a file um so collections
[2080.36 --> 2088.12] natively or in the base most basic sense um you have a series of documents um that contain data yaml
[2088.12 --> 2095.80] front matter um and content and that's it um you can optionally set up um each individual document to
[2095.80 --> 2100.76] have an output file um that just goes into forward slash collection name forward slash document name
[2100.76 --> 2108.76] um and that will output an individual file if you want that um but the idea is is sort of data um
[2109.40 --> 2114.68] plus content mixed together in a nice way that isn't this isn't just yaml can you give an example of it
[2114.68 --> 2121.16] is that i'm thinking is it like if i were publishing a podcast so to speak would it be like a podcast is
[2121.16 --> 2125.88] that what you mean where it acts like a page or acts like a post does by normal traits but you kind
[2125.88 --> 2133.24] of give it its own name space and it's its own kind of model so to speak right so you use collections
[2133.24 --> 2137.32] for anything that isn't necessarily date sensitive although you can use dates and collections if you
[2137.32 --> 2146.28] want to um with when we were first setting up the jekyll site for example we had each docs docs page set up in as
[2146.28 --> 2153.72] a post it was just like 2010 01 01 here's my post uh or here's my docs page and we set it up as a post
[2153.72 --> 2158.84] because we wanted to make sure it was processed before the pages write them out into pages etc um
[2158.84 --> 2166.84] and have an individual an individual html file generated for each docs page as well so when we were
[2166.84 --> 2173.24] doing that it it was creating a collection of items but in the only only collection that we had which was
[2173.24 --> 2179.32] posts um you can think of posts as a date centric collection okay um of of documents and each document
[2179.32 --> 2185.96] is called a post in that case um so what we wanted to do is take that idea and generalize it not make
[2185.96 --> 2193.16] it so date centric people were kept asking hey can we remove the dates from our posts of course in a in
[2193.16 --> 2199.80] in a blog you every post should have a date um that's the point of a blog it's it's a chronologically
[2199.80 --> 2205.96] ordered um series of content so we said well if we're not going to take dates out of out of posts
[2205.96 --> 2214.52] let's you know create some more generalized concept um that's based on posts but um allows you to um
[2215.16 --> 2222.28] to collect various items um and write them out to individual files or just just have that data um so