This questions is created to establish the best way to deal with separation of big context like a blog in smaller pieces.
The main problem is that a Blog context can get very big if all the schemas go under one context.
I wanted to ask if the what is your opinion on the following scenario:
Article context with schema Article and a migration Articles
This would look something like this
YourApp.Article.Article when you will need to reference the schema which might be confusing
So I thought of making the naming more descriptive like this:
Question: Is there a better way to name this modules: context and schema for easy readability?