At Kleeen, we have at our transparency as a core philosophy. This means we want to be open about how we built the Kleeen Authoring Tool. If you are apprehensive about investing your time and energy into using Kleeen and what you're going to get, below is an explanation of our foundations and links to the sources.
- Kleeen’s authoring tool export follows standard practices to manage repository, project, and code, making it easy for long-term maintenance and support away from our authoring tool.
- Once code is exported to your repo it is your code. Kleeen doesn't own your code or see your data.
- Every project exported to GitHub will follow a monorepo structure; this means that the repository will contain multiple projects and libraries.
- We use a build framework called Nx to architect the monorepo, which has broad support across the dev community, great IDE integration, and extensive documentation.
- Here’s to find more about Nx and React https://nx.dev/react.
- We have built the API project on top of the Apollo platform, which at its core utilizes the open-source GraphQL client and server. Anyone working with GraphQL will need a platform. If you want to find out more about Apollo, you can do it here: https://www.apollographql.com/.
- Working on the Cloud project should be welcoming as all code generated is well organized. All modern web application development has to do with state management, for which our exported projects use React-Redux, which is maintained directly by the Redux team.
- Finally, it’s worth to mention we use the latest version of all libraries, including React on its version +17 and the release of Hooks, which will make it easy for you to keep the project updated.
- To learn more about Redux and React Hooks, please visit the following links: https://react-redux.js.org/introduction/why-use-react-redux, https://reactjs.org/docs/hooks-intro.html
If you have any questions about this, please contact firstname.lastname@example.org and we will be happy to answer them for you.