I’ve realized I have this post type.

I talked about work in the normal journal, but I’d rather use this.

Journal = Personal.

Work Journal = Work.

I once had them connected by relationship, but we don’t need tha complexity.

—–

Reaper:

Reaper was started on Fr, 5. Dez (there’s a post about it) – exactly one month later now.

We sprinted initial dev – about 1 full week to have something great. Further small improvs were made along the way. Transforming from simple assembler to Engine.

Today, we introduce Code Editing and a major UI improvement (feels much better).

Improvements:

From the single left Sidebar to: Topbar, Sidebar Left, Sidebar Right.

Topbar can be moved to the bottom. All areas can be toggled on and off.

Also though: „Why the hell not“ – let’s try Code Synch Integration – let Claude Puppy think and determine if it’s possible or not.

Had the initial ideas in Bad Gastein to build something like EtchWP – Scoped Elements and allows editing from frontend.

Talked to GPT about it today on a walk with the Dog, while freezing cold.

GPT outlined that Scoping code per element is the tricky part – need to create AST (Abstract Syntax Tree), map it and coordinate changes and such.

I asked, if it’d be easier to show sections code – and it is. Also logical: simply load the section code „strings“ and replace them when editing.

First I had ideas to build it in a new one: Reaper Evo – that should solve all bottlenecks, but that’s retareded. Rather improv current Reaper. Writing new = major work. Claude can rewrite implements = actually works pretty well, even though codebase is large already. There might be unused code laying around, but I don’t care much.

Claude ripped it beautifully:

Crazy. UI –proto-primary takes on normal theme –primary.

Tomorrow, I’ll work it for Flexopack 2: writing the project new.

Issue still: header logos (background img is not the best.) I can instruct it to use normal imgs though = dark light mode switch we need in the rarest cases.

Tomorrow, we’ll work it for sure.

Also on the List: „The JSON CMS“ – a CMS UI we can include in every project.

PHP registering of post types = only needed for CMS. Frontend can remain static.

We have the proto already and I’ll now enhance it with OPUS4.

Introducing some new field types. Not sure if we can do relationships with JSON objects? – Probably: need to introduce post number id (curr id is text.).

JS fetch in the frontend. Needs to be baked into the code, but no problem for CC.

I have to figure out the best workflow: Me & the Tool.

Do I prompt, let it ripp and watch shorts in the meantime? I FUCKING HATE THAT.

Prompt prepation carefully. Then work on the manual things while it ripps in the background. Treat it like a MACHINE, it can work. It’s not fragile. Don’t screw it up unnecessarily, but work it.

If code export = then rewrite, then publish – or whatever is the best way.

-> Reaper Multi Page support: JSON file mapping links to configs?
?project=blueprint&config=homepage&preview=true. Basically mapping the config={}parameter.

Then Reaper Prototypes would be clickable.

But that’s something I learn more about when actually working it.

I can also simply include a list of all links individually.