Current CTO exploring entrepreneurship on the side; coach; mentor; instructor.
Dedicated to promoting digital literacy and ideological diversity in tech.
If you're looking for hosting mostly content, you can't go wrong with Jekyll (jekyllrb.com).
Then, instead of pulling your content from an API, you host your content in git as part of your blog and deploy new pages using automated build triggers in whatever git provider you use.
Github becomes your CMS, and editor! You can blog/write content in Markdown in whatever editor you like and push to github to be automatically deployed, or you just do it manually from the github web interface.
You can then integrate whatever tooling you want into github(or bitbucket, etc) to manage your workflow to suit your needs.
Current CTO exploring entrepreneurship on the side; coach; mentor; instructor.
Dedicated to promoting digital literacy and ideological diversity in tech.
Well in this case Jekyll becomes your cms and static site generator. You wouldn't pull your posts from Jekyll and then display them somewhere else.
As for the customizations, thr markdown is converted into HTML and css in the browser. You would use the same tools as you would any other static site. You could work from existing Jekyll templates, or create your own from scratch as needed.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If you're looking for hosting mostly content, you can't go wrong with Jekyll (jekyllrb.com).
Then, instead of pulling your content from an API, you host your content in git as part of your blog and deploy new pages using automated build triggers in whatever git provider you use.
Github becomes your CMS, and editor! You can blog/write content in Markdown in whatever editor you like and push to github to be automatically deployed, or you just do it manually from the github web interface.
You can then integrate whatever tooling you want into github(or bitbucket, etc) to manage your workflow to suit your needs.
If you use Jekyll, would you let
_post/folder to contain more than hundred of files? Wouldn't that be hard to query?Also, how would you customize markdown?
Well in this case Jekyll becomes your cms and static site generator. You wouldn't pull your posts from Jekyll and then display them somewhere else.
As for the customizations, thr markdown is converted into HTML and css in the browser. You would use the same tools as you would any other static site. You could work from existing Jekyll templates, or create your own from scratch as needed.