In previous blog post we talked about how to create custom drupal entity(content entity), here are some reasonings when to do such a thing and why.
- If you are faced with having to put information into a custom table consider whether defining an entity and attaching fields to it through the Drupal APIs might be worthwhile.
- When you dont need Nodes publishing options (e.g. author, publish status, etc)
- A very simple rule of thumb I use is whether your content need to be publicly displayed on its own. If so, then go for node, if not choose an entity.
- If your use-case is similar enough to an existing entity, go with using that entity. If your entity is governed by significantly different rules than any existing ones though, create a new one.