jborbely

Thank you Bet for taking the time to reply. Perhaps my confusion results from the fact that I developed web sites before, where Pages were physical objects, e.g. html files.

Based on your reply it seems that in the php world Pages are similar database objects to Posts but there are differences. A Page might have zero or many Posts but a Posts can’t have any Pages. At the same time a Page might have both Posts and Comments. Furthermore, each static page can have a lot of Comments, even nested Comments.

Users can decide on which Page they want to leave a Comment. Why it is not possible to have the same freedom in deciding on which Page they want to leave a Post? Instead all Post will go – by definition – either to Home or to another Page (‘Set this at Settings–>Reading’). Than if I want to separate the Posts by topic i.e. Categories, I have to define Categories, assign them to Posts, than I have to use some plugins with which I can redirect Posts to Pages based on Categories. This for me seems to be over-engineered solution.

Users in – not always of course – smart enough to make their choice. If I had two Pages, one for ladies fashion, another one for gents fashion, a user can decide on which one to leave a Post about skirts. So I still do not understand the reason why all Posts must go to one, single pre-set Page as opposed to Comments. Any further info would be highly appreciated on this.