I have been experimenting with Fastpages over last few days. Today I managed to create a partial integration of netlify cms with my blog . Good thing about the setup is
Workflow based on pull request for draft post
Ability to do some editing directly from mobile. ( useful for those long commute to work)
I am wondering if some of these things can be adopted in different ways to future versions of fastpages. I espically like idea of automatic pull request to merge a finished post in netlify cms
I have no programming or web dev experience, but I want to understand what’s going wrong?
I changed the build command in netlify to make server but then the build fails.
Would appreciate your response
I think you have not updated your baseurl. Css is looking for path at wrong url. Please change your baseurl in _config.yml and settings.ini as suggested. Welcome to world of programming. I made same mistake initially
Yes. Why don’t you post a link to your repo if it’s open. I can do a quick check tomorrow. You can also check fastpagesdev.netlify.app. repo is rahuketu86/Fastpagesdev on github. This is my test repo. You can do a quick look at config.yml
I have my site on a private repo. Mostly as a precaution in case I get a question from work. However i have made an exact replica of setup on test repo shared above. I also have a fork of fastpages which has cms and org pages built in rahuketu86/fastpages. But even then you still need to fix url in config.
Setting should work either way for blog site either or github or netlify.
Reason it doesn’t work on both is because being a static site you generate all the links by supplying a baseurl. It is rendered by liquid template in your page layout and header with {{ site.baseurl}} expansion.
So you have to choose one. In some dynamic apps with server / react you can link it based on some dynamic values provided by a api call or callback
If you render gh-pagws branch by mapping to netlify it won’t work. However if you take the build step also in netlify you can probably make it work on both but you will have to modify your github action . Add an addition transfer step as done @hamelsmu before your jekyll build step and do the same build on netlify. But why bother. It will break your upgrade in future