On Tue, 2018-10-30 at 13:18 -0400, Jason E Bailey wrote: > On Tue, Oct 30, 2018, at 5:50 AM, Robert Munteanu wrote: > > Hi Jason, > > > > On Tue, 2018-10-23 at 12:00 -0400, Jason E Bailey wrote: > > > 1. Creating a resource provider to use as the default resource > > > provider for the starter installation > > > 2. Define a Resource > > > 3. Define a Resource Type hierarchy > > > 4. Convert all generated HTML to HTML5 standards > > > 5. Fix the website > > > > Can you add some more information about 1-3? Are you looking to > > build a > > custom resource provider specifically for the starter? > > For 2 and 3. > Well 2 is better then what it used to be we actually state what the > resource needs to supply, but there's gaps around the concept of > resourceType, and when a specific type is needed or not. Some of this > comes from me working on a resource provider. Should all resources > have a resourceType? Our code defaults to the node type if a resource > type isn't defined. I think there's an argument that we shouldn't do > that and that by default all resources should have a resourceType and > a resourceProvider should add one if it hasn't been defined. > > That's where we go into the concept of a resource type hierarchy and > a type structure.
Just to try and understand this better - you're saying that instead of Sling falling back to the jcr:primaryType property in case of JCR resources, the JCR resource provider should instead synthesize that property itself, even if it does not exist? Robert
