First OKP4 boilerplate, with Vite

[antho31]

Here is the first UI Starter to interact with the OKP4 protocol (with smart contracts).

It provides all the basic pieces of code to:

• connect with a wallet (Keplr, Leap and even Metamask !)
• get balance
• get contracts list
• get transactions list, decode data
• create cognitarium (RDF triples data store) & law stone (Prolog program rules store) smart contract instances
• insert data in a cognitarium instance
• select data from a cognitarium instance (SPARQL select)
• evaluate a Prolog rule (law stone query)

A step-by-step tutorial will be published soon based on this boilerplate.

FYI @lolottetheclash @ErikssonJoakim @AnjaMis @Yoj16
I'm not used to coding frontends and am not comfortable with CSS coding. Please provide a better UI if necessary. You can take the opportunity to see how interactions with the OKP4 blockchain are possible.

[bdeneux]

@antho31 Is this wanted that all sources file are located in a vite folder ?

[antho31]

@antho31 Is this wanted that all sources file are located in a vite folder ?

Yes, I propose a monorepo, expect more boilerplates with other frameworks (svelte, ...) later ;)

[antho31]

@ErikssonJoakim autoprefixer fixed, thanks for the feedback

[antho31]

FYI - PR linked to a tutorial (axone-protocol/docs#318)

[ccamel]

Alright. Let's proceed with this initial step.

[amimart]

Thx for this first boilerplate, nice to see enhancements to DX 😉

I'll note here some ideas of improvements that should be considered (or not) before going public :):

• Dedicate this repository as the vite boilerplate instead of making it a monorepo containing all the boilerplates.
• Consider a CI ensuring code quality, this also means defining the expected quality of boilerplate :).
• Make configurable some constants like rpc URL.

[bdeneux]

👍

[antho31]

Thanks for your feedback!

• Let's rename this repo "okp4-vite-starter" (or any other name)? Thus giving up the mono repo idea would fix the deployment issue, as we can use GitHub Pages easily 🥳

• @amimart Should I be precise in README that the constants.ts is a configuration file (where you can change RPC URL, ...)? Or use a .env file to avoid misconfiguration? I guess the second option is better. Apart from REST & RPC urls, do you see specific constants to be configurable?

• I agree with the CI, Is anyone interested in helping me on this? I don't know how to approach this subject

[bdeneux]

Thanks for your feedback!

• Let's rename this repo "okp4-vite-starter" (or any other name)? Thus giving up the mono repo idea would fix the deployment issue, as we can use GitHub Pages easily 🥳
• @amimart Should I be precise in README that the constants.ts is a configuration file (where you can change RPC URL, ...)? Or use a .env file to avoid misconfiguration? I guess the second option is better. Apart from REST & RPC urls, do you see specific constants to be configurable?
• I agree with the CI, Is anyone interested in helping me on this? I don't know how to approach this subject

@antho31 I can help you for the CI if you want ;)