text stringlengths 0 1.17k |
|---|
[386.24 --> 386.58] It's great. |
[386.58 --> 394.28] It's great to be able to check stuff into Git and, um, you know, and even deploy, uh, through |
[394.28 --> 396.44] Git on like Heroku or something like that. |
[396.44 --> 402.36] Um, so, um, yeah, I mean, I would love to update it. |
[402.58 --> 407.20] Uh, there was a lot of work that went into it when we went, when I first worked on it, |
[407.56 --> 408.10] pushed it out. |
[408.16 --> 411.00] I think there was, I worked on it like eight months, almost solid. |
[412.00 --> 417.54] Um, and I just don't have that kind of time to devote to it anymore. |
[417.54 --> 425.82] Um, at this point, uh, Jim Gay, uh, shout out to him, uh, Saturn Flyer on, on Twitter. |
[426.44 --> 433.64] Uh, has been maintaining Radiant for a number of years and has done a great job, uh, at it. |
[433.72 --> 438.30] So I'm very content to let him lead the, lead the charge with that. |
[438.30 --> 446.60] And Jim, um, actually runs kind of a consult, a web consultancy and is building sites every |
[446.60 --> 447.74] day with Radiant CMS. |
[448.28 --> 453.54] So I think he's the right guy to, um, to work on it. |
[453.54 --> 459.60] I think one of the things that was hard for me was after I created Radiant, um, I ended |
[459.60 --> 464.56] up not do, not building a lot of content oriented websites. |
[464.56 --> 468.54] Instead, I, my career sort of went towards web applications. |
[468.54 --> 469.82] It's kind of funny how that works out, right? |
[470.34 --> 471.34] Applications in general. |
[471.34 --> 476.64] And so, yeah, there's times when I feel like I'm kind of isolated for that problem space. |
[476.64 --> 480.88] Um, you know, I, I don't understand it as well. |
[481.02 --> 481.26] Yeah. |
[482.36 --> 485.78] What's a good tee up for what we've done with the SAS with us. |
[485.78 --> 494.00] The SAS way started out as a, as a Nesta CMS, which is a Ruby, um, file based, I guess is |
[494.00 --> 496.58] the probably easiest way to say it is a static site. |
[496.58 --> 501.70] Uh, I don't think Nesta has, I think it might have that feature, but it's not, it's not |
[501.70 --> 503.40] meant to be a generator. |
[503.54 --> 507.48] It's meant to be basically a flat file based CMS written in Ruby. |
[508.04 --> 508.44] Right. |
[508.90 --> 512.10] Um, and that was a great project. |
[512.18 --> 513.76] It's, it's what helped lift it off the ground. |
[513.86 --> 518.82] You know, we, you and I were able to easily, uh, tee that up pretty quickly. |
[518.82 --> 523.92] We did deploy to Heroku's, you know, super fast cause we took, you know, we took advantage |
[523.92 --> 528.28] of like varnish and caching and other things that Heroku provides and all the other things |
[528.28 --> 532.30] that just a, a flat file system kind of CMS provides. |
[532.30 --> 538.36] But, um, here about three weeks ago, we took this turn to, to finally, I mean, like we said, |
[538.40 --> 543.88] the site's been out there for almost, almost three years and we, our original model was |
[543.88 --> 550.48] kind of to, you know, go out to the SAS world and sort of recruit those that were, uh, for |
[550.48 --> 555.04] lack of better terms, movers and shakers, people that were sharing, you know, their knowledge |
[555.04 --> 558.96] with the SAS community on how to best write CSS the SAS way. |
[560.08 --> 565.40] And, uh, you and I talked, I would say probably like eight months ago about open sourcing the |
[565.40 --> 570.36] SAS way and oddly enough, and I'll come clean, but I felt a little apprehensive about doing it. |
[570.38 --> 573.86] I don't know why, but, uh, I'm really glad you forced us to do it. |
[573.88 --> 580.38] Because I think it's really a much better fit for, um, for the content the way it is. |
[580.38 --> 586.30] So why don't, why don't you share with the listeners why you feel passionate about how the |
[586.30 --> 592.30] SAS way meets up with this get flow, kind of check your content into get kind of mentality, |
[592.38 --> 595.30] this sort of open publishing way of, of doing things. |
[595.30 --> 597.12] Yeah. |
[597.22 --> 604.30] I, um, I mean, I think part of it for me, uh, has just been over the last couple of years |
[604.30 --> 609.60] getting more and more familiar with the way GitHub works with, uh, pull requests and all |
[609.60 --> 609.92] that. |
[610.00 --> 615.48] Um, I mean, we were passionate users of get at user voice and probably about every other |
[615.48 --> 616.60] company these days. |
[616.60 --> 624.86] And that, uh, that workflow of just being able to work on a change, push it into a branch, |
[624.86 --> 632.10] uh, ask for people to review it, comment on it, whatever merge, uh, just seems ideal for, |
[632.10 --> 637.44] uh, you know, building text-based documents. |
[637.44 --> 646.84] I guess you could say, um, I, you know, what, one aspect of it too is where a blog about HTML, |
[646.84 --> 652.46] um, and CSS and, um, you know, SAS. |
[652.46 --> 663.28] And so like having the ability to quickly drop in and write, write that kind of code alongside |
[663.28 --> 666.56] writing code for an article, uh, is pretty awesome. |
[667.52 --> 676.72] Um, so I, I mean, in general, the fact that it is a, uh, uh, static file based content management |
[676.72 --> 680.10] system, uh, it's all checked in on there on GitHub. |
[680.42 --> 686.20] It means it's a lot easier for people to come alongside and submit new articles. |
[686.88 --> 692.66] Um, also, uh, make changes, fix things on the site if it's not displaying correctly. |
[693.28 --> 699.62] Um, and really, I think that the big thing that I love about this is, is that we've reversed |
[699.62 --> 705.90] the, um, trying to go out and recruit people kind of scenario, which we still try and recruit |
[705.90 --> 712.72] people to write stuff on the SAS way to, to it, it being also something where people can |
[712.72 --> 716.90] come to us and say, Hey, I have an article idea, an idea for this article. |
[717.32 --> 718.22] What would you think? |
[718.26 --> 722.68] And then they fork the repository, they write it up and send us a pull request. |
[722.68 --> 731.60] And, um, you know, we, we've had, uh, two articles, I guess, since we, uh, opened it up this |
[731.60 --> 731.94] way. |
[731.94 --> 740.10] And, uh, it, uh, you know, these are from people that we didn't know about and, um, they've |
[740.10 --> 745.98] worked out to be fantastic articles for us filling, you know, some holes, uh, in, in what |
[745.98 --> 746.32] we had. |
[746.32 --> 750.52] And so one of the things that I've struggled with too, is, is that sometimes you really |
[750.52 --> 756.72] need an article on a topic, but one of your go-to people, I guess, is not like, doesn't |
[756.72 --> 757.98] really want to write about that. |
[757.98 --> 769.76] Um, and so really freeing up, uh, just for anybody to be able to contribute to it has |
[769.76 --> 772.54] been, I think a very good thing for the SAS way. |
[772.90 --> 772.96] Yeah. |
[773.08 --> 779.86] I mean, considering that SAS and compass, um, and I guess the SAS world is, is known to be, |
[779.86 --> 782.04] you know, it's their open source technologies. |
[782.04 --> 788.16] Anyways, it would make sense to, and this is why I said, I self-admitted that, uh, that |
[788.16 --> 789.74] I was sort of the bottleneck. |
[789.74 --> 793.70] I mean, it's kind of funny too, that the fact that, you know, I helped lead the changelog |
[793.70 --> 797.84] who, uh, you know, focuses on, uh, what's fresh and new and open source. |
[797.84 --> 802.36] And here I am being a little apprehensive about opening up this publishing flow just because |
[802.36 --> 804.30] I think part of me doesn't want to lose control. |
[804.30 --> 808.82] But then I, I learned something along this path that I realized that wasn't really control |
[808.82 --> 810.74] we were trying to achieve. |
[810.74 --> 812.98] It was, it was really, uh, openness. |
[812.98 --> 819.10] And I think the last probably, you know, a few weeks I've really changed my, uh, idea |
[819.10 --> 824.94] because I've been closely involved in this project being open source and kind of, um, helping |
[824.94 --> 827.34] curate this content and manage it. |
[827.34 --> 831.54] It's, it's, I can see now the light, so to speak. |
[831.90 --> 832.42] Yeah. |
[832.54 --> 833.62] By having it open. |
[833.70 --> 838.24] So like you said, it's, it's really easy for someone to, to forth a repository and, you |
[838.24 --> 841.24] know, don't worry about messing up. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.