3 ms·
Great work, thank you for sharing this. I see an opportunity for you to create tutorial steps, to teach a developer step-by-step what an input repo should cont
by jph 5y ago
Great work, thank you for sharing this. I see an opportunity for you to create tutorial steps, to teach a developer step-by-step what an input repo should contain in order to output "Hello World". Perhaps this is as simple as an example repo that contains a couple of files such as example.md and example.css?
- symkat 5y agoThanks! I have some examples on markdownsite.com in the middle, I’ll post them here as well, thank you for asking: https://github.com/symkat/mds-example.markdownsite.net https://github.com/symkat/mds-example.markdownsite.net - A static website made from markdown files https://github.com/symkat/hugo-example.markdownsite.net https://github.com/symkat/hugo-example.markdownsite.net - A static website made with Hugo https://github.com/symkat/os-example.markdownsite.net https://github.com/symkat/os-example.markdownsite.net - A hand-rolled website with HTML/CSS The websites for each can be seen at their respective domains: https://mds-example.markdownsite.net/ https://mds-example.markdownsite.net/ https://hugo-example.markdownsite.net/ https://hugo-example.markdownsite.net/ https://os-example.markdownsite.net/ https://os-example.markdownsite.net/ I absolutely want to get the docs more cleaned up and make understanding how to get a site running something effectively communicated. Right now I have this https://markdownsite.com/docs https://markdownsite.com/docs explaining some stuff. Thanks again!