How Can I Organize a Nintendo Gaming Content Database in Airtable?

Generally speaking, the best structure is to keep as much as possible in one base, with separate tables for each type of data object. Then use linked records between tables to connect data objects.

When I say data object, I basically mean a piece of information that needs to contain more information within it. So sometimes something might be better as a field when you only need some information about it and sometimes it should be it’s own table. As an example, consider a phone number. If all you need is the phone number, it’s a field within a table. If you need to express that the phone number is cell or landline, it becomes a data object and might be it’s own table.

It might be worth checking out some of Airtable’s templates for inspiration, stuff like the Content Calendar or Content Studio templates.

Just off the top of my head, I would probably have a table for games, a table for articles/content ideas, but SEO keywords would probably be a field in the article table.

Having separate tables will serve you better than one giant table with a Type field.  A solid base would include a “Content” table for guides/articles/news (distinguish them by Content Type).  Also have a “Games” table for the Tomodachi Life and 3DS titles.  Finally a “Characters” table and a “Keywords” table to complete your base.

This way you can link Content to Games, Characters and Keywords as you need them since a single guide might reference multiple characters or target multiple keywords.  Publishing status and content ideas don't really need their own tables but simply a Status field in “Content” that can be something like Idea, Drafting, Published, etc. You can create views that are filtered off that field.  This will help keep everything connected without unnecessary duplication.