building journl

Hey — I’m building journl.

I need something better than Notes, less “office” than Docs, and more expressive and chronological than WordPress or (eurgh) Notion.

They all have their place, but when I want to write about something that takes time — a process — there isn’t really a good place for it.

A notepad comes closest.
But notepads get lost.
Equations get messy.
Nothing links together properly.

So this is me starting journl.

Did this picture work?

Looks like it.

Bold

Heading

Quotes

• bullet 1

• bullet ...

1. un

2. deux

3. trois

for i in cats:
    print (i)

okay, code blocks need some work.

Hi

Hello

Bonjour

hi

This is quite nice, I think.

It means I can be expressionate when I write - less constrained, more natural.

What actually matters in the tech stack?
And am I building things in the right order?

Current thoughts:

• Migrate the DB to somewhere

• Add in PDF exports

• Fix the LaTex stuff

• Fix annoying type issues with typescript

• Enforce that a whole thread has to be shared to share images / posts - for now.

• Allow direct links to posts in a thread.

• Add reader preview to journl writing view.

Not sure about the order yet.

.

.

.

è

Testing.

hope that worked.

that one too?

no. AWS permissions are playing up.

Access to fetch at 'https://journl.s3.eu-west-2.amazonaws.com/u/cmkzztck80000y3asfdkbzgtk/images/5b57a544-4bc1-4602-b96e-c8d024272a40.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA5SFP6PWNIZDZ2C4Q%2F20260324%2Feu-west-2%2Fs3%2Faws4_request&X-Amz-Date=20260324T222610Z&X-Amz-Expires=60&X-Amz-Signature=42591582a92717da0802091701e40d8b3b6bfa8054e0bb118e3de4a482d3065c&X-Amz-SignedHeaders=host&x-amz-checksum-crc32=AAAAAA%3D%3D&x-amz-meta-originalname=ma-thin-yZksb3p98H4-unsplash.jpg&x-amz-sdk-checksum-algorithm=CRC32&x-id=PutObject' from origin 'https://journl.ink' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.