Welcome to 26to26

Welcome to 26to26 — a tiny experiment where I’m rebuilding shikadigital.co.jp from the ground up in 26 days.

What is 26to26?

26to26 is a personal experiment. Starting December 6, 2025, and running through December 31, 2025, I’m rebuilding my digital agency’s website using modern web technologies and AI-assisted development workflows.

This site you’re reading right now? It’s where I’m documenting the process — mostly for myself, but if it helps someone else, that’s a bonus.

Why 26 Days?

The timeline is intentional: 26 days to close out 2025 and set the foundation for 2026. It’s tight but doable, forcing focused work without endless planning.

The rough plan:

  • Days 1-5: Foundation and architecture
  • Days 6-15: Core features and content
  • Days 16-22: Polish and refinement
  • Days 23-26: Testing, optimization, and launch

The Tech Stack

This project showcases modern static site development:

  • Astro 5.x for lightning-fast static site generation
  • Tailwind CSS 4.x with a custom Terminal/Code theme
  • Bun as the JavaScript runtime and package manager for blazing-fast performance
  • Content Collections for type-safe content management
  • AI-assisted development using Claude (Desktop and Claude Code) and Kiro
  • Deployed on Sevalla with global CDN distribution

Here’s a quick example of how Content Collections work in Astro:

// src/content/config.ts
import { defineCollection, z } from 'astro:content';

const daysCollection = defineCollection({
  type: 'content',
  schema: z.object({
    title: z.string(),
    date: z.date(),
    dayNumber: z.number().min(0).max(26),
    summary: z.string(),
    status: z.enum(['upcoming', 'in-progress', 'completed']),
  }),
});

export const collections = { days: daysCollection };

This type-safe approach ensures every daily post has the correct structure and validates at build time.

What You’ll Find Here

Each day, I’ll document:

  • Technical decisions and architectural choices
  • Code examples with syntax highlighting
  • Challenges encountered and how they were solved
  • AI collaboration insights — what worked, what didn’t
  • Design evolution following the Terminal theme aesthetic
  • Performance metrics and optimization strategies

These are mostly notes for myself, but they might be useful to someone else trying similar things.

Why Document It?

Documenting the process helps me think clearly and stay focused. By writing things down:

  1. I stay accountable to the timeline and my own standards
  2. I can review what worked and what didn’t
  3. I learn better by articulating decisions and trade-offs
  4. Maybe someone else finds it useful — but that’s not the main goal

What to Expect

Starting tomorrow (Day 1), I’ll post daily updates as the shikadigital.co.jp rebuild takes shape. Some days will be heavy on code, others on design, and some on problem-solving and iteration.

The posts will be honest — including the mistakes, the dead ends, and the frustrating parts. That’s how development actually works.

Let’s See What Happens

26 days. One complete website rebuild. Daily notes.

No pressure to build an audience or perform. Just focused work and honest documentation.

Day 1 starts tomorrow.

This is Day 0 of 26. The journey begins December 6, 2025.