Joep Meindertsma
Joep Meindertsma
Sometimes, when designing URLs and naming things, we make mistakes. And with we, I typically mean myself. So at some time in the future (before 1.0), I'd like to fix...
Atomic Data aims to increase interoperability. For developers to make interoperable apps, they need to: - Define their data model using Atomic Data Classes - Make sure their data model...
If we want Atomic Data to be successful, we need easy, accessible methods for people to convert their existing data to Atomic Data. I call this project: _Atomizer_. We need...
We often want to provide more information about the relationships _between_ resources: - Say I want to describe the `friendship` between two people. I could create a `friendship` Property that...
Currently, the get started section is a small part of the overview page. This could be improved by making it a larger page that feels more like a tutorial.
See https://github.com/atomicdata-dev/atomic-data-browser/issues/172 Having a [Class for Errors](https://atomicdata.dev/classes/Error) helps to standardize how we communicate Errors from back-end to front-end. I suppose other usecases will present themselves later.
Having machine readable errors is essential for getting a good user experience while dealing with forms. For example, if some username has been taken, we want to show an error...
https://github.com/jamstack/jamstack.org/new/main/src/site/headless-cms ``` --- title: Atomic-Server repo: atomicdata-dev/atomic-data-rust homepage: https://atomicdata.dev twitter: atomicdata-dev opensource: "Yes" typeofcms: "API Driven" supportedgenerators: - All description: Atomic-Server is an open-source headless CMS. Lightweight, very fast, easy...
Currently, users have to know the subject of a resource when creating a commit. This is fine for editing existing things, but what if the resource is new? This introduces...