Week 11 – StoryMaps

I think I would feel pretty confident with helping someone use StoryMaps. I had used it prior for one of my classes, and I felt pretty confident with using it this week. That being said, I do think that there is more for me to explore, and I will most likely try some of StoryMaps’s other features when I have the time. I feel like StoryMaps is one of the more intuitive tools that I have learned how to use so far, not only because I had some prior experience with it, but also because it is very user friendly in how different elements are located. I especially like how you are able to integrate different widgets, such as videos, images, and maps, within your text blurbs. As far as the limitations of StoryMaps goes, it felt as if there were a limited amount of customization options, when it came to changing how the layout looked, and it felt like cropping the images was kind of inconvenient.

I think that what makes a good StoryMap is intentional design, where all the elements work together to help support the StoryMap’s narrative. Something to avoid would be the temptation to use all the features available, which can create a cluttered and confusing experience for a viewer. Instead, sometimes less can be more, and it’s better sometimes to focus more on what you’re trying to tell rather than what the software can do.

Week 10 – Audacity

Learning how to use Audacity seemed fairly straightforward, although I am pretty sure that I do not know all of what the software is capable of. I was able to record myself and overlay sound effects on my recording, and I was also able to manipulate the volume of each track. In the future if I have time to revisit this tool, I would like to try to learn more about “blending” the audio, and having audio clips fade in and out rather than just overlaying them on top of one another.

I think I would feel pretty confident helping someone learn and set up Audacity, however I would like to explore more of what Audacity can do.

Week 9 – Documentation

In order to create good documentation, the writer will need to describe each step that they took with a pretty notable amount of detail. It may also be necessary to add a visual aid, such as a video or images to the documentation in order to show certain steps that need to be done. For my own Vivero project, my project lead and I will need to create documentation on how to upload articles to our database, and how to extract metadata from these articles. However, I also would not be surprised if eventually we will have to provide more documentation in order to effectively communicate how to navigate our digital project. In order to make this happen, I will make sure to communicate often with my project lead when technical steps are implemented, and I will also keep a document that lists the steps taken for what is necessary.