Planets

Dynamic Routes

“Profile” page for planets

This is being created by Nathan on a standalone NextJS application that will then be merged with the rest of the signal-k/client repository.

Because Next.js uses the moduleName.module.css hierarchy for css files, I would recommend that the styles for the frontend are put in the styles folder with the following (demo) structure:

pages/

public/

next/

build/

lib/ / utils/

styles/

planets/

base.module.css → global styles for the planets section

cover.module.css → styles relating to the “cover image” section of the planet page

• This is just an example structure, but it would be ideal for all the CSS files to be in an internal folder inside styles/ as when we bring these components into the main Next app on signal-k/client, we’ll need to have a distinction between each route and the styling components for said routes → just makes it easier for us with things like imports & merge conflicts down the line.

Anomalies

Anomaly claiming

Claim a planet NFT, then create a proposal/publication about it Voting on Proposals (frontend)

Anomaly staking

Once an anomaly has been confirmed, it can be staked to earn resources (and then we can update the traits like numberOfBuildings)

Generating anomalies

Right now, we need to add functionality to enable the colours of the planet biomes to be changed. This snippet is where we can change the colours: