Software Repo, Teck Stack

The frontend never directly touches the WordPress database. That’s one of the central ideas of Jaroa. 2. What have we built so far and what is the current architecture status? We have built Quite a lot, actually. First: the frontend exists – let’s take a look at the app directory (which will change over time) […]

We started with an older project called: That was our experimental house. We then decided: “This idea is worth becoming something of its own.” So we created: and pushed the first version to GitHub. We are currently working on: It is not a framework yet. It is the first working application from which we are […]

Perfect. ✅ We have successfully headed from the old Headless PHP Application identity into Jaroa. That is exactly the final state we wanted. So Jaroa Development Change #2 has been successfully committed and pushed. We now have: And importantly, our working tree confirms that we did not accidentally commit backend/wp-config.php. Now we would make the […]

I would start just after the README commit, and I would resist the temptation to immediately add another feature. The architecture is working. Now we need to decide what Jaroa 1.0 actually means as a product, not merely as a technical experiment. My recommended next step: establish the Jaroa application lifecycle Right now we have: […]

I think it is an excellent idea, and actually it fits Jaroa unusually well. What you’re proposing is more than keeping a development diary. It creates a public chronological record of how the project evolves, which is valuable precisely because Jaroa is being built incrementally. The important distinction I’d make is this: Each conversation becomes […]

A small experiment in building a simpler web application There is a particular moment in software development when a collection of files begins to feel like an application. It does not happen when the first page renders. It does not necessarily happen when an API returns JSON. It happens somewhere in between, when the pieces […]