Add htmx example - #53
Merged
Merged
Conversation
added 10 commits
July 26, 2026 10:00
# Conflicts: # project/Dependencies.scala # project/build.properties # project/plugins.sbt
Contributor
Author
|
Added usage of |
Contributor
|
Thanks! This is great! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello!
I would really like to make Krop more accessible, so I want to improve the documentation.
While Krop offers powerful abstractions for building web applications, the lack of comprehensive usage examples makes it difficult for developers to understand how to apply the framework in practice. By providing a complete, real-world authorization application with HTMX integration, this example serves as one of a practical learning resource that demonstrates Krop's core concepts in action, making the framework more approachable and accessible to newcomers.
I believe that adding such examples is essential for Krop's adoption and growth. 😉 Clear, runnable examples help backend developers quickly grasp Krop's patterns and idioms, significantly reducing the learning curve. This is particularly valuable for teams building applications with frontend requirements.
Could you please review this MR to make the documentation more comfortable for the newcomers?