Repository navigation
Top tabs instead of the module sidebar - #328
Open
ifahimreza wants to merge 1 commit into
Open
ifahimreza wants to merge 1 commit into
ifahimreza wants to merge 1 commit into
Conversation
A module's sections are the header's tab row (Settings last), the way a Core page's tabs already were. A section's pages are links at the top of the content (PageNav), not a white band of tabs. There is no sidebar of Saddle's own beside WordPress's menu any more. Every page is one aligned column: the header's content, the paused strip and the footer pad onto the page's width (--saddle-col), so the breadcrumb, the tabs, the page and the footer start at the same edge. Modules use the 960px page width. Fahim, 2026-10-05: "sidebar make site ugly ... why not we make nice". Sibling modules need no change: they register the same screens. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
Fahim, 2026-10-05, with screenshots of CRM and Analytics: "sidebar make site ugly ... why not we make nice". Every module page had two menus side by side (WordPress's and Saddle's 200px section sidebar), a wide gap before an 880px column, and a band of page tabs that didn't line up with the header. He chose top tabs, like Kit.
What changes
sectionTabs()). This is the row Core pages already used.SectionNavand the.saddle-moduletwo-column layout are gone.PageNav, replacing the white tab band). They are real links: a middle click opens a new tab, a plain click stays in the app. The current page is the "raised" chip the sidebar item used.--saddle-col), so the breadcrumb, the tabs, the page links, the content and the footer all start at one edge. Modules use the 960px page width (Home stays 1040).tabandsub.admin/DESIGN-ALIGNMENT.md: the frame, F2, F4 and the Navigation section are rewritten, with a History entry.admin/build/is not committed.Checked
sectionTabsreplacessidebarItems),lint:jsclean, build OK. No PHP changes.localhost:8883):&tab=settings&sub=emails, and Back and Forward.Not here
Analytics draws a card inside a card on Visitors and Reports (its own screens). That's a follow-up in saddle-analytics.
🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.