I want clear documentation with hello world example and Get Started steps

Feedback from IMDEA.

I want to create the Boards Appview. Why can't I use the Auth System directly without so many questions from the AI?

Creating /:board inside the existing web app is easier because we can reuse, almost for free:

existing Vault auth

existing daemon auth cookies

existing webUniversalClient

existing site/document routing

existing document creation/draft flow

existing permissions/capability checks

existing layout/header/menu infrastructure

existing Remix server API routes

A whole new app is more independent, but it forces us to recreate or extract:

auth callback flow

/api/auth and /api/config

daemon proxy

local key storage glue

signer-backed publishing

route parsing

app shell

deploy/runtime config

So if your priority is start building fast, I recommend: implement /:board as an AppView in the existing web app first. Once the product shape is proven, we can extract it into a standalone Board app later.

Creating a Server, running a new branch, and building the new code takes 80% of my Vibe Coding time

Installation Guide

Complete Uncertainty on the Presentation View Layer should work

Feature/Slice/Segments is the right framework for us?

Board is a new AppView? with a query, with new UI components, and with some new Metadata Blobs (tries)?

UI Components

When to create a new one?

Can we have a Skill that teaches you all this?

I want to understand how the system and protocol works

I thought that the https://explore.hyper.media/feed would give me the Feed of Blobs coming into my Node, and I would help understant how the network worked.

Instead we have the Feed Events. I understand they are important if the are the event sourcing stream of events? mmmh

In the code, type: "citation" and type: "doc-update" are frontend loaded feed event types, not the raw protocol blob types.

I want clear documentation with hello world example and Get Started steps

I want to create the Boards Appview. Why can't I use the Auth System directly without so many questions from the AI?

Creating a Server, running a new branch, and building the new code takes 80% of my Vibe Coding time

Complete Uncertainty on the Presentation View Layer should work

I want to understand how the system and protocol works

I have no idea on how to run this without branching the app, can't we have an easy way to run my own software?

It would be useful to have a protocol analyzer that tells the developer in real time protocol verification feedback