Home

HintKeep`@next`

Store hints, not passwords.

The aim of the application is to make a practical and useful application that applies a number of architectural patterns as close as they can be to their definition in order to both exercise them and understand them better.

Use GraphQL as a web API for querying and updating the data.
Use the CQRS architectural pattern as much as possible.
On the frontend, use ReactJS Page Flows and MVVM to demonstrate an alternative to the Flux architectural pattern.
Use Azure Table Storage for a database, can be optimized for querying over editing as in most cases the data will be read rather than modified
The UI needs to be clean, intuitive and most importantly, accessible to everyone. This is an additional exercise for learning and implementing accessibility requirements in a application.
The application is internationalized, although it would only be made available in the English language as a first step.
Use Azure Bicep files for describing and deploying to the Azure infrastructure.
Use netlify.com for deploying the front-end, both hintkeep.net and www.hintkeep.net should work, HTTPS is mandatory.

Deployment and hosting details are on HintKeep@next Azure Web Apps Infrastructure, there are other alternatives such as using Azure Container Instances, but in the end with all the desired environments it will end up 2 or 3 times as expensive. They are not the right pick for hosting a 24/7 web app, but they are an excellent fit for background jobs.

Documentation

This wiki serves as project documentation. Bellow is a list of pages that document the structure of the project, both in terms of files and directories and as data storage and so on.

The linked pages will be updated as HintKeep@next will be developed, currently it is in the requirements gathering and planning phase.

Legacy pages: