How does Articulate /blog manage to render given there is no default template for the Articulate Doc Type?
I normally see a default template or a selected template for a Document Type so that umbraco knows how to render the page. There is no Template defined for Document Type "Articulate" associated with the "/Blog" url - so how does the umbraco run time determine what template to run to render the page?
I know there are 4 themes for articulate - but how is the plumbing put together so that the selected theme pointing to App_Plugins\Articulate\Themes is actually run?
How does Articulate /blog manage to render given there is no default template for the Articulate Doc Type?
I normally see a default template or a selected template for a Document Type so that umbraco knows how to render the page. There is no Template defined for Document Type "Articulate" associated with the "/Blog" url - so how does the umbraco run time determine what template to run to render the page?
I know there are 4 themes for articulate - but how is the plumbing put together so that the selected theme pointing to App_Plugins\Articulate\Themes is actually run?
I've never seen this behaviour before in umbraco.
Articulate uses route hijacking for it's document types and then proxies to the correct theme folder for it's views.
For example, the rich text document type and the markdown document type both inherit from this controller and this is how the view is rendered https://github.com/Shazwazza/Articulate/blob/master/src/Articulate/Controllers/BlogPostControllerBase.cs#L13
The rich text controller is here https://github.com/Shazwazza/Articulate/blob/master/src/Articulate/Controllers/ArticulateRichTextController.cs
and is named ArticulateRichText which matches the document type name, this is how route hijacking works. There are docs on that here https://our.umbraco.com/Documentation/Reference/Routing/custom-controllers
is working on a reply...