![\"\"](\"https:\/\/onlineacademiccommunity.uvic.ca\/dsc\/wp-content\/uploads\/sites\/2373\/2018\/06\/zotero-logo.1519312231.jpg\"){kind=logo}
<\/a><\/div>\nZotero<\/a> (zoh-tare-roh) is a free, open-source, well-supported tool that is meant to be “your personal research assistant.” Originally, it was created as a bibliographic manager, but it has become much more powerful over the years and allows you to “collect, organize, cite, and share your research” in useful ways. Moreover, Zotero “is developed by an independent, nonprofit organization …. With Zotero, you always stay in control of your own data.”<\/p>\n If you’re looking to streamline your scholarly research workflow; collect sources directly from the web; organize your annotations, PDFs, and notes in one place; create and manage citation styles and bibliographies with one click; and be assured that your data will be exportable; then Zotero is the tool for you.<\/p>\n This tutorial will walk you through the process of installing Zotero, its browser connectors, and its most useful plugin for research management, “zotfile.” The combination of these three tools will give you the ability to easily collect, organize, cite, and share your research.<\/p>\n [\/et_pb_tab][et_pb_tab title=”Textual Analysis” _builder_version=”3.17.3″ use_background_color_gradient=”off” background_color_gradient_start=”#2b87da” background_color_gradient_end=”#29c4a9″ background_color_gradient_type=”linear” background_color_gradient_direction=”180deg” background_color_gradient_direction_radial=”center” background_color_gradient_start_position=”0%” background_color_gradient_end_position=”100%” background_color_gradient_overlays_image=”off” parallax=”off” parallax_method=”on” background_size=”cover” background_position=”center” background_repeat=”no-repeat” background_blend=”normal” allow_player_pause=”off” background_video_pause_outside_viewport=”on” tab_text_shadow_style=”none” body_text_shadow_style=”none”]<\/p>\n Under construction. Check back soon!<\/p>\n [\/et_pb_tab][et_pb_tab title=”Geospatial & GIS” _builder_version=”3.17.3″ use_background_color_gradient=”off” background_color_gradient_start=”#2b87da” background_color_gradient_end=”#29c4a9″ background_color_gradient_type=”linear” background_color_gradient_direction=”180deg” background_color_gradient_direction_radial=”center” background_color_gradient_start_position=”0%” background_color_gradient_end_position=”100%” background_color_gradient_overlays_image=”off” parallax=”off” parallax_method=”on” background_size=”cover” background_position=”center” background_repeat=”no-repeat” background_blend=”normal” allow_player_pause=”off” background_video_pause_outside_viewport=”on” tab_text_shadow_style=”none” body_text_shadow_style=”none”]<\/p>\n Under construction. Check back soon!<\/p>\n [\/et_pb_tab][et_pb_tab _builder_version=”3.17.3″ title=”Reading Technical Documentation” use_background_color_gradient=”off” background_color_gradient_start=”#2b87da” background_color_gradient_end=”#29c4a9″ background_color_gradient_type=”linear” background_color_gradient_direction=”180deg” background_color_gradient_direction_radial=”center” background_color_gradient_start_position=”0%” background_color_gradient_end_position=”100%” background_color_gradient_overlays_image=”off” parallax=”off” parallax_method=”on” background_size=”cover” background_position=”center” background_repeat=”no-repeat” background_blend=”normal” allow_player_pause=”off” background_video_pause_outside_viewport=”on” tab_text_shadow_style=”none” body_text_shadow_style=”none” tab_text_shadow_horizontal_length=”0em” tab_text_shadow_vertical_length=”0em” tab_text_shadow_blur_strength=”0em” body_text_shadow_horizontal_length=”0em” body_text_shadow_vertical_length=”0em” body_text_shadow_blur_strength=”0em”]<\/p>\n <\/a><\/p>\n Available as a PDF<\/a> | or <\/strong>on Github<\/strong><\/a><\/p>\n Technical documentation is any material meant to accompany a particular tool, software, or technology which can be descriptive (what problem does this solve?) or instructional (how-to). Although documentation (“docs”) comes in various formats, this guide focuses on software documentation in textual format published on the web.<\/p>\n Here’s the most common scenario in which I read documentation: I’m just starting a project and have a specific goal in mind, but I don’t how to go about doing it. I may not even know what programming language, device, etc. to use. Can I do this with something I already have or should I install a dedicated application for it? If I want to make a sound-reactive light display<\/a>, should I use Arduino<\/a> or Raspberry Pi<\/a>? What physical parts (LEDS, microphone, etc.) do I need? Which seems less complicated and time-consuming?<\/p>\n In short, I’m reading docs because I want to know what steps are involved and what the final product might look like\u2014without investing too much time and resources upfront or reinventing the wheel. However, reading documentation is like trying to find a word in a dictionary without knowing how to spell it: how do I find what I’m looking for when I don’t know what to look for?<\/p>\n This guide walks through types of documentation, how to parse them, and common conventions in web documentation (e.g. README files on Github). It provides advice and tips to help you navigate docs and sift the dizzying amount of information on the internet. Although much of this advice holds true for many types of software, I’ll be using examples from Python<\/a>, Machine Learning<\/a>, Command Line<\/a>, Arduino<\/a>, JavaScript<\/a>, and Twine<\/a>.<\/p>\n <\/p>\n