rix1.dev · my personal website

Welcome to the source repository of my personal website, rix1.dev! I'm a product developer and engineering manager based in Oslo, Norway. My website showcases previous and ongoing projects as well as my professional journey.

About the Site

Built with Lume and served by a small Deno runtime, the site reflects my interest in products, technology, and design.

Features

• Project Showcases: Detailed overviews of my latest and past projects.
• Blog: Insights into my professional experiences and personal interests.

Built and deployed with

• Lume - A static site generator built with Deno.
• Deno - A secure runtime for JavaScript and TypeScript.
• Deno Deploy - A hassle-free platform for serverless JavaScript applications.
• Deno KV - Privacy-friendly page and crawler counters.

Local Development

To get a local copy up and running, follow these simple steps.

Prerequisites

Ensure you have Deno installed on your machine. To install Deno, run:

curl -fsSL https://deno.land/install.sh | sh

Installation

1. Clone the repo:

   git clone https://github.com/rix1/rix1.dev.git
   cd rix1.dev

2. Start the Lume development server:

   deno task dev

The site should now be running on http://localhost:3000. Open your browser to this address to view the site.

To test the production-style dynamic runtime, build the site and run the local server:

deno task build
deno task start

The dynamic server runs on http://localhost:8000 and includes runtime-only features such as /status, /api/visitor-count, and the Deno KV visitor counter.

Production Runtime

Production uses Deno Deploy's dynamic runtime with serve.ts as the entrypoint. The visitor counter is intentionally privacy-friendly: it stores anonymous per-page human visitor hashes and declared crawler families, but not IP addresses or raw user agents.

Set a stable private salt before deploying so the anonymous human hashes remain consistent across deploys:

deno deploy env add VISITOR_COUNTER_SALT "<random-long-value>" --secret

Pass --org <name> or --app <name> if the Deno Deploy CLI has not already selected the right application.

If the salt changes later, existing anonymous visitor IDs will no longer match new hashes, so counts may start incrementing again for returning visitors.

Writing Posts

Posts live in posts/*.md. To publish a new one, add a Markdown file with this front matter:

---
title: My post title
description: A short summary used for the overview, RSS, and social previews.
date: 2026-05-18
topic: Build
---

The shared defaults in posts/_data.yml add the post layout, author data, and the post tag automatically. For interactive posts, prefer a small browser script or web component in assets/ and opt into it from the post:

scripts:
  - /assets/my-post-widget.js

Blog images can be normalized to the site's wide image format with ImageMagick:

deno task image:blog input.jpg assets/my-post/output.jpg

This exports a stripped sRGB JPEG at 1600x900 and quality 84.

Drafts live in drafts/*.md with draft: true. Lume renders drafts while serving locally, but deno task build ignores the whole drafts/ folder so they do not deploy.

Contributing

I would be surprised if anyone would like to contribute to this site, but if you find any typos feel or want to change my opinion about something, feel free to open a PR:

1. Fork the Project
2. Create your Feature Branch (git checkout -b fix/your-opinion)
3. Commit your Changes (git commit -m 'Adjust your attitude towards X')
4. Push to the Branch (git push origin fix/your-opinion)
5. Open a Pull Request

License

Distributed under the MIT License. See LICENSE for more information.

Contact

• @rix1 - Twitter
• Project Link: https://github.com/rix1/rix1.dev
• Website: rix1.dev