I would like to mimic how larvel.com documentation on our website. I see that the soruce is at https://github.com/laravel/docs can anyone please point me to how this gets build and deployed? Is it using mkdocs or Sphinx? I am interested to see how the headers, navigation and theme of the site is preserved in auto-generation docs.
@smarru As far as I know, the documentation is written by Taylor and the community; I don't think a package was used. AFAIK Jack McDade designed the site.
@deringer that doesn't generate the documentation, that's just a glorified TOC.
I see that the soruce is at https://github.com/laravel/docs can anyone please point me to how this gets build and deployed? Is it using mkdocs or Sphinx?
The fact they mention MkDocs means that they are indeed looking to automatically generate documentation (as a whole) not just the front page (table of contents).
Thank you all for all the insights, its very helpful. To clarify, we have a laravel based portal (https://seagrid.org/) and have styled the theme. For the documentation tab we currently take the users to a confluence wiki. Rather I would like to get the documents written in markdown and deployed as static html. Jekyll, mkdocs like tools help me go from markdown to html. The unknown to me is how to use the static header and footer so users do not feel they are in a different land for documentation.