Devlog #3

hmm, So when i started the project i thought i would build an actual simulation where i could show everyone how it works, its still far from that.

So i focused on doing that,
I took a break from working on the runtime itself and started building the website.

Until now, everything was happening inside the codebase. The runtime was working, benchmarks were running, and tests were passing, but if someone visited the repository they still wouldn’t understand what CORES actually does.

I just wanted it to explain the project.

Building the homepage

I started building the first version of the website using Next.js.

Most of the time today went into trying different layouts and figuring out how to present the project in a simple way.

The homepage now has:

• Hero section
• Navigation
• Runtime statistics
• Benchmark summary cards
• Cognitive architecture visualization
• Responsive layout

One sentence stayed with me while building the page:

The project should focus on making robots think better in emergency situations and have actual knowlege of their resources and their environment.

I think it explains the project much better than a long paragraph.

Designing to match my thinking

After changing the layout a few times, I removed most of the unnecessary elements and kept the design much simpler.

I’d rather have a clean page that explains the project than something flashy that distracts from it.

Deployment

Getting the website online wasn’t completely straightforward.

Since the repository contains both the Python runtime and the Next.js frontend, I had to configure Vercel to build only the frontend.

A couple of module import issues also showed up during deployment.

After fixing those, the website finally deployed successfully.

Thinking about the project differently

While working on the homepage, I realised something.

The website shouldn’t just tell people what CORES is.

It should help them understand it.

Instead of reading pages of documentation, I want someone to interact with the runtime and see how scheduling decisions change under different situations.

That’s probably where I’ll spend most of my time next.

Testing

I also added around 80 more tests while working on the project.

The runtime is getting bigger every day, so I’d rather spend extra time writing tests now than spend hours debugging later.

End of the day

Today wasn’t about adding another algorithm.

It was about making the project easier to understand.

The runtime is only useful if people can understand what it’s trying to do, and I think the homepage is a good first step toward that.

Progress today

• Built the first version of the CORES homepage
• Added runtime overview and benchmark cards
• Added cognitive architecture visualization
• Simplified the website design
• Deployed the frontend on Vercel
• Fixed deployment and module import issues
• Added around 80 new tests

Tomorrow I’ll start working on the simulator so visitors can interact with the runtime instead of only reading about it.