Photo migration, docs readiness, and ICP groundwork.

Today was a builder’s day in the best way: lower noise, more execution, and visible progress across product, content infrastructure, and top-of-funnel preparation. I also had a solid gym session, which helped the rest of the day stay focused and clean.

Compared to yesterday’s distribution-heavy rhythm, today was mostly about shipping foundational pieces that make future outreach and publishing easier.

What I shipped

• Built and shipped a new /photo page for the website.
• Added a stronger visual treatment (including the dither look) to make the photo experience feel more intentional.
• Started migration away from photos.egeuysal.com into the main site flow.
• Switched photo storage from Cloudinary to Vercel Blob.
• Shipped an accessible Ryva /docs page to support upcoming warm intros.
• Wrote the essay planned for today.
• Confirmed machine-readable public feeds are available: blog.json, diary.json, and photo.json.

The main theme was reducing fragmentation: fewer disconnected properties, fewer moving parts, and cleaner surfaces for users who want to explore what I am building.

Product and infrastructure signals

The photo-page migration matters more than a visual update. Moving from a separate photo property into the main website simplifies the content system and removes one more split context in the brand. People now discover photos in the same environment where they can also read blog posts and diary updates.

Switching from Cloudinary to Vercel Blob also gives me tighter control over the stack I am already using. Less platform sprawl usually means lower maintenance cost over time, cleaner debugging, and fewer integration edges to monitor.

Making blog.json, diary.json, and photo.json available is a quiet but high-leverage move. It creates a structured layer for future automation, indexing, and external analysis without adding work each time.

Outreach and ICP momentum

My LinkedIn connection limit reset, so I restarted outbound connection requests today. Current post reach staying around 1k+ views per post is a useful baseline signal: attention is consistent enough to keep distribution compounding while I keep shipping.

I also wrote roughly 20 replies across relevant Reddit threads. These were not broad-audience comments; they were targeted at hard ICPs who already have incomplete solutions in place. That context matters because trust is usually easier to build when the pain is already understood and actively felt.

Planned funnel from those threads:

• Start with useful public replies.
• Wait for positive engagement.
• Move qualified people into DMs.
• Continue with a short, tailored conversation instead of a generic pitch.

Weekly execution strategy

This is the last week of school and test load is high, so I am intentionally keeping the operating mode lighter. Instead of forcing maximum output every day, I am focusing on high-leverage tasks that can compound asynchronously:

• Product surfaces that stay useful after one shipping pass.
• Documentation that supports third-party intros.
• Outreach systems that can be delegated or batched.

I am also letting my dad handle part of the connection flow this week, which is practical given the time constraints.

Friction and risk

• School tests reduce available deep-work windows.
• Increased top-of-funnel activity can create follow-up debt if responses spike.
• Any media migration can introduce silent issues (broken links, stale caches, missing assets) if not monitored after launch.
• Delegated connection flow can increase volume, but message quality still needs to stay high to preserve trust.

Numbers

• 1 new /photo experience shipped
• 1 media storage migration completed (Cloudinary -> Vercel Blob)
• 1 Ryva /docs page shipped
• 1 essay completed
• 3 structured public data feeds confirmed (blog.json, diary.json, photo.json)
• ~20 Reddit ICP replies posted
• LinkedIn outbound restarted after limit reset
• Social baseline remains ~1k+ views per post

Quote of today

Build the surface once, then let every future conversation land better.

Main progress today: I consolidated content infrastructure, upgraded discoverability surfaces, and kept ICP conversation pipelines active without overloading the week.