Pass styling through from backend/container

performant-software / neatline-spa

Single page application for Neatline mapping interface

4 stars 2 forks source link

Pass styling through from backend/container #23

Open akstuhl opened 6 years ago

feralresearch commented 6 years ago

In support of this, the CSS for the SPA has been refactored and namespaced. After build there should be a single file "main.css" bundled with the SPA. All classes/IDs inside should be prefixed with psn3

jamiefolsom commented 6 years ago

@akstuhl and @tezcatlipoca I think we decided, at @ZoeLeBlanc's suggestion, that we simply create one or more neatline themes, corresponding to one or more existing Omeka S themes. Optionally, we could investigate switching to the appropriate theme when the Omeka theme is switched, but that is optional. Correct?

akstuhl commented 6 years ago

@jamiefolsom That sounds correct. With the front-end-defined themes approach we'll still need a way of storing and retrieving the theme selection for the site/exhibit in the back-end. Maybe the best approach would be have themes be selectable per exhibit and add a 'theme' field to the exhibit schema.