feat: Nag Responsive UI#6
Merged
Merged
Conversation
The Nag Responsive UI will supersede the SmartMobile UI. The current implementation achieves more than feature parity with SmartMobile UI. Route-based instead of URI parameters for rest-like experience. Largely server rendered, limited JSON/AJAX operation.
ralflang
added a commit
that referenced
this pull request
Mar 17, 2026
Release version 5.0.0-beta1 refactor(routes): migrate responsive routes to builder pattern Merge pull request #6 from horde/feat/nag-responsive feat: Nag Responsive UI
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.
The Nag Responsive UI will supersede the SmartMobile UI. The current implementation achieves more than feature parity with SmartMobile UI.
Route-based instead of URI parameters for rest-like experience. Largely server rendered, limited JSON/AJAX operation.