The only middle-way sort of solution I found a long time ago, even before joining the company, while looking where to host https://jdsalaro.com was to use GitLab, they being open-source and quite public about their, now our, values.
Nowadays I'm planning on writing again and have tried a setup that seems to be alright:
- migrate from Pelican to Hugo since the community is more vibrant, responsive and the themes much more mature and well maintained.
- Use a mature, well-maintained documentation-oriented template as base (I based https://jdsalaro.com off Pelican's bootstrap3)
- Create an Obsidian vault out of the posts/ directory to improve note-taking and editing capabilities.
- Host same as before on GitLab
- Deploy via CI/CD copying the posts/ directory to a public repository
- Probably mirroring to GitHub
I'll be able to report back once I've gotten the above fleshed-out :)
Nowadays I'm planning on writing again and have tried a setup that seems to be alright:
- migrate from Pelican to Hugo since the community is more vibrant, responsive and the themes much more mature and well maintained.
- Use a mature, well-maintained documentation-oriented template as base (I based https://jdsalaro.com off Pelican's bootstrap3)
- Create an Obsidian vault out of the posts/ directory to improve note-taking and editing capabilities.
- Host same as before on GitLab
- Deploy via CI/CD copying the posts/ directory to a public repository
- Probably mirroring to GitHub
I'll be able to report back once I've gotten the above fleshed-out :)