Match header name to GitHub repo name

jessieay commented 9 years ago

In some cases, the guide and the GitHub repo for that guide have the same name
In other cases, they do not
This is an incremental step toward more consistent naming conventions, eg: all playbooks should be named topic-playbook in GH and Topic Playbook here
The purpose of consistent naming structures is to make it easy to find/update guides on GitHub after seeing them within the Guides website

baccigalupi commented 9 years ago

Sweet! I love your commit and pull request message too.

I don't have enough context to know how this impacts functionality though. Probably someone else should weigh in on this too.

mbland commented 8 years ago

@baccigalupi In many of the individual guides, we have to take care to keep the sidebar in sync with individual page titles; in most guides at this point, the ./go update_nav command will help with this per https://pages.18f.gov/guides-template/update-the-config-file/#register-new-pages. The critical thing is that the title of the page match exactly the title listed in the sidebar so that the little blue sidebar highlight will be generated properly for each page.

In this case, the sidebar is a launch pad to other guides, so there's not the same concern. I also think it's nice to match the title with the repo. @emileighoutlaw may have something to say about the capitalization of the titles, but we can always fix that with a follow-up PR.

jessieay commented 8 years ago

@mbland Thanks for the review/merge! :+1:

18F / archived-guides

Match header name to GitHub repo name #24