text
stringlengths
0
1.17k
[3387.36 --> 3393.84] or you know bare bones skeleton sort of site um but if you're if you're looking for like if you're
[3393.84 --> 3398.98] some erlang programmer or something and you just you don't have the time to set up a ui you don't
[3398.98 --> 3404.90] want to write any html you just want to write what like write a blog post about something um then
[3404.90 --> 3412.04] all that you have to do is clone down the repo run rake install run rake new posts and then give it a
[3412.04 --> 3418.54] title and then boom you're off um and it's the coolest thing um it handles new posts new pages
[3418.54 --> 3426.44] deployments um previewing generation all of that stuff um one of the key points as well is that it
[3426.44 --> 3432.16] it has this one one task called rake isolate and one of the the points that you mentioned earlier
[3432.16 --> 3439.00] about jekyll um is or i guess that we talked about at uh briefly um was this idea of incremental
[3439.00 --> 3445.00] regeneration right now jekyll just says i'm gonna when you run jekyll generate or jekyll build rather
[3445.00 --> 3449.96] it just takes your whole site and rebuilds it um and that's not that efficient um especially if
[3449.96 --> 3458.28] it's the same in 98 of the files so um if you have a massive site maybe of like 1200 posts or something
[3458.28 --> 3463.80] you've been writing for a long time um i know matt gemmel uses octopress and he has you know i think
[3463.80 --> 3468.08] close to a thousand posts or he did you know a couple months ago um i'm sure he has over a thousand
[3468.08 --> 3474.00] posts now um he's a great writer but it just took so long for those posts for that site to regenerate
[3474.00 --> 3479.46] that he said you know i can't do this so um octopress gives him the tool called rake isolate which gets
[3479.46 --> 3486.18] rid of all the posts except for the one that he's working on and basically just regenerates that one
[3486.18 --> 3492.22] um the entire site but just with that one post so it removes the 999 other posts that he doesn't
[3492.22 --> 3497.36] need to be looking at because he's not working on it right now um and then you um you run rake
[3497.36 --> 3502.00] integrate and it puts all the posts back and then you run rake gen deploy and he deploys a whole new
[3502.00 --> 3506.34] thing once it's once it's done so is that using git magic to do that or is that how's that working
[3506.34 --> 3512.70] rake isolate um basically just takes it takes all the posts except for the one that you're working on
[3512.70 --> 3519.54] moves it into a separate directory um that jekyll won't look at and then runs jekyll build or jekyll
[3519.54 --> 3523.68] served depending on what you're doing so it all that it does is it just moves the files
[3523.68 --> 3528.38] um and then moves it back when you run rake integrate right right it's it's it's an amazing
[3528.38 --> 3534.64] idea um and it's such it's so so you know dead simple that it's surprising that that no one else
[3534.64 --> 3540.26] has done it but that's sort of a unique piece to to octopress so octopress is sort of this framework
[3540.26 --> 3544.92] that makes blogging with jekyll or writing sites with jekyll as easy as possible and gives you the
[3544.92 --> 3553.44] the ui or the uh the site um uh theme and all this stuff to work with immediately did the projects
[3553.44 --> 3560.66] so it's it's almost um even still now even after hearing that it's still hard to really see
[3560.66 --> 3567.32] where they you know where they separate i understand that it's kind of built on top of
[3567.32 --> 3571.88] jekyll but is it a point that they'll ever merge they'll ever share the same functionality
[3571.88 --> 3577.22] or essentially tackle the same kinds of problems or is that the reason why you're involved in both
[3577.22 --> 3582.44] projects kind of help keep them in parallel and keep them kind of working together well
[3582.44 --> 3588.38] i'm definitely i'm definitely involved with both um in order to make sure that they're going along
[3588.38 --> 3593.82] parallel in in parallel um i'm way more involved in jekyll just because jekyll has no i mean matt's
[3593.82 --> 3600.32] working on it as well but matt's um matt's really busy so um i'm the one that's sort of taking care of
[3600.32 --> 3606.04] of the immediate day-to-day sort of stuff with jekyll um and because no one else is doing that i'm sort
[3606.04 --> 3611.32] of taking more of a back seat or more of an advisory role i guess um i look over pull requests that
[3611.32 --> 3619.62] that brandon puts up on octopress repos um and helping with problems as needed um but in terms
[3619.62 --> 3625.80] of the future there's definitely the possibility that they would merge um the octopress as we know
[3625.80 --> 3631.98] it today would not be the octopress of tomorrow in any sense um brandon's doing amazing work um on
[3631.98 --> 3637.98] the octopress organization on github and you can take a look at um where he's taking octopress and
[3637.98 --> 3642.96] splitting it off into a gem and this gem is just about functionality it's just about sort of
[3642.96 --> 3650.06] extending the basic jekyll generation stuff into um generating new posts based on like erb templates
[3650.06 --> 3655.80] that sort of thing um and he also created something which i'm really excited about called octopress inc
[3655.80 --> 3662.92] um and octopress inc is is an extension to jekyll that allows you to to write isolated themes
[3662.92 --> 3668.44] so i have a gem for example called i don't know parker's site or parker's theme or something
[3668.44 --> 3674.22] and i can publish that on ruby gems and you can say gem install parker's site or parker's theme or
[3674.22 --> 3679.68] whatever and use and it uses octopress inc such that when jekyll says all right i'm going to go
[3679.68 --> 3686.06] build this site um it uses the css the javascript that i've written um and it's it's all separate from
[3686.06 --> 3692.64] my own content files so what octopress inc has done is basically taken the concept of wordpress themes
[3692.64 --> 3698.56] where the theme and the content are completely separate um and applied that to static site
[3698.56 --> 3703.98] generation as jekyll knows it so i'm sort of i'm sort of there to to make sure that everything's
[3703.98 --> 3708.62] going along at the same time and to help with like the jekyll 2.0 major bump for example that's a
[3708.62 --> 3712.24] fantastic teaser for an upcoming conversation i'm sure we'll have with brandon i know that
[3712.24 --> 3718.56] i mean anytime we ever mention and i try to get brandon to share as much as he can but i know he's it's
[3718.56 --> 3723.26] he's been so close to 3.0 for a while now and i know that a lot of the listeners and a lot of the
[3723.26 --> 3729.24] readers of our weekly email and and the blog and anytime we publish any sort of teaser of the upcoming
[3729.24 --> 3734.06] octopress 3.0 they're always like all over it you know everybody's like waiting with bated breath kind
[3734.06 --> 3738.84] of so to speak so i'm sure that that was a perfect teaser for to tee it up for brandon when he comes on
[3738.84 --> 3745.58] the on the show um i guess let's go ahead and tail off the call then i know there's probably
[3745.58 --> 3750.34] i know you got things you got to do and we could talk probably for days but because you do a lot of
[3750.34 --> 3758.06] cool stuff but let's let's um let's talk about the future of of jekyll let's tail into that and i think
[3758.06 --> 3762.98] you kind of know where i'm going with it but where is jekyll going how does it align with github pages how
[3762.98 --> 3769.50] does it align with github uh github pages api what can you tell us about uh not just jekyll 2.0 which
[3769.50 --> 3775.48] came out early this month but the the future and beyond that's a really awesome question um the
[3775.48 --> 3783.04] future of jekyll is is the simplest but also simultaneously most powerful static site generator
[3783.04 --> 3792.94] that you can find um for for anyone um isolating isolating it from um the expectation that
[3792.94 --> 3800.56] you must know ruby is is paramount to that objective um the jekyll of tomorrow is a jekyll that
[3800.56 --> 3808.20] is is easy to install um is really easy to use um doesn't hopefully has as few bugs as possible
[3808.20 --> 3815.50] if none or if not none rather um and and does the really amazing things like incremental regeneration
[3815.50 --> 3825.08] and has themes um the way that octopress inc act price inc um displays them um and in order to get
[3825.08 --> 3831.72] there we just need a lot more manpower um we just need people who are interested in in taking a stake
[3831.72 --> 3837.32] in jekyll and saying this is a really cool project um let's make it what i want it to be um and when
[3837.32 --> 3842.54] they hit a pain point to say yeah i could write a plug-in for this that monkey patches jekyll to the
[3842.54 --> 3847.86] you know how i want it but why don't i take that change and contribute it upstream and see if
[3847.86 --> 3854.78] they're interested um and to to sort of have that constant conversation with how am i using jekyll
[3854.78 --> 3860.82] and how is jekyll right now um is sort of what's gonna what's gonna push jekyll forward that might uh
[3860.82 --> 3865.48] that might lead us right into the call to arms i guess for for jekyll because one of the things we
[3865.48 --> 3871.54] ask on this show is some some decent questions at the end that's our common questions i guess um but we
[3871.54 --> 3875.40] always ask you know what's the call to arms how can the community step up and help out so maybe you
[3875.40 --> 3881.20] kind of mentioned it but maybe you can kind of go a little deeper yeah so the the way that we would
[3881.20 --> 3886.26] love for you to get involved is is to be involved in the conversation the issues there's an irc channel
[3886.26 --> 3895.22] um pound jekyll there is um there's so much available um there's also a jekyll dash help repo um so if
[3895.22 --> 3900.54] you're if you're if you find that you have an extra even 10 minutes a day to watch that repo and
[3900.54 --> 3905.76] answer questions to help with the ecosystem or the the users who are are struggling with this or
[3905.76 --> 3911.48] you know hey i installed jekyll but i can't seem to get this to work can you help me yeah sure let me
[3911.48 --> 3916.10] just take a quick look at your repo most jekyll problems are diagnosable you know in five minutes
[3916.10 --> 3923.68] um unless it's some crazy issue with you know your gem environment or something so um to be to be
[3923.68 --> 3930.08] involved and to do what you can to um either contribute code um or contribute ideas just open
[3930.08 --> 3934.14] an issue that's like hey this is a really cool idea that i had when i was just writing my site
[3934.14 --> 3939.60] what do you think about it um and then we can discuss it um to you know involve your friends
[3939.60 --> 3945.24] maybe uh if you have a if you have a pal who's also using jekyll or a colleague to have them you know
[3945.24 --> 3949.68] get a github profile they don't already and contribute their ideas um to be part of the
[3949.68 --> 3954.48] conversation um there's obviously no way that you're you're going to be involved if you aren't
[3954.48 --> 3959.30] a part if you aren't a part of it but um it's relatively easy to just watch the repo i promise
[3959.30 --> 3967.84] like maybe 12 to 15 notifications a day i try to stay uh busy but but not too overwhelming um
[3967.84 --> 3975.54] so you know just sort of contribute where you want to where you can um of course triaging issues is
[3975.54 --> 3980.70] super helpful but i handle every issue that comes through um so you're pretty active i was always
[3980.70 --> 3986.48] when i was just kind of prepping for this conversation i was like wow you are on on the