Developing with Weavy
This article is an overview of key topics for understanding what you can do with the Weavy server SDK.
Much of the functionality in Weavy is delivered in the form of apps. Some of the built-in apps are the Posts and Files apps. It is also easy to build your own apps from scratch with the Weavy SDK.
For more information, see Apps.
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.
For more information, see Content Types.
Daemons are background jobs that run at a specified schedule. They can be used for all kinds of scheduled tasks such as reporting, cleanup etc.
For more information and details on how to implement them, see Daemons.
A hook is an extension that is triggered in response to one, or more, system events. They can be used for all kinds of stuff, e.g. implementing a conversation bot, spam filtering, sending notifications etc.
For more information, see Hooks.
A provider allows developers to replace core components of Weavy such as caching, files storage, etc with their own implementations.
For more information, see Providers.
Scrapers are used when unfurling links in Posts, Comments and Messages. Weavy has built-in link unfurling, but with a custom scraper you can easily override this and provide a custom preview of the link.
For more information, see Scrapers.
The classes in the
Weavy.Core.Services namespace contains the service layer in Weavy and is probably the code you will use most frequently when developing with Weavy.
They contain all the logic and methods required for getting, creating and updating Spaces, Apps, Content, Users etc.
For more information, see Services.