In DIYHub we categorize posts when we curate them with a 1:1 category relation.
We use MySQL for our curation database and I imagine a folder-like structure for users to explore the community on a dedicated page.
by clicking on one of those they get to another level where all the specific categories are listed.
This is just an idea - if a tree is easier to implement I think that would work too.
Our database:
Table "curationChoices"
postAuthor
postPermlink
category
Table "curationCategories"
categoryShort
categoryLong
mainCategory
The relation between both tables is via category <> categoryShort ( I know I should have used the id ;) )
We could create a database view where the postAuthor is combined with the postPermlink and the mainCategory+categoryLong are already joined.
In the best case there is a new admin part:
enter the curation database system (MySQL, ms SQL, etc.)
In DIYHub we categorize posts when we curate them with a 1:1 category relation. We use MySQL for our curation database and I imagine a folder-like structure for users to explore the community on a dedicated page.
by clicking on one of those they get to another level where all the specific categories are listed.
This is just an idea - if a tree is easier to implement I think that would work too.
Our database:
The relation between both tables is via category <> categoryShort ( I know I should have used the id ;) )
We could create a database view where the postAuthor is combined with the postPermlink and the mainCategory+categoryLong are already joined.
In the best case there is a new admin part: