Learn about some of the core Weavy concepts, and find everything you need to know about extending Weavy with custom functionality.
Before learning how to extend Weavy it could be useful to understand understand a bit more about the low-level architecture of Weavy.
A content item is a single piece of content added to an App. Examples of content items are notes, files or folders. A content item is also an instance of something we call a content type. Said differently, content types are classes of content items.
Daemons are background tasks that run at a specified schedule.
A hook is an extension that is triggered in response to one, or more, system events.
A tool is a piece of code that is executed on demand from the management UI.
Areas and Controllers
Sometimes you might want to add entirely custom functionality that isn’t based on the Weavy building blocks. The preferred way of doing this is to add an ASP.NET MVC Area to the solution. In this area you can add Controllers, Views, Models, and do pretty much anything that would be possible with a standard ASP.NET MVC web application.