greenheart / greenheart.github.io Goto Github PK

Try running npm run build && npm run preview to reproduce the error.

Automated image optimization might be useful in the future, to allow blog posts to include more images.

"I am an 19-year-old orienteer..." should be "I am a 19-year-old orienteer..."

I noticed http://samuelplumppu.se via https://raviloop.github.io via https://gitter.im/gitterHQ/gitter?at=5830518f5eb8ea792a3d1a0a by @raviloop

This would speed up the page load time by easily cutting the image sizes in half.

For inspiration, see how it was solved in IDG.tools

Create a quick blog post about TailwindCSS plugins, and making custom utilities show up in the editor intellisense. This adapts well to the workflow, while still getting the other benfits of Tailwind.

https://gist.github.com/Greenheart/7242428baf948aaf6d3a1af10c161ced

This would be a really nice feature to make the blog more social, while still keeping control and building on open standards rather than adding a custom commenting system.

Idea: https://webmention.io/
Idea: https://github.com/snarfed/bridgy

Implementation walk-through: https://www.codingwithjesse.com/blog/add-mastodon-replies-to-your-blog/

latest first

This can be generated at build time, with the metadata from each post. Also use the same data for regular SEO.

This could catch broken links and redirect to the landing page

Update title, and clarify that it's not about tech, but about systems change, and developing (technical but also social and cultural) systems that enable change.

Become aware that we are all co-creating systems all the time. We're embedded in multiple layers of systems, and we use systems. Thus understanding how to design, develop and use systems is a core capacity that I want more people to get access to. Similar to the power of words, the power of systems design and development is something that requires great responsibility. But also something we need to distribute power, so it truly becomes democratic and not elitist or centralised. Thus free software is another critical component to enable this.

But also co-operation over competition.

This is needed to fetch assets correctly

Would be fun to keep a full history, and see my progress and development over the years.

Maybe keep it all public?

Note to self:

There are four pieces needed to make nvm work when loaded as a omz plugin:

1. setting NVM_DIR
2. adding the nvm plugin
3. configuring the nvm plugin to lazy load
4. starting omz and loading the plugins

By following all these steps, shell startup time went down from ~1.5 s to ~200 ms. A huge improvement for a common action performed many times daily.

export NVM_DIR="$HOME/.nvm"

plugins=(nvm git)

zstyle ':omz:plugins:nvm' lazy yes

source $ZSH/oh-my-zsh.sh

Use the new data-sveltekit-preload-data="hover"

https://kit.svelte.dev/docs/link-options#data-sveltekit-preload-data

This could be similar to how it's solved for IDG.tools and IDG.community

• maybe consistent casing like "My tech stack" instead of "My Tech Stack".
• Update skills so they are relevant.
• Update intro text.

How to reproduce:

1. Visit any blog post
2. Go to the home page / using the link in the top left header
3. The page title does change when navigating between different blog posts, but not back to the original page title for the landing page

Probably need to use specific meta tags for the blog posts, and then a more general set of meta tags for the landing page and about page.

• Possibly enable data-sveltekit-prefetch for the entire page.
• Remove the need for a custom Link component, and the isExternalURL() helper.
• Possibly update the blog post about automatic link prefetching since it's now outdated.