Understanding when to use a module.
Created 7 years ago by gwerner

I'm working on implementing a basic home page slider. I'd like to be able to control the text and images used in the slider from the admin. Is a module the best place for this? It seems like any time there is a database interaction then a module is where I would start. Does Pyro v3 still adhere to Modules for database interaction, Plugins for front-end access? I'm still digging into all this and am about half way through the module videos. So far, so good. But wanted to get verification on this. Thanks.

ryanthompson  —  7 years ago

You got it! Extensions and modules are installable so can run migrations. Another good indicator a module is needed is if you want to interact with it via the control panel. Moduleshave sections with buttons that help build out areas in the control panel.

Extensions are a wild card so that's for another day. Plugins are for view layer functionality. Themes are self explanatory and field types are your data transport machines. They handle data from input to storage to output and decoration.