omeka-s-developer
omeka-s-developer copied to clipboard
omeka
Documentation for Omeka S developers
Github now allows you to use actions that could create a release and attach a zipped version of the module for you. Putting an example action in the documentation (`docs/register_an_addon.md`)...
Even though I had read the documentation, I was still confused/surprised by the behavior. This might make it more explicit? See also https://github.com/omeka/omeka-s/issues/1719 :)
Should cover: * How to create theme configuration fields in theme.ini * How to access theme configuration values and assets in the views
We have _some_ of this in the API page but we should have a page that has every possible parameter.
I set up my routes and navigation in `module.config.php` and couldn't figure out why they weren't working until I was advised to include `getConfig()` in `Module.php`. I don't think we...
When I was thinking about using external libraries with my module, I couldn't find any documentation on best practices for including them.
When I was writing CSSEditor and reading the Events documentation, I couldn't discern what class identifier(s) to use with `view.layout`.
This https://github.com/omeka/omeka-s/issues/852 should be added for module writers