We started a book club! Each week we host a Twitter chat on Thursdays to discuss a chapter of Docs for Developers.
On Thursday Dec. 30th we had our 6th Twitter chat, hosted on the @DevEdBookClub Twitter account about Chapter 6.
This post is a recap of the chat and a place to continue the conversation.
What docs have particularly good examples of visual content?
What do you like about them?
Dvkr gave a shout out to the comics that are found in React’s new beta documentation. They enjoy how the comics personify React.
What are your favorite visuals for learning new content?
What’s your workflow for creating visual content? At what point in the writing process do you add them?
What tools do you use?
Do you have any questions about creating visual content that this group might be able to help weigh in on?
I shared that my workflow changes depending on the content. Sometimes I start with a visual and create content around it. Other times I leave the visuals for the end. I also mentioned I enjoy using Figma and Affinity designer to create visuals that are SVGs. Some of the visuals I create I like to animate and SVGs make this easier to accomplish.
I use Procreate when creating an image.
Valeria@vlrmigova@DevEdBookClub Q2) I love to use online whiteboard Weje. It allows to manage multiple projects and visualize a workload in easy way. Also It suits perfectly for brainstorming, creating mood boards, kanban boards, teamworking.05:25 AM - 31 Dec 2021
Aisha and Portia both admitted they have a hard time creating visual content. Aisha likes to commission illustrations when possible. Portia tries to draw something on paper first and then uses tools like Miro.
Do you have a preferred workflow? What tools do you like to use to create visuals for your documentation?
What takeaways from this chapter can you apply to your own documentation practice at work?
Any quotes or ideas that resonate with you?
Sarah Rainsberger had two favorite takeaways. First, she liked the message “Simplify to Amplify". Visuals can be really helpful but can also be very distracting.
Second, she appreciated the reminder that screenshots aren’t always the best option. They lack text for screen readers. Use in your documentation only when they are the best option.
Sarah Rainsberger@sarah11918@DevEdBookClub @DevEdBookClub A3. And, I liked the reminder that a screenshot is great, but the text isn't available for copying that way, so pick WHEN a screenshot really is the best tool. (That said, where's the font where inner brackets ARE SMALLER, like I can hand write??) #DevEdBookClub03:17 AM - 31 Dec 2021
Portia added she would have liked a section in the book that talked about maintaining visuals. A lot of documentation sites struggle with keeping their visuals up-to-date.
You can see the full conversation on the DevEdBookClub Twitter account.
DevEdBookClub@devedbookclubWelcome to our 6th #DevEdBookClub!
Tonight, we’ll be discussing Chapter 6 of @DocsForDevs. This chapter is all about adding visual content.02:00 AM - 31 Dec 2021
Add a comment on the Twitter thread or share your thoughts here to continue the conversation.
What did you think about Chapter 6 of Docs for Developers?