You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current method of providing the chapters is with PDFs, which is good too. But we can build a better UX by hosting a documentation site using static site generators (say Docusaurus). This will allow us to build rich features like back links, beautiful design etc. Since GitHub allows hosting static sites for free, it won't add any friction to the workflow.
Problems
Surfing an online site with good design is better than downloading chapters as PDFs.
Additional Context
I have seen organizations do this for their code base documentation.
Eg: The Palisadoes Foundation (the organization with which I completed my Google Summer of Code), uses this for hosting their documentation
The text was updated successfully, but these errors were encountered:
Course Details
GitHub
Description
The current method of providing the chapters is with PDFs, which is good too. But we can build a better UX by hosting a documentation site using static site generators (say Docusaurus). This will allow us to build rich features like back links, beautiful design etc. Since GitHub allows hosting static sites for free, it won't add any friction to the workflow.
Problems
Surfing an online site with good design is better than downloading chapters as PDFs.
Additional Context
I have seen organizations do this for their code base documentation.
Eg: The Palisadoes Foundation (the organization with which I completed my Google Summer of Code), uses this for hosting their documentation
The text was updated successfully, but these errors were encountered: