You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to be able to publish a Leven blog as a sub-page on a website - so that using Leven wouldn't require a dedicated domain only for the blog.
I'm guessing this could be done either with a configuration option for Leven's "root path", or an option to never have absolute URLs?
My main reason for wanting this is to experiment with publishing Leven without having to redo existing pages or change top-level configuration. This would also be useful for demonstrating multiple configurations of a theme, or other demonstrations where having a domain-per-instance is not practical.
If this is already an option, could it be added to the documentation?
The text was updated successfully, but these errors were encountered:
Thanks for opening this issue! Right now Leven doesn't actually know what a URL is - it just passes slugs to templates. So there are a few options (ordered from my most favorite to least favorite):
Make all URLs relative in templates.
Add a custom config check within each template.
Make Leven actually aware of URLs and add a URL property to each template and a separate config option to set the root of each URL.
It would be nice to be able to publish a Leven blog as a sub-page on a website - so that using Leven wouldn't require a dedicated domain only for the blog.
I'm guessing this could be done either with a configuration option for Leven's "root path", or an option to never have absolute URLs?
My main reason for wanting this is to experiment with publishing Leven without having to redo existing pages or change top-level configuration. This would also be useful for demonstrating multiple configurations of a theme, or other demonstrations where having a domain-per-instance is not practical.
If this is already an option, could it be added to the documentation?
The text was updated successfully, but these errors were encountered: