Article Database?

There you go! I didn't think about pagination, but yeah my idea is probably useless without it. Next idea...

.
The reason I was thinking about this is for B2B website product pages.
Typically we make each product page with tabs for various information.
Description, detailed features, screenshots, demo videos, specifications, contact form, etc.
While this works, it is hard for the client to maintain without help.
The tabs plugins confuse them.
Working in code requires a level of expertise.
And sales people invariably want to link directly to the individual tabs so they can point customers to the exact information.
All of these issues create maintenance and operation problems.

So this discussion sparked my imagination.
What if the product page was a category, and the tabs are actually different items.
Then the different item pages (or tabs) could be different FLEXIcontent content types which the clients could easily edit and maintain.
All items (tabs) could have a unique URL.

Another way to do this (which you will see all the time on B2B websites) is to create pseudo-tabs by cloning and repeating the tab portion on each page.
To the user it looks like a tabs but it is actually multiple pages.
Again, this is difficult for a client to maintain.

If there were a FLEXIcontent category view which could display the category items (or articles) as tabs, we could create content types for each "tab" item which the client could easily maintain.
Add an item and it creates a tab.
Delete an item and the tab is gone.
This would eliminate another common issue where the default tab structure must be edited to add or remove certain tabs.

Pagination would not be an issue.

I wonder if I am looking at this backwards.
What if the item pages could have a zone or field plugin which would display the tabs?
Each tab would be the other items in that same category.

Or perhaps the tabs plugin could link the items via a tag?

Obviously I am thinking out loud here . . .

So there is my "category item tabs" fantasy.



.