Begin fixing landing customization #148
Open
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
There is a surprising amount of content that depends on
$.Site.Data.landing. This is bad and should be removed or made to use something default-but-changeable This changeset does exactly that. I've also reworked the way that iamge compare is checked for, which makes it possible to use it in the body content as well later as a shortcode.This also begins the process of making all scripts fingerprintable for SRI.
TODO:
$.Page.Scratch.Getand related.Changes
landing.yamltolanding_default.yaml-> This should actually be indata/lotusdocsto namespace it away but I didn't want to make any sudden movements.$.Site.Data.landingto one.fixes #143 and future-proofs it a bit.