[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"projects":3,"site-tour-tonepath":56},[4,20,31,42],{"slug":5,"name":6,"tagline":7,"summary":8,"body":9,"stack":10,"href":16,"sourceUrl":17,"logo":18,"hasCaseStudy":19},"computravel","Computravel","South African travel platform, rebuilt end to end.","A Nuxt + Directus catalogue for holidays and day tours, with search that lives in the URL, editor-authored campaigns, and a deployment pipeline.","\u003Ch3>The problem\u003C\u002Fh3>\u003Cp>Computravel's old site was a PHP build that had fallen behind: a dated brand, no live package data, and pages the team couldn't easily update. They needed a rebrand, holiday packages fed straight from the Thompsons travel API, and a site their own staff could run.\u003C\u002Fp>\u003Ch3>What I built\u003C\u002Fh3>\u003Cp>I rebuilt it end to end, as the only developer: a Nuxt front end, a Directus back end the team edits themselves, and the integration that turns Thompsons' package feed into destinations, day tours and holiday pages organised by place rather than by the supplier's own schema. Visitors search by destination, category and price, and send an enquiry from any package.\u003C\u002Fp>\u003Ch3>How it works\u003C\u002Fh3>\u003Cp>The Nuxt server sits in front of everything: it shapes Directus data for each page, caches the rendered pages and purges them when content changes, and serves pictures through Cloudflare's CDN. Search lives in the URL, so any set of results can be shared or bookmarked. Every change ships through a pipeline that migrates the database, rebuilds and smoke-tests on a self-hosted runner.\u003C\u002Fp>\u003Ch3>Where it is now\u003C\u002Fh3>\u003Cp>Live at computravel.co.za, and I still maintain it. The full story, from the confusing supplier data to the caching that fixed its performance, is in the \u003Ca href=\"\u002Fcase-study\u002Fcomputravel\">Computravel case study\u003C\u002Fa>, and the stack choice is in \u003Ca href=\"\u002Fblog\u002Fwhy-nuxt-and-directus\">Nuxt and Directus for a client site: why I chose them\u003C\u002Fa>.\u003C\u002Fp>",[11,12,13,14,15],"nuxt.js","directus","postgres","docker","github actions","https:\u002F\u002Fcomputravel.co.za",null,"\u002Fimages\u002Fprojects\u002Flogos\u002Fcomputravel.png",true,{"slug":21,"name":22,"tagline":23,"summary":24,"body":25,"stack":26,"href":28,"sourceUrl":17,"logo":29,"hasCaseStudy":30},"yearcrest","Yearcrest","Unique circular calendars and year planners, printed and framed as wall art, or for a display screen","A place to design Yearcrests. Create a symbol of your family, your team's story, or your year to come. \nOr make a useful and pretty leave calendar for your team.\nPrint and frame in glorious high resolution, or share a live link for a display screen for the foyer.\nBring in your calendar data from google, and add beautiful photos of your choosing. Plenty of presets to use for text and colors.\nAlso, bring in your team's season and make a crest from that. The live link will add results as they come in.\nMany more use cases.","\u003Ch3>The problem\u003C\u002Fh3>\u003Cp>Calendars and planners are usually grids: practical, but nothing you'd frame. Yearcrest started from the idea that a year (a family's birthdays, a school's terms, a team's season) could be drawn as one circular design, good enough to hang on a wall or show on a screen in a foyer.\u003C\u002Fp>\u003Ch3>What I built\u003C\u002Fh3>\u003Cp>Yearcrest is my own product, and I built all of it: a studio where a crest is designed in the browser, layer by layer, from templates or from scratch, using the dates you care about and a photograph of your own. Dates can come from a Google calendar, and a sports season's fixtures can be fetched for your team, with results filling in as they're played.\u003C\u002Fp>\u003Ch3>How it works\u003C\u002Fh3>\u003Cul>\u003Cli>\u003Cp>\u003Cstrong>Print and screen from one design.\u003C\u002Fstrong> A crest is drawn in fixed drawing units and scaled to any frame, so the same design prints sharp at wall-art size or runs live on a display.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>A dedicated export service\u003C\u002Fstrong> renders print files in headless Chromium, so what's on paper matches what was previewed on screen.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Directus behind it, Nuxt in front:\u003C\u002Fstrong> the templates and content are managed in Directus, and the studio and site are a Nuxt app.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>A live display link\u003C\u002Fstrong> keeps a crest on a screen up to date, such as a season's results.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Packs, not subscriptions:\u003C\u002Fstrong> a crest is paid for once, for a year. [check: pricing wording you want public]\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Ch3>Where it is now\u003C\u002Fh3>\u003Cp>FInal QA stage, still locked to the public\u003C\u002Fp>",[12,11,27,14,13],"vue.js","https:\u002F\u002Fyearcrest.com","\u002Fimages\u002Fprojects\u002Flogos\u002Fyearcrest.png",false,{"slug":32,"name":32,"tagline":33,"summary":34,"body":35,"stack":36,"href":39,"sourceUrl":40,"logo":41,"hasCaseStudy":30},"publicdraw","a service for performing transparently fair random draws.","When opportunities or resources need to be distributed fairly amongst a group of people, this service solves that problem.\nExamples are music or sports event ticket allocation, or housing allocation in a suburban area.\nA user may sign up and create a draw. Other users then need to enter the draw before it takes place , as the 'operator' user should not be allowed to change the draw time after creating it. \n","\u003Ch3>The problem\u003C\u002Fh3>\u003Cp>When there are more people than places (tickets to a sold-out event, plots in a housing scheme, spots on a course), whoever runs the draw is asked to be trusted. Usually there's no way for anyone to check that the result wasn't steered, or that their entry was even in it.\u003C\u002Fp>\u003Ch3>What I built\u003C\u002Fh3>\u003Cp>Publicdraw is a service for random draws that the organiser can't steer and anyone can check. An organiser creates a draw and sets its cutoff, and can't move it afterwards; people enter before the cutoff; the result is drawn from randomness nobody controls. I designed and built it on my own, in Go, and it's open source.\u003C\u002Fp>\u003Ch3>How it works\u003C\u002Fh3>\u003Cul>\u003Cli>\u003Cp>\u003Cstrong>The entry list is committed before the randomness exists.\u003C\u002Fstrong> At the cutoff the list is fixed and published as a commitment, so it can't be changed once the result could be known.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>The randomness comes from a public beacon.\u003C\u002Fstrong> The result uses a round of drand, a randomness beacon run by independent organisations, so neither the organiser nor the service can choose it.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Anyone can verify a result in the browser,\u003C\u002Fstrong> against a pinned drand key: nothing is uploaded and no server is asked.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Entrants get a receipt\u003C\u002Fstrong> that proves they were in the committed list at their position, without revealing anyone else.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Every action is in a transparency log,\u003C\u002Fstrong> each record chained to the last, so editing or removing one breaks everything after it.\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Ch3>Where it is now\u003C\u002Fh3>\u003Cp>Live at publicdraw.truelathe.com, with its code public on GitHub.\u003C\u002Fp>",[37,38,11,27],"go","drand","https:\u002F\u002Fpublicdraw.truelathe.com","https:\u002F\u002Fgithub.com\u002Fsharkfin-909\u002Fpublicdraw","\u002Fimages\u002Fprojects\u002Flogos\u002Fpublicdraw.png",{"slug":43,"name":44,"tagline":45,"summary":46,"body":47,"stack":48,"href":53,"sourceUrl":54,"logo":55,"hasCaseStudy":30},"tonepath","Tonepath","Music Improvisation Study Tool","A browser app that allows musicians to explore chords and scales via a hexagonal pattern grid. ","\u003Cp>\u003Cstrong>The problem\u003C\u002Fstrong>\u003C\u002Fp>\u003Cp>Improvising over chord changes means knowing, at every bar, which notes belong to the chord and its scale, and how to move between them. Most practice tools show a keyboard or a fretboard, which hide the patterns those notes make.\u003C\u002Fp>\u003Cp>\u003Cstrong>What I built\u003C\u002Fstrong>\u003C\u002Fp>\u003Cp>I got inspired to build this project after watching a \u003Ca target=\"_blank\" rel=\"noopener noreferrer\" href=\"https:\u002F\u002Fyoutu.be\u002FDoWm5k9nmFQ?si=SMPh_OH5lu9VLASg\">yotube video\u003C\u002Fa> by Fons The Improviser. He was talking about improvising as a path we create across chords, using various scales or chord tones. It made me try to think of a useful way to represent the decision we make every time we go to a note when we improvise, or when we create a melody.\u003Cbr>\u003Cbr>I began thinking about hexagonal midi controllers like the hex board, and decided to see what I could do with a hex grid input in the app. The idea was that we can then view note choices less linearly and in a pattern like way. I then realized that this was a learning path that was almost an instrument on it's own, and that musicians should have a way to then bring that to their main instrument. \u003Cbr>\u003Cbr>So that's how I ended up with the concept of an app that was essentially a way for the musician to to compose their own exercises or etudes, and then play them on their instrument by reading the notation, accompanied by the chords and a metronome.\u003C\u002Fp>\u003Cp>\u003Cstrong>How it works\u003C\u002Fstrong>\u003C\u002Fp>\u003Cp>It takes a musician from a chord chart to playing over it, in modes:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cp>\u003Cstrong>Edit progression:\u003C\u002Fstrong> enter the chords, pick their scales, and play the progression back.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Edit etude:\u003C\u002Fstrong> write a line over the chords by picking notes on the hex.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Improvise on the grid:\u003C\u002Fstrong> play on the hex while the transport moves through the chords.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Tune instrument:\u003C\u002Fstrong> the hex lights every note played into the microphone.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Improvise on instrument:\u003C\u002Fstrong> play over the changes with a click, the hex following each chord as it comes.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Read etude:\u003C\u002Fstrong> every bar on one page, with a click and a moving playhead.\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp>\u003Cstrong>Where it is now\u003C\u002Fstrong>\u003C\u002Fp>\u003Cp>Free to use at tonepath.truelathe.com, with its code on GitHub.\u003C\u002Fp>",[49,50,51,52],"tonaljs","vexflow","react","node.js","https:\u002F\u002Ftonepath.truelathe.com","https:\u002F\u002Fgithub.com\u002Fsharkfin-909\u002Ftonepath","\u002Fimages\u002Fprojects\u002Flogos\u002Ftonepath.png",{"project":57,"slides":59},{"slug":43,"name":44,"tagline":45,"summary":46,"body":47,"stack":58,"href":53,"sourceUrl":54,"logo":55,"hasCaseStudy":30},[49,50,51,52],[60,65,70,75,80,85],{"path":61,"url":62,"description":63,"image":64},"\u002F?mode=progression","https:\u002F\u002Ftonepath.truelathe.com\u002F?mode=progression","Edit progression: enter the chords and pick their scales, with the whole screen for the chart. ▶ plays the progression back.","\u002Fimages\u002Fsite-tour\u002Ftonepath\u002Fprogression.jpg",{"path":66,"url":67,"description":68,"image":69},"\u002F?mode=write","https:\u002F\u002Ftonepath.truelathe.com\u002F?mode=write","Edit etude: write a line over the chords by picking notes on the hex, a honeycomb of each chord's scale with a step to the right and a third up-left.","\u002Fimages\u002Fsite-tour\u002Ftonepath\u002Fwrite.jpg",{"path":71,"url":72,"description":73,"image":74},"\u002F?mode=grid","https:\u002F\u002Ftonepath.truelathe.com\u002F?mode=grid","Improvise on the grid: play on the hex while the transport moves the chords, or let chord bump move on after a set number of notes.","\u002Fimages\u002Fsite-tour\u002Ftonepath\u002Fgrid.jpg",{"path":76,"url":77,"description":78,"image":79},"\u002F?mode=tune","https:\u002F\u002Ftonepath.truelathe.com\u002F?mode=tune","Tune instrument: warm up and tune. The hex lights every note played into the microphone.","\u002Fimages\u002Fsite-tour\u002Ftonepath\u002Ftune.jpg",{"path":81,"url":82,"description":83,"image":84},"\u002F?mode=improvise","https:\u002F\u002Ftonepath.truelathe.com\u002F?mode=improvise","Improvise on instrument: play over the changes with a click and the chords, the hex following each chord as it comes.","\u002Fimages\u002Fsite-tour\u002Ftonepath\u002Fimprovise.jpg",{"path":86,"url":87,"description":88,"image":89},"\u002F?mode=read","https:\u002F\u002Ftonepath.truelathe.com\u002F?mode=read","Read etude on instrument: every bar on one page, with a click and a moving playhead.","\u002Fimages\u002Fsite-tour\u002Ftonepath\u002Fread.jpg"]