Dear KeyCloak team, In the last days I worked intensively with KeyCloak, trying to check if it fits as a solution in a current project and I was suddenly aware of the big potential still hidden in the software. The problem is, that these capabilities can be understood only after hours of experimenting and I was able to appreciate the vision behind it. There is not too much trace of the vision in the documentation, which is not bad, but it does not tell you why some feature are there and how to better make use of them. So, a kind request: can you publish some document telling why you decided to implement a feature? These contributions don’t need to be extensive, it gives just us a glimpse of the gold buried in the project. A road map or a list of features under evaluation could be very useful too. Thank you, Giovanni _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user

Dear KeyCloak team, In the last days I worked intensively with KeyCloak, trying to check if it fits as a solution in a current project and I was suddenly aware of the big potential still hidden in the software. The problem is, that these capabilities can be understood only after hours of experimenting and I was able to appreciate the vision behind it. There is not too much trace of the vision in the documentation, which is not bad, but it does not tell you why some feature are there and how to better make use of them. So, a kind request: can you publish some document telling why you decided to implement a feature? These contributions don’t need to be extensive, it gives just us a glimpse of the gold buried in the project. A road map or a list of features under evaluation could be very useful too. Thank you, Giovanni _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user

Dear KeyCloak team, In the last days I worked intensively with KeyCloak, trying to check if it fits as a solution in a current project and I was suddenly aware of the big potential still hidden in the software. The problem is, that these capabilities can be understood only after hours of experimenting and I was able to appreciate the vision behind it. There is not too much trace of the vision in the documentation, which is not bad, but it does not tell you why some feature are there and how to better make use of them. So, a kind request: can you publish some document telling why you decided to implement a feature? These contributions don’t need to be extensive, it gives just us a glimpse of the gold buried in the project. A road map or a list of features under evaluation could be very useful too. Thank you, Giovanni _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user

Dear KeyCloak team, In the last days I worked intensively with KeyCloak, trying to check if it fits as a solution in a current project and I was suddenly aware of the big potential still hidden in the software. The problem is, that these capabilities can be understood only after hours of experimenting and I was able to appreciate the vision behind it. There is not too much trace of the vision in the documentation, which is not bad, but it does not tell you why some feature are there and how to better make use of them. So, a kind request: can you publish some document telling why you decided to implement a feature? These contributions don’t need to be extensive, it gives just us a glimpse of the gold buried in the project. A road map or a list of features under evaluation could be very useful too. Thank you, Giovanni _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user

Dear KeyCloak team, In the last days I worked intensively with KeyCloak, trying to check if it fits as a solution in a current project and I was suddenly aware of the big potential still hidden in the software. The problem is, that these capabilities can be understood only after hours of experimenting and I was able to appreciate the vision behind it. There is not too much trace of the vision in the documentation, which is not bad, but it does not tell you why some feature are there and how to better make use of them. So, a kind request: can you publish some document telling why you decided to implement a feature? These contributions don’t need to be extensive, it gives just us a glimpse of the gold buried in the project. A road map or a list of features under evaluation could be very useful too. Thank you, Giovanni _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user

Dear KeyCloak team, In the last days I worked intensively with KeyCloak, trying to check if it fits as a solution in a current project and I was suddenly aware of the big potential still hidden in the software. The problem is, that these capabilities can be understood only after hours of experimenting and I was able to appreciate the vision behind it. There is not too much trace of the vision in the documentation, which is not bad, but it does not tell you why some feature are there and how to better make use of them. So, a kind request: can you publish some document telling why you decided to implement a feature? These contributions don’t need to be extensive, it gives just us a glimpse of the gold buried in the project. A road map or a list of features under evaluation could be very useful too. Thank you, Giovanni _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user