We got window splitting working in Electron. This validates that our layout engine can handle real spatial complexity - the foundation we need before building the negotiation engine. Next up is the negotiation engine itself: a system where components and slots talk to each other about space. Components say "I need this much room" and slots respond "here's what I can give you." It's bidirectional, which will make our platform powerful. The breakthrough this week came from prototyping in Figma first, using their autolayout to test how properties interact. The video shows the split in action. One layout engine, infinite arrangements, ready for the negotiation layer.

Reorganized codebase into scalable hierarchy - applications to root, clients under applications/client/. Moved Storybook into core app for in-context component development, reducing iteration cycles. Fixed theming to use global state instead of UI context tied to layouting. Updated all build configs, tests, workflows and infrastructure to align with new architecture. Things feel cleaner.

Defined fundamental component structure covering sizing, position, behavior and visual properties. Split Settings into individual components to establish the component philosophy. Subslot mechanism works well. Launched Electron desktop version - now supporting both web and desktop clients. Improved layout engine to handle CSS grid control with content alignment and dynamic row sizing.

Built subslot mechanism that enables complex layout fragmentation. Layout engine now supports coordinate variations (A1 vs a1) for size indication. Cleaned up recursive function issues - DOM output is now clean and manageable. Added GitHub CLI for pull requests and refined the coordinate system philosophy.

This week we had first TV shared coding session - we're truly working as two developers now. Moved layout engine from semantic to coordinate system (A1-B1-B2) and split Settings into 3 components. This revealed we need component clustering - one more layer for the layout engine. Reached new collaboration level with proper code review workflow.

Implemented first padding fixes and defined the layout engine architecture. Two-tiered system: slots decide grid position, components handle size with flexbox priority. Restructured Storybook into a catalogue, not a library. Ready for next sprint focused on component development and settings integration.

Got the slots system working with negative and positive space areas. Added design tokens to Storybook and set up Windsurf rules for better AI collaboration. Built a husky script that blocks app areas based on user roles.

Cracked the layout system - modes are working and we can switch between them smoothly. Narrowed down 38 potential features to 5-6 core differentiators for our alpha. Built the first pass of our block editor and writer mode.

Finally working together on the same codebase. Set up Storybook as our project overview and added our first production atom - background. Backoffice, backend and rest is waiting to be connected with the new UI. Finally have a systematic way to build instead of just exploring. Started building version 2 of the website.

Big milestone this week - we merged magicbinder into the main Diskura project, so we finally have one shared codebase to work on together. Started designing the 'builder helper' panel, but the real challenge is figuring out how users jump from planning to actually building and back to planning again.

Cracked a major problem: AI gets lost when you give it too much freedom. Built 7-8 guardrails to keep AI focused and prevent it from overcomplicating things when we build Diskura. This is the difference between AI that helps and AI that creates chaos.

Settled on our system hierarchy: Workspace → Subspace → Project → Builder. Like organizing a craftsman's shop - everything has its place and purpose. The real challenge: how do you let AI help build while keeping the integrity of the craft intact?

BIG WIN! 🎉 We built our first AI page builder prototype that generates Next.js pages from company descriptions, an early step toward automated design-to-code workflows. We've also improved our design tool's container performance and added sidebar collapse functionality. The UI is aligning with IDE patterns while we explore interactive canvas concepts.

Automated our deployment pipeline so we can ship updates instantly via github actions. No more manual deployments slowing us down.

Launched our public website to start sharing what we're building. Hello world!

We're taking time to define what a 'project' means in our tool. To us, it's more than a folder of files; it's a dedicated space where fragmented ideas can be thoughtfully joined into a coherent whole.

We've decided to design our user interface directly with code, using AI as an assistant and skip Figma as the main tool. This lets us work with reality sooner, helping us build with a more hands-on, intuitive feel and see what works and doesn't.

The first version of our internal Starter Kit is complete. We see this as building the foundation of our workshop - a solid, reliable base that gives us the stability to build our tools upon.

Our initial roadmap is sketched out. The goal is to address the fragmented nature of modern toolchains by creating a single, shared space where the different stages of creation can come together cohesively.

Craft is often a collaborative effort. We've added user invitations and permissions to the starter kit, making it possible for teams to work together in a shared, organized space.

Switched to a better backoffice tool - Refine. Small changes like this add up - now we can focus on building instead of fighting our tools.

A satisfying moment of 'joinery' this week. The frontend and backend of our starter kit are now connected, turning two separate parts into a single, functioning piece for the first time.

We've refined the core concept for Diskura. The aim is to create an environment where anything that can be coded can be created, with the care and intention of a craftsperson, making it a true partner in creation.

Cut our build time in half with some smart optimizations. As a bootstrapped team, every minute saved is a minute we can spend building features that matter.

While working on the starter kit, we registered diskura.com and started a parallel prototype. This is our space for exploring new UI concepts and asking what a more thoughtful interface for builders might look like.

Decided on RDS Aurora Serverless v2 for our database. Its ability to scale to zero is perfect for low-cost experimentation - a principle that feels important for any creative tool.

Picked a simple state management solution, Zustand and Tanstack Query. We will see how it holds up over time.

Set up a monorepo structure that actually makes sense. No more hunting through scattered folders, everything has a place.

Shipped our first working UI components. They're not pretty, but they work - and that's what matters right now.

Project kickoff. Building feels fragmented - too many tools, too many handoffs, too much context switching. We want to change this with Diskura. Before we dive into core features we are starting with magicbinder, a starter kit that we can reuse for building anything.