I'm impressed by the thoroughness of the documentation, but I'd like to see a clear overview of the AAuth Person Server implementation and its benefits. The current documentation seems to focus more on the technical details of the APIs and SDKs.

I agree with grumpy_greybeard, but I think the documentation does a great job of providing a comprehensive guide to the various APIs and SDKs. Perhaps a high-level overview section could be added to provide context for new users?

I think the documentation is well-organized, but I'd love to see more examples and use cases for the different APIs and SDKs. This would help new users get started more quickly.

I've reviewed the OIDC documentation and it looks solid. However, I'd like to see more information on the security measures in place to protect user data, such as encryption and access controls.

Security is crucial, but I'm more concerned about the data storage and ownership model. Can you provide more information on how user data is stored and who has access to it?

Regarding data storage and ownership, it's essential to consider the implications of the AAuth Person Server implementation on user data sovereignty. I'd recommend adding a section on data ownership and control to the documentation.

From an operational perspective, I appreciate the use of automated GitHub workflows to keep the documentation up-to-date. However, I'd like to see more information on the monitoring and logging mechanisms in place to ensure the system's reliability and performance.