Explore >> Select a destination
|
You are here 
|
josh.works | ||
| | | | |
mzrn.sh
|
|
| | | | | Most websites I build start off as a blank Jekyll site with Tailwind CSS on top. | |
| | | | |
danq.me
|
|
| | | | | My family and I have made a tradition of our regular attendance of Fairport's Cropredy Convention. There I - being the earliest riser of us - have in turn made a tradition of getting up early to find a nearby geocache on any morning that I'm up before the kids. This practice has already eliminated all of the caches in Cropredy itself, and so now my morning walks take me further afield. This morning I opted to follow the footpath over the fields to Great Bourton to investigate the two multicaches commencing in the churchyard. Having determined the coordinates for both and (unsuccessfully) attempting the other cache first, I was optimistic for a smiley face here. The GZ was easy to find - I'd stopped here to check my map on the way out! - and I was soon searching in earnest. In the low-angled light of the morning sun, the shade of the thick leafy canopy made for challenging conditions, so I flicked my torch on and pointed it in the direction of the host object... and there, clear as day despite its camouflage, was the cache. Easy as pie! SL. I was briefly tempted to re-try the cache I failed to find earlier, under the assumption that the container would look similar to this and the same technique might bear fruit. But I didn't feel like doubling back twice more while my stomach was rumbling, so I carried on towards Cropredy to see whether any others if my party were yet ready for some grub. TFTC. | |
| | | | |
mherman.org
|
|
| | | | | Step-by-step guide covering how to automatically deploy a Jekyll site to Netlify using Docker and GitLab CI. | |
| | | | |
geoff.tuxpup.com
|
|
| | | How I Start: Django, Tailwind, HTMX (part 1) I wanted to try out some "modern" front-end development for a while, and I did. FastAPI is great. So is Svelte. But even though I found creating APIs that way to be a breeze, building a whole site that way felt much slower and heavier than using traditional server rendering. So I decided to give django a fair shake for a while, and I'm glad I did. | ||
