Yes, on the surface, they are similar - if not maybe even identical.
But to follow that logic, you could say that "Employees" and "Customers" and "Contractors" are all people and therefore should be in the same table, right?
Like most business problems, I won't know how things should be until I know how things should be?!
Today, I would say an "Article", an "Interview" and a "Case Study" are identical and could go in the same table since each has meta-tags and I am lumping the entire content/copy in one field.
But over time things could change.
For example, maybe an "Interview" would break up content into what the "Interviewer" and "Interviewee" say?
Or maybe a "Case Study" would necessitate breaking up the content more into sections like "Background", "Problem", "Approaches", "Final Solution" whereas an "Article" is pretty much just one thing?
Of course I am asking about these unknowns now, so that I don't choose an architecture that was poorly conceived for growth and scalability.
To me, I am leaning towards have an "Articles" table, and an "Interview" table, and a "Current News" table because things are more like to diverge than converge.
Of course, 500 tables later I may hate that approach?!