What blog architecture should I use on MODX?

Question

MODX

Tell me, please:
- how to properly build the architecture of processes so that you can display content by category on a separate page using filtering by tags. Preferably on MODX. At this stage, I am trying to build an algorithm of actions so that everything is correct, and I plan to refine the technical nuances in the implementation process.

I see it like this (in modx):

Admin panel :
- in the admin panel I create additional tv-fields in the page template (author and category of articles)
- I create a resource (page)
- I put the name "author" and "category name" in the fields
- for categories and for each author also, as I understand it, you need to create separate

PhpMyAdmin resource pages :
- I create a table with the fields "author" and "category name"
- somehow I call the content by ID, while identifying these fields

I'm not strong in the backend, please help.
Thank you in advance.

I am attaching the diagram:

Answer 1

Option number 2: I would not put on Tickets (so that there are tickets - not resources - there are enough reasons for this), in general, Regular resources + pdoTools and Tickets if you need a commenting form that saves comments to the database.
Option 3: Minishop2+pdoTools+ whatever. Despite the fact that Minishop2 was created to create stores, it can be customized (it is unnecessary to turn it off, etc.) and make a full-fledged blog on it (where, unlike the above options, articles can be added to several categories at once, there is tagging already out of the box , links, etc.) + add msearch2 and there will be filtering without unnecessary dances with tambourines.
Regarding the authors of the article: it’s not better to set up separate accounts for each author and then automatically display the author - something like this)

Answer 2

Tickets+pdoTools