Discourse stripped your spacing, so it’s hard to tell what your file originally looked like! If you use three “grave accents” (```) to surround your routes file, you can preserve spacing!
It’s because in the route’s file, you’re saying I want the template to get data from the page named home, and in the template file it’s saying using the *post* you gave me, do this work. I’m not entirely sure what the optimal way to handle an issue like this is, but one method is to create a copy of the page.hbs file in your them and duplicate it to something like homepage.hbs and change {{#post}} to {{#page}} and {{/post}} to {{/page}}
If you have any info on why the cannot read "match" of undefined error, that would be super useful so the messaging can be improved! I’m glad you got it working
I’d change that message to something specific to the routes.yaml file, e.g. “You’re routes.yaml file is looking for something it can’t find. Please check its configuration.”
We’re pretty sure the error came from handlebars render If you’re willing, please run ghost log --error in your installation so we can see what exactly happened
Every theme has a different underlying structure. Your best bet is to copy vapor’s page.hbs and make the necessary changes to it.
Side note: it will probably be a lot easier to use a local installation of Ghost to set up your site, since you can make changes faster and get more verbose error information
I have two ghost blogs running on the same server. I think they’re partially sharing the same ./content folders. So, I think I was making the change in the wrong (at least as things are currently configured!) content folder. That’s why I wasn’t seeing the changes.