making this website

tags: 👨‍💻-dev, 🌱-early, 🔬-thissite,
published
updated

highlights:

misc notes:

why this stack?

i’m not sure what this stack would be considered (astro + md(x) + githubpages), agm / gam / mag or amgp?

i’ve always liked the idea of astro, & the ability to try other frameworks within* it.

i’m curious about the aha stack, because i haven’t poked around htmx or alpine.js, but they sound really interesting (i’m already a big fan of astro).

basic structure

i plan on having most of the files be md(x), but there’s still a few that are astro (home, about, user story mapping sample).

a few main pages

i’ve got samples-index hidden at the moment.

‘samples’ is intended to be a ‘work sample’ thing. the anxiety of having legitimate case studies is weighing on me too much, especially with the amount of time that’s passed since my last fulltime role.

in order to keep links and resources more relevant, i’m framing it as a sample of some work that i’ve done with some current resources that would help today.

just 2-overcomplicated

originally, i had marked a separate content collections with a work collection.

this meant creating additional folders & setup pages.

after going through the process, it seemed to make less sense, especially with my current samples folder.

i can keep the structure pretty flat, and adjust later if i need to create folder for separation. (tried nested folders-test && it seemed to work with the [...slug].astro file).

take a peek

peek the YAML

below is the frontmatter for this.mdx file.

---
title: "making this website"
description: "notes about the making of this website (kelsy.design)"
pubDate: "Jan 27 2024"
updatedDate: "Mar 29 2024"
tags: ["👨‍💻-dev", "🌱-early", "🔬-thissite"]
---

experiment below with an image using highlighter plugin in figma

A code snippet with metadata for a website, including title, description, publication date, update date, and tags related to development stages and draft status

some references:

peek the package

the current website is made with the following package.json.

"dependencies": {
    "@astrojs/mdx": "^2.2.2",
    "@astrojs/rss": "^4.0.5",
    "@astrojs/sitemap": "^3.1.2",
    "astro": "^4.5.12",
    "lightningcss": "^1.24.0"
  }

current content collection folder structure

content/
 notes/
    - about-this-site.md
    - filenaming-experiment.md
  - .config.ts
pages/
 notes/
  - [...slug].astro
  - [page].astro
 tags/
  - [tag].astro
  - index.astro
 samples/
  - sample01.astro
  - sample02.mdx
- about.astro
- all-posts.astro
- index.astro

meta notes

i like to spread my thoughts across different tools & mediums.

A sketch-style digital drawing showing a conceptual map of a design process with notes, diagrams, and various interface states

sometimes the difference is subtle, but usually there are enough differences between tools that i tend to get different ideas.

A mind map-style design showing a central node labeled "notes" with connected nodes labeled "TODOS," "misc," and "archive," further branching into detailed tasks and sections

doodling out the different ideas in goodnotes on the ipad + apple pencil is a lot different from using a dedicated mindmapping tool that’s also a native app (i.e., not electron) like mindnode on a mac mini.

i also end up thinking a lot with a mix of code, figma, & browser (testing + tabs for docs).

exploring & asset creation + seeing in the browser, back to figma, read some docs, explore in code + figma, repeat.

if i feel myself starting to get stuck, i’ll switch contexts to help loosen things up again.

it might be switching over to the ipad to doodle or maybe pen + paper for a bit.

i’ve noticed that ideas come a lot easier when i let myself think from a different angle.

it’s also a good excuse to practice with different tools, but in a way that is ~semi focused on what you’re working on.


👈 back to all notes