hi!
right now, we have an option to display subpages in the header:
but instead of that, i’d love an option to show other same-level subpages instead, for quickly navigating between them.
yes, i know i can replicate this with buttons. but a built-in page tabs feature would be fantastic!
Hi @Swan_Song1
Can you please elaborate?
@Swan_Song1 you can get something similar by linking your pages, right clicking the link and selecting ‘Display As > Card’.
Here is the best solution:
Be happy now!
Can you please elaborate?
sure, here’s what i mean:
you can get something similar by linking your pages, right clicking the link and selecting ‘Display As > Card’.
yeah, i know, i just don’t like having to manually rebuild it each time for each page.
and while i’m aware i can create a “tab bar” as a named formula to reference on each page, the tab bar does not highlight the currently active page.
i know i can use buttons and a select control to identify the last clicked button, but it doesn’t update if you manually switch pages on the sidebar.
Here is the best solution:
Be happy now!
i do like this solution a lot and it’s the one i currently use! but i’m just not very fond of shoving entire pages into a detail view haha, it just takes up SOOOO much space!
This forum is just as good.
I have added an additional method to the doc @Kyton_Coda added.
I like using a table called Dictionary to store definitions that I want to have available repeatedly. I have expanded that idea as shown below:
I have added a Compose column, and added references to some sub pages in the document.
From anywhere in the document, you can then reference db Dictionary from anywhere in the doc, and filter to that specific row.
You could follow the same approach for say, Terms and conditions that you want in contracts, or any piece of information that you want to display often, but only maintain once.
Here is the amended doc.
If you specifically want buttons, there is a solution using an undocumented formula that will allow you to add multiple buttons in a single cell in a column. Have now tried that myself.
i like that dictionary idea, i actually have a table on my docs called “Templates” that i use to do much the same thing, along with named formulas so that i don’t have to do the table.filter(whatever) stuff every time. it still has the issue of the current page not being highlighted though 
i also do have an implementation that uses buttons and a detail view with canvases, and as much as i like my solution, i just very much do not like having to do this tbh, the code is a mess
i’m very fond of Coda’s implementation and UX for the new tabbed table views, so i hope that tabbed pages will be in their roadmap someday!
Just a note: views come with a price. Your doc size and performance is affected by (too many) views.
So, as your doc and table(s) grow, you do have to put some thought into when and where you are going to use (tabbed) views.
In the past, I kept on adding views, since this was a quick and easy way to get new perspectives on my data. But when my tables got into the thousands of rows, including sub-tables all over the place, I had to rethink this approach and I actually deleted some views that were nice to have, but not a necessity. I trimmed my doc by over 30% without deleting any data.
The same applies to columns: I created some formula columns just for display purposes (for example: RelatedCollumn.totext() ) to prevent people from clicking directly to another table. In Coda, this is done in 10 seconds, but adds a lot of ballast in large tables.
I realize the last part of this post is bit off-topic, but at the same time it touches some of the same issues as covered in this thread (tabbed views/pages)
yeah, quite honestly i don’t like that whenever we ask for basic functionality, the solution is so often to just make new tables or views with hella complicated formulas. it’s neither user-friendly nor convenient, and adds so many moving parts to a doc that can easily break.
right now, i have extra tables for templates, page tabs, row tabs for different layouts, user settings, and more.
i just wish that Coda had more default functionality for so many of the basic features that we see in other low-code notetaking apps, so that we wouldn’t have to homebrew them ourselves.
tabbed views are a HUGE step forward, and i hope they really push to introduce more stuff like that.
