[Shock] - Added Jinja filter called 'pathRelativeToPage' to build URLs on top of page URL (Relates to #164) #165
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.
[Shock] - Added Jinja filter called 'pathRelativeToPage' to build URLs on top of page URL (Relates to #164)
This PR doesn't actually resolve #164. When I worked on the problem, I found that the
Page
url
property was giving us just the path, e.g.,/posts/my-post/
. We don't have any official access to the root domain, so there's no way to solve #164 without first deciding where the domain name should officially live. I didn't want to tackle that right at this moment.With this approach, assuming a website defines it's own data property called
homepage_url
, a URL can be built as follows:We should still make this much easier in the future, but this is enough to unblock some other work.