Need more information for that. What do mean by recipe post ? Where your data will be stored ? How many recipes you want to provide ? What actions would you like to provide to your users ? Is there a form ? Is there other informations than recipe that you would like to show ?

I would like to create a food web site. The recipe post is a document type which would have a numeric field in which I want to store a number of user total page views.

Each time someone opens a recipe post on the website I should update that field. Every time programmatically republishing a node page could be a bad practice and speed concern.

I don't know is there a better way, maybe using content apps or creating a custom table to store node Id of a particular recipe and pageview increase for 1?

There should be more than 1000 recipes niche specific for pku people.

The recipe document type should consist of:

• Cooking time, Servings, Difficulty

  • Ingredients as nested content (ingredient quantity, measure, Ingredient name)

  • Cooking steps as nested content (picture, step description)

  • Additional notes

  • Nutrition info

  • There won't be any form, maybe just facebook comment plugin.

I see basically 3 ways to solve this:

1. Use document types, to give you an example I had a tree content of ~5000 nodes for a project that involved creation, select and update (never delete) and I didn't had any performance issue for ~50-100 simultaneous users.
2. Use the library of Tim: https://our.umbraco.com/packages/developer-tools/ui-o-matic/ that will provide all you need to store data as custom table (orm, backoffice page, etc..)
3. Do it custom

I would personally suggest the second as If for a reason you have to move to an other cms or else, your database structure won't be affected. But you would need to check if nested content is easy to implement (may be informative: https://our.umbraco.com/packages/developer-tools/ui-o-matic/computer-says-no/73449-listview-within-listview)

is working on a reply...