Skip to content

Presentation materials for the Docs Thursday presentation at @futurice

License

Notifications You must be signed in to change notification settings

jamesstoneco/docsthursday

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 

Repository files navigation

Docs Thursday Presentation Materials

Promotional poster with time of event and catchphrase these docs need your love

Table of Contents generated with DocToc

Slides

Resources

With 25 years of experience writting developer documentation, McKinney provides motivation, strategies, and practical applications for writting developer documentation. He introduces the 2 audiences for developer documentation: contributors and users with an emphasis on the latter.

Altough this might be a bit to verbose for starter documenation, as it perhaps focuses on contributors, it has some great advice about what should be in a readme file and how it should be formatted.

A review of 46 polled open source projects, from small home-grown to very large projects. Some key takeaways are most projects are concerned with conributor experinence, the community of the static site gen, and automation. Interesting was that language was not a preference but rather having a less steep learning curve was key. Most projects interviewed cited that they were happiest when using a variety of tools that fit their specific needs.

TODO: write summary

Podcasts, Confrences, Slack Community of Techinical Writers. A huge amount of resources.

If you are not a developer, this provides a good walkthrough for setting up github pages / jekyll. Video and demo are targeted towards Technical Writers at the Write The Docs conference.

In this video Beck did a survey of over 200 public opensource readme files from projects with over 10k stars on github, projects he was familair with, and some closed source readmes. Bias is towards established popular products.

A series of the 4 ways to build confidence in your users from a readme, described in the talk Write the Readible Readme, that you can easily go through to evaluate your current readme and where it could use some love.

Tools

Created by the Facebook Opensource Team to create a simple way to document projects.

Generates a Table Of Contents for markdown files automagically. Important flag: --github

A tool that will automatically add all of the contributors from a file to your project readme file.

Great project for documenting react projects with mdx. Also a great example of good documentation.

A free but add supported way to automatically build and host your docs. You can use standard markdown files in a docs directory and you will need to use python to configure initilaly.

About

Presentation materials for the Docs Thursday presentation at @futurice

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published