Is there a good way to add a field to a custom layout that would allow me to use a non-item image as a background/banner?
I'm attempting to recreate the basic look of a physical exhibit we have here in the library. A lot of the panels in the original have borders -- interesting patterns, a chunk of map, etc -- that don't need to be (and in some cases shouldn't be) items in the Omeka archive. Is there a way to pull those images from the server directory rather than making them public items that have no context outside this one exhibit?
I'd rather not have to create layouts specifically for each page that can never be re-used, but I will if that's the best way to go about it. Ideally, I could just add a field or two to the layout and paste in the URL for the desired image.
Sure, you can add non-item images in the "images" directory in your theme. You can include those images in the CSS for the theme you're using, and if necessary, create some new classes to correspond with your design.
I probably should have been more specific.
My question is about individual page layouts within Exhibit Builder, rather than the whole exhibit or site. For example, within the EB version of this page:
the pattern at the top would be better as a direct pull from the site directory, whereas the other images should be items within the public archive. Should I just use a text field in my layout and insert the image there, or is there a better way to go about it?
Other than the images, are your layouts basically going to be the same from page to page?
If you're going to have to use different layouts for every page anyway, it's probably best to just include the images directly in the layout.
If the header image is the only thing standing in the way of making the layouts reusable, then a text field sounds like a reasonable workaround, as long as your layout is written to expect the image there.
Well, only one or two of the layouts will be reused in this particular exhibit, but I'd like all of them to be reusable for future exhibits so that I don't have to keep reinventing the wheel.
(Hopefully, I won't always be the only one creating our exhibits. I'd like to make the process as easy as possible for people with even less coding knowledge than me.)
Sounds like a text field is the way to go. Thanks for the advice.