Sprint 1: MVP of documentation site

[smit1678]

Develop initial working version with content from Toolbox or Refugee Mapping Toolbox to test ideas and review.

[russbiggs]

Workplan

• Experiment with Hugo templates and features based on 3/18 meeting
• Research for additional topics from 3/18 meeting (search, image processing pdf generation) _in progress
• Develop MVP with hotosm/toolbox wiki content in progress
• Begin documentation of lessons learned from initial development

Items needed from @smit1678 :

• Edit permissions to https://github.com/hotosm/toolbox/wiki markdown for development
• github repo for toolkit site
• github repo for template edits (I've init'ed a git submodule so I can VC any customizations) maybe named hotosm-hugo-book or similar?

[smit1678]

Edit permissions to https://github.com/hotosm/toolbox/wiki markdown for development

done, https://github.com/hotosm/toolbox/invitations

github repo for toolkit site

done, https://github.com/hotosm/toolkit-site

github repo for template edits (I've init'ed a git submodule so I can VC any customizations) maybe named hotosm-hugo-book or similar?

done, https://github.com/hotosm/hugo-book. can we give it a catchy name? :)

[russbiggs]

I've pushed the base template to https://github.com/hotosm/hugo-book. I'm wondering if we should just do a proper github fork in the HOT organization. Not sure if there is any benefit one way or another. Any thoughts @smit1678?

[russbiggs]

@smit1678 Can you set up a github repo for the base platform template (to hold hugo structure, CI config, README with how-tos etc.) Maybe named 'hot-docs-template'

[smit1678]

@russbiggs Done ✅ https://github.com/hotosm/hot-docs-template

[russbiggs]

MVP is up here:

https://hotosm.github.io/toolkit-site/docs/

The routing is still a bit funny on gh-pages and it requires a bit of git fancy footwork. These can be ironed out in the upcoming sprint.