* 10 was a bit much...

* add the uploader's secondary email in CC if provided by the user
* remove the option to add the inquirer's specified email address to CC,
  to avoid leaking the email addresses of the uploader
* instead, optionally send a separate confirmation email to the inquirer

* also, add a new config item `THEME_TUW_TEST_INSTANCE_URL` that will be
  used in the "final note" block in the email template
* if that value is set to `None`, then the block will be skipped
  entirely
* also, mock view function from Invenio-Config-TUW to not depend on it
  for tests

* Add links to 'My Dashboard' and preservation formats (new config item)
* Reword/fix sentences

* apparently, the previous config-based approach stopped working

* because the previously configured image didn't actually exist anymore

* their functionality can now be emulated with banners

* this behavior can be controlled via a configuration flag
* it's disabled per default because it could be used to spam the inbox
  of arbitrary email addresses

* with a default of 5 attempts per hour
* this should be enough for legitimate requests, even with failed
  attempts (i.e. captcha mismatches) but still prevent spam floods
* also, hide the contact form for users when viewing their own records'
  landing pages

* this is possible since we configured sending of emails from the
  backend
* it replaces the current implementation of "contact uploader" that
  worked via "mailto" links, which was suboptimal because it exposes
  email addresses to the public
* it is also optionally protected via a captcha as a simple spam
  prevention mechanism that also prevents accidental resubmission of the
  form on refresh

* create a config item THEME_TUW_FRONTPAGE_INFO for the content
* add a block in the frontpage.html
* apply styling

* Use 'TU Wien Research Data' as the default config value. The previous one isn't valid anymore.

* create a config item THEME_TUW_FRONTPAGE_WARNING for the content
* add a block in the frontpage.html
* apply styling

* add support for a custom warning message in the header

* because the display of the staging warning is logically a very
  separate thing from the matomo site id...

* to make it clearer which templates replace existing ones, and which
  are "new" templates

* our version was ancient and less useful than the upstream version

* the upstream versions have advanced beyond our customizations

* create a new permission guard page for creation of communities
* move the templates into their own subdirectory
* update the text on the existing deposit page guard

Closes #18

Reverted back to explicit blueprint registration, moved this functionality into before first request, substituted with dict comprehension

fix recent uploads

Moser, Maximilian authored 3 years ago and Wörister, Florian committed 3 years ago

* allows us to install a custom webpack.config.js
* copy the assets files from invenio-assets as a base
* AVIF is a newer image format than WebP with smaller file sizes -however, it is not as widely supported by browsers yet
* convert images to webp

* this allows us to control which scripts are always included on pages

* also, remove the LOCAL_LOGIN_ENABLED configuration variable, because
  that's now part of Invenio-Accounts

* override the header template from invenio-app-rdm to make the search
  button orange
* fix the wrong text color on the login button

* removed trailing whitespaces
* also, hide staging warning per default

staging banner to page template