Community guidelines
Please keep discussions civil and on-topic. Repeated violations may lead to a temporary ban.
ale rimoldi Newcomer
@ale · Joined 8 years ago · 7 posts · 2 topics · 0 reputation
Badges
Recent posts
-
On serving a site on `http://mydomain/2020/` with Grav in `2020/grav`
· 7 years ago
"For posperity" because Ole helped me find this solution in the chat. Thanks Ole!
-
On serving a site on `http://mydomain/2020/` with Grav in `2020/grav`
· 7 years ago
Sorry, this is a long post... You won't need a bedtime story tonight! Some time ago I've decided that Grav should be kept in its own directory. This means that my normal setup looks like this: /.htac
-
Reading content from an "unrelated" Github repository
· 7 years ago
On top of it, I got two times a strange session error when jumping directly to the Book. Going back to the /learn page and again to the book makes the problem disappear... Ok, probably understood the
-
Reading content from an "unrelated" Github repository
· 7 years ago
After the "Urrah" post above, here a few things, I'm not really happy about: I could not find a good way to do the routing in the plugin. Currently, I'm defining two routes in site.yaml. (https://gi
-
Reading content from an "unrelated" Github repository
· 7 years ago
Voilà, I've uploaded a proof of concept! The book (work in progress...) stored in this repository https://github.com/aoloe/scribus-book-starting-with "defined" by this project file https://github.com/
-
Reading content from an "unrelated" Github repository
· 7 years ago
A few replies : - ) the current project.yaml is just a place holder. i think that i will need multiple "project" definitions for the different targets. examples could be project-grav.yaml and project
-
Reading content from an "unrelated" Github repository
· 7 years ago
My goal is to publish multiple books/manuals inside of an existing Grav site. Each book and manual is managed as an independent Github repository and its structure is defined by a project file (json/