Daniel Villar has been on fire with the SPLOTs. Not only did he invite me for a workshop last month in Coventry University (and that site is a SPLOT), where we got pre-made versions of them available on Conventry.domains, he recently put three different ones into play for his new OWLTEH project.
Beyond this, Daniel has provided a bunch of good ideas that have recently made their way into several themes.
If you are ready to bail on the first paragraph because I just launched into SPLOTs, I have a SPLOT that explains SPLOTs.
I know of these because he tweeted them.
I want you to… SHOW US THE SPLOTS!
You see, I try to keep a list of example sites people have made with these; it shows the range of ideas people come up with, plus it helps to show that other people have made them.
On each Github repo for these themes I have a section in the ReadMe called something like See It In Action, for example over at the TRU Collector:
Once you scrape past the shroud of confusion of Github, the beautiful thing about it is that it’s a collaborative editing space as much as Google Docs is. I have a sentence below the list:
If you make a TRU Collector site, please please pretty please, fork this repo to edit this Readme with a link to your new site.
But I think maybe that Grant Potter is the only person who actually did this.
So I aim here to show you how easy it is. You will Fork a Repo and then brag about it.
You will need a free GitHub account (I just made one for my dog to make sure I explained this correctly), its also useful for reporting issues, problems, offering feature requests. Or just sating hi.
If Felix can do Github, why not you?
Okay, so let’s say Felix has made a new site from the Splotbox theme, and he wants to share it as an example. Good Dog.
Hovering over the pencil icon (he knows that means edit, not chew), you see that it is labeled “fork and edit”:
What forking means is that it takes an entire copy of the theme from my repo and puts a copy into yours. You make changes, and then send them back to me. I then accept them into the official site.
Then he finds the place in the Markdown code for the examples. Okay, this may look scary, but all you need to do is copy the other examples.
The * in front means its a list item and then the
[label](http://somecoolurl.oeg/splot) is how you add a link.
This took Felix about 3 minutes:
The box at the top helps the repo owner (me) understand what changes are being proposed.
If your Markdown looks good, I can add it to the public repo just by accepting the changes.
It looks and sounds more complicated than it really is, but it’s all about distributed editing and managing versions in a way much more efficient than shoving around email attachments.
If this still makes you scream in horror, there’s another simple way, and that’s just to send me a link by opening an issue, it’s more or less like writing a blog comment.
But forking and proposing changes in Github will get you some code cred, eh? Just like Felix.