In this issue, I note the things about inheritance which should not get forgotten.
By this I don't mean they shouldn't be forgotten to implement for first release, but not being forgotten as use cases and general behavior for possible future implementations. So in this state it might be important to know about theses cases.

1. Detecting the parent page of the area content should be using the model hierarchy and not the physical node hierarchy:
Now that an area has a definition, it can be rendered from any other template script -> getting to node and render it.
To collect the content from the parent pages, the parent page of the area should be the parent by the model hierarchy.
Otherwise it will always inherit the content from the physical structure and not from the rendered page and its parent pages.

2. STK scope prototype&concrete template.
What should happen, if the prototype is not defining a inheritance on an area, but a concrete template does (for example an article)?
When defined on the prototype its clear, every page inherits the content form the parents in this area.
When defined only on an article does that mean:

• The article inherits its content down to all subpages?
• Or the article gets all the content from the pages above? -> all subpages of an article being not a article wouldn't have inherited content.
  Now how its defined in stk: you tell a element (in extras for example) inherit to subpages. Marking only on article template a complete area to be inherited, I would expect the same behavior -> inherit all down.