Google Code is nifty
01 Dec 2006Just found a cool bit of code through Google (I searched) on Google (Code), and then checked it out in a matter of seconds using SVN. The whole operation took under five minutes.
I’ve delivered simple, clear and easy-to-use services for 20 years, for startups, scaleups and government. I write about the nerdy bits here.
— @joahua
Just found a cool bit of code through Google (I searched) on Google (Code), and then checked it out in a matter of seconds using SVN. The whole operation took under five minutes.
I’m employed by an organisation (the one I referred to in my first post about this project, wherein I didn’t bother explaining exactly what was going on, but hoped it would be clear to those who already knew) that exists to — amongst other things — resource youth ministry.
One thing we’ve noticed (“we” is myself and a handful of others with an interest in the web) over the past twelve months is an uptake in web usage by youth ministries — for obvious reasons: that’s where kids are spending their time, and it’s a great communication tool, and everyone else is doing it.
When I say everyone else is doing it, I actually mean everyone else is trying to do it. Everyone has, for the last six to twelve months, been writing the same applications, integrating the same software, paying for the same software, attempting to train the same people, and generally doing a lot of the same stuff, separately. With no point of intersection or sharing or intelligent resource management.
This is understandable: afterall, the web presents a relatively new front for churches in general, and whilst kids have been wasting time online for years, only with the relatively recent advent of social networking websites (I refer to it as ‘SocNet’ in these parts — no-one else seems to, but I like it, so whatever) have the less computer-inclined began spending significant amounts of time in front of a keyboard.
There’s also a bit of a catch-22 when it comes to building these things. People ask, what are the benefits? We’ve never had someone come along to youth group because of our website! — well, no, you’re right. But you also don’t have a website, so that’s hardly fair, is it? Nine times out of ten people will not come along to church (generically) because they’ve searched for a church in a particular suburb in Google (though, speaking of that, I’ve got to do a bit of SEO work on the Matthias site — it’s not on the first page for a “Church in Paddington” query. Changed the title, it’ll be a while til that kicks in. We’ll see.)
They’ll come because a friend asked if they wanted to, or they were walking past and heard people inside, saw them going in, and wondered what it was all about.
But this is hardly exclusive to having a website. If they have those points of contact, a website is a great way to invisibly investigate further without needing to make themselves uncomfortable. It’s easy to find these sorts of websites through search engines — you walked past a church and noted its name, you remember the name of your friend’s church, etc.
The same goes for youth groups, obviously.
People have just been starting to realise this, or at least think of it at all and decide “yeah, we could do that”. So, there’s the rationale for it all. Most people with decent websites already may not have considered rationale in any great depth — they’ve got a good website because they know someone who makes them, and volunteered their time (maybe they’re a leader), throwing something together with Xoops in an afternoon. It’s quick and dirty, but effective.
We’re trying to spend a small but not insignificant amount of money to equip people to do these sorts of thing, so it’s only sensible that some more time is spent considering what on earth we’re trying to achieve. Hence the lengthy prelude to what it actually does.
Now, the features. We have too many target audiences for it to be an altogether comfortable project, but that’s half the fun of it. The product is being marketed to churches (who pay for it) through leaders (who want to use it) and for youth (who actually aren’t the centre of the universe on this one, but we need to give them UX that says they are). Outside of these three, there are also the friends of the youth already in the application who are just checking out the youth group page.
Of course, it’s not quite that simple. We’re also marketing this to camps, high school scripture groups/lunchtime bible groups, and maybe bands/events. Which is great and technically only a small step, but it does pretty horrible things when you try and explain who’s paying for what in a concise business-like fashion. If you’ve read this far, chances are you’re well aware that concise-ness has never been my strong point.
So, with these targets in mind, we are (firstly) going to equip them with websites. Big woop. WordPress.com and Blogger eat your heart out. Cue yawns.
No, seriously. We’re going to give them (‘them’ being the various entities described above, not individuals so much — there’s no way I’m positioning this against other SocNet sites because I reckon it’s too fragmented to last… Facebook or Myspace or Bebo or…. yes.) web pages. Welcome to 1999.
They’re going to have web pages with calendars they can chock full of the schedule for the term, though. So that’s exciting.
And everyone’s going to have their own username, so they can leave comments on the inevitable blogging element with identity — this is wonderful for comment- and generic form-spam. Incidentally, I read a few blogs that Wild St people are writing and was really excited to see they’re actually enthusiastic about doing it. There’s quite the bunch of them on Blogger these days, and it’s all completely autonomous — so far as I know, no-one has pushed them to start doing it. I was so proud of their keenness and innovation for building up community and spreading the gospel! Another aside, my copy hasn’t arrived yet but I believe there’s something about blogging in The Briefing for December (it’s not on their website yet, either). My copy arrived today, and I discovered the current issue is in their webstore, just not on the main site. It’s The Briefing #339, if you’d care to read it.
Anyway. Blogs will feature. Calendars will feature. All the stuff you’d reasonably expect to be able to do with a CMS tool these days will feature. Blogs, calendars, galleries, contact forms, static pages. Yay. So that’s the boring stuff that we’ve just got to do the grunt-work for at some point (I’m sure it can be fun, but, just between you and me, I’m not really looking forward to the couple of weeks we have to spend on that bit).
Now, for interesting and innovative features — because, let’s face it, the above is hardly enough to convince anyone to switch their existing website (if indeed they have one) across to a hosted platform for a nominal (to be determined, but probably only payable by church groups, and not for camps/events on account of these being once-off) monthly fee.
Contact tools. Yummy. We’re going to give them mailers that make it easy to send a message to, say, all the kids in year 10. Or just guys. Or girls in year 8. Or only to your co-leaders (we’ll have a resource area where they can share files — Word documents, PDFs, slide shows — on the site, too: that’s some of the fun CMS stuff). But email’s been done before. Everyone’s used email. Admittedly, sometimes you just wish there’s a better way to store and manage lists of people, and this tool will certainly do that, but it’s a little boring still.
So we decided it’d be a good idea to throw SMS into the mix. It’s not just a gimmick: again, this is in response to what people are already doing. The only difference is it’s paid on a shared account (used by the leaders — the youth kids won’t have access to these tools, for fairly obvious reasons) and integrates the same contact management features as the mailer app. We’re hoping convenience will draw people across to this tool. Use scenarios are basically just that you’d use this tool to inform people of what’s going on this week at youth group, or reminding them that the group is on bringing supper this month, etcetera. The originating number will be that of a single leader, or it could even be that of that person’s own leader.
For example, one message is sent to all kids by the group co-ordinator, but that message is altered depending on who the individual recipient’s bible study leader is, so that it appears to originate from them. Obviously common sense would say that you wouldn’t do that without consultation, so we’d probably have a check box in the leader’s “my account” page that would say “Allow messages from other senders to originate from my mobile number”, or something to that affect.
Beyond contact tools, we want to take advantage of the fact that this is a service-based product and entirely a hosted solution. Part of the reason we’re strongly pursuing that is it gives an opportunity to equip and direct in a way that decentralised sites can’t be. So, a few things we’re thinking of doing are centralised offerings like weekly newsletters (sent to leaders two days in advance so they’ve got an opportunity to see it first) and global blog properties that give reviews, current affairs commentary, etc.
That’s the end of the universal features that are great for kids and leaders alike, but there’s lots more for leaders. As I’ve already said, we want this to be self-funding. Part of this is selling electronic versions of dead-tree products, as DRM’d PDFs, or as unencumbered PDFs with watermarks/obviously time-sensitive advertising (so violation of copyright is glaringly obvious). The other part is (for me at least) far more exciting, and that’s reselling user generated/contributed content (UGC) under an iStockPhoto-esque model (Basically, profit sharing).
This isn’t just about words on a page — I want to get plenty of video stuff happening, too, because (especially in reformed evangelical Anglican/Baptist/Presbyterian, etc. churches) that doesn’t get nearly enough of a work out as is. It’s a really effective tool for supporting preaching/bible studies, and it’s been largely overlooked until probably early this year (I had my first conversation with someone about video resources for small group bible studies as late as July or August this year, I think! They had used a Matthias Media resource which I haven’t encountered, and thought it really helpful).
Pricing models for all that are still a little up in the air, but, from a consumer’s point of view, it’s definitely going to be affordable. The project will ultimately sit on a server maintained gratis and depend largely on volunteer labour to administer content. The only “costs” are those to the established Youthworks publishing division, but hopefully we can transition the way they do their high-school level content effectively, so they’re commissioning content for the web and selling it there. Something that’s really exciting is the possibility that, instead of commissioning content, it’s possible to purchase it directly and already created from a pool of resources on the website.
There’s definitely a workable model here, somewhere.
Prayer is greatly welcomed for:
I always thought the script.aculo.us drag’n’drop-shop demo was stupid. It seemed illogical and only really practical for stupid puncy little shops with five or ten products – certainly, with everything listed on the same page.
Then it hit me — this is perfect for shuffling documents around. CYIADA (see-uh-da), is (partially) about selling documents and resources electronically — and it does that with pre-paid credits. This, of course, means that there doesn’t have to be any cumbersome checkout stage. Better than Shopify (excellent though that is), potentially.
Drag documents you like when browsing into a floating “My Resources” bin on the side of the page, AJAX is used to throw up a “confirm purchase” DIV which presents simple “yes”/”oops” options, and keep moving. It’d be trivial to modify the confirm view to have a “purchase for my whole group” checkbox (which would, of course, change the cost), too. Anything beyond that might be too complex.
Of course, there would be graceful degradation for those without JavaScript turned on… because someone has to ruin the party :P
You can run Django in IronPython under .Net. Awesome. A Windows-based server is suddenly a choice again, which is… fantastic. Mostly for piping documents through MS Office products for indexing and PDF generation, because OO.o is great with Word docs but not so great — font sizing issues, etc. — with other things, especially PowerPoint, which could account for up to a quarter of the content contributed by users, I’d say. So I can run native MS Office -> PostScript export -> ps2pdf processes, and MS Office -> Horrible XML -> Scrub markup filters -> Search index, without having to battle with Wine, etc.
Of course, the second process would probably benefit from using OO.o as a processing environment, but that’s equally achievable on a Windows or *nix platform.
So many fears about platform (OS and language) have been sufficiently allayed. Which is kind of annoying, because, all of a sudden, .Net is actually an option. I’m still confused over databases though, so there’s plenty of befuddlement to go around. Ultimately it doesn’t matter a great deal if we find the right developer (for whatever language… except obscure things like Smalltalk and Ruby … oh did I say that? … doo be doo — just for future-proofing/maintenance reasons), which, hopefully, we will. Another meeting about money for this thing is happening on December 13th, so prayer is very welcome for that! I want $35,000 to spend over about two and a half months to pay one other developer and outsource design, as well as myself, of course (the front-end dude). By the end of that time we’ll hopefully have an absolutely fantastic solution that will magically propel (not that I really want to use Propel, because that’s for PHP ;-)) itself forever… yeah, right.
We’ve got a half-baked business plan for this thing (by half-baked, I mean it’s all stuff I’ve written and the real gurus haven’t had anything to do with the numbers, etc., so it’s not really authorative) that should get it out of the red by a couple of months in (which is ridiculously quick… another reason to think it’s half-baked) and allow for cleaning up all the bits we missed in the hectic two and a bit months it was originally thrown together in, but, at the same time, it’s going to be partially dependent on licensed, published (dead tree) content (i.e. not just user-contributed stuff, which, longer term, will hopefully account for the bulk of sales — the profit margin is lower, but it’s also easier to move more units because of the sheer scope of content we’re hoping will be available) — so because we’re licensing that revenue is going to be eaten into by publishing division and other content sources.
All of that is, of course, dependent on people wanting to use these things (they do, but from there it’s a question of making the product known to them and making adoption easy) and being okay with sharing stuff they’ve written. Some knee-jerk reactions have been negative to that, but the objections were accompanied by acknowledgement of a need to think more about what sharing content is doing — that is, why we’re bothering to create this site anyway.
Which, I have realised, I have not shared here yet. I want to write it another time because I think I’m getting clearer at explaining what we’re trying to do every time I try, so it’s no bad thing repeating myself. Here’s a brief overview of what Josh does (or, is trying to do) at Youthworks.
Just for kicks I decided to walk in to work today (my weekly bus ticket ran out and that’s as good an excuse as any). Took me pretty much dead on an hour to get here, which is quite a decent time spent in transit. I’d be half an hour to 40 minutes were I to catch a bus (once you count waiting time, etc.) so it’s really not that bad at all. Might try and make this a regular occurrence.