Other than minor additions to the documentation infrastructure Regann initially laid out last semester, most of my documentation has been more process-oriented, rather than technical. This is because my work this semester focused on researching content and then adding it to pages in the formatting Regann specified in their original documentation. That said, I did add a section on how to edit the header, though it was rather small. This bit was dry and technical, but based on “How-to” for minor tasks in programs that I’ve used before.
More importantly though, Dr. Shook asked me to document some of the conversations we had around how to design the website, so that future Vivellos could understand our approach and hopes for the project. I found it rather nice to have a written record of our ideas to look back upon myself. I’ve attached two sections, one on our overall philosophy of design and another on why we chose to continue with WordPress rather than Mukurtu. For the former, I tried to capture considerations we had talked about throughout the semester, such as audience and accessibility. Inevitably, this got into ideas of what we want the IoRF project to do, and what long term plans might look like. As for Mukurtu, I mostly tried to explain why, after exploring the program’s features, I recommended that WordPress could accomplish IoRF’s goals better than Mukurtu. I think these blurbs captured our discussions well, and I hope that the Philosophy of Design section can provide future Vivellos who take up the project inspiration so that they are not starting from ground zero.