Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default theme / branding for Freemarker templates (respecting CSP header restrictions) #13

Open
aaime opened this issue Nov 4, 2024 · 0 comments

Comments

@aaime
Copy link
Member

aaime commented Nov 4, 2024

OGCAPI makes use of free marker templates that are embedded into jars. We also have the generic GeoServer theme extension point (that adds header contributions which can be used to override CSS - and thus override anything).

While the user can configure free marker templates for OGCAPI (and GetFeatureInfo)...

We do not have a programatic way to manage this:

  • What is emended in the original jars is defaults used (yes user can configure in data directory, but not developer)
  • To respect CSP restrictions it would be nice to have a similar ability to add to inject in the header as is available in wicket

I would like to combine these two points so that I can make a jar to supply overrides for OGCAPI content while respecting CSP header policy.

@aaime aaime converted this from a draft issue Nov 4, 2024
@jodygarnett jodygarnett changed the title Extendable branding with default bundles (respecting CSP header restrictions) Default theme / branding for Freemarker templates (respecting CSP header restrictions) Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant