Future Plans, Whats Next for Us?

I don’t usually document what I am planning rather than what has just been done. However as the planned changes will be substantial maybe it’s time to both add a bit of content and document the planned changes.

Database

So The plan is to add a database to the project, the main purpose of which is to provide a revisions section where I can document the changes made for each build and if the build was successful and published or not.

The plan then would be to further develop this to store links for display down the line.

Table structure

So the planned table schema is:

CREATE TABLE revisions (
    id INT AUTO_INCREMENT PRIMARY KEY,
    version_number VARCHAR(10) NOT NULL,
    description TEXT NOT NULL,
    author VARCHAR(255) NOT NULL,
    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
    updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
    status VARCHAR(50) NOT NULL
);

provided by Copilot, however this will need changing to the format required by Astro.

Turso database distribution

Adding this is also going to require an account creation with TTurso which doesn’t seem inconsequential looking at the documentaion. And this is on top of the setting up of the local db. Hence the hesitation in pushing this forward.

CardPlus

Following this I plan to add a new display card based on this tutorial: Inverted Radius Shape

Radius Card

So next its putting some of this into practice!