Thank you again for your input 
I hope you don’t mind this noob answering…
Neither did I, I’m not an M$ guy Only C and C++ …
I’ve been using the IArticle naming convention merely to prevent coding errors due to name space pollution, as a help for typing in VS Code such as:
export interface Article …
export interface Articles …
public articles$ …
private articles …
private articleArr …
…
Whenever I type “I” and press TAB it comes correctly.
The reason I’m keeping in a separate file is because they are included in multiple components and any change in the structure will be made in one place.
In this specific application I’m struggling with, I have 3-4 common Interface files, and each module may have its own interfaces. E.g. Article is common, Book is in library module.
I actually read your posts about this last month, also examined (tried) a lot of other methods which do compilation on the fly (on an older version of Angular) etc.
What I could not convince myself is this:
Say I have 10 different Article Layouts as components
Say I have 10 different Module Layouts as components
If I have a PageLayout component, which would include all of them and use one or two with *ngIf in the template, that would become a huge component. I don’t know how much it would hurt in a PWA (and running on mobile) thou…
If I cannot do it correctly, probably I’ll go back to that…
Nope, I did not suggest that. But after I had issues with Observables, I tried to convert them to see what happens. I’ve been already using your skeleton-bone style with @Input…
That would most likely go to normal if I ever solve this Observable mix-up in my brain…