For the site’s actual content, I reasoned that since I was working as a transcript data entry specialist for the Office of the Registrar at a private arts university in the Bay Area at the time of taking the course, I would generate my own functional proof-of-concept website that had more relevant features than what is currently on the school’s webpage for the registrar’s office. [See Competency G for more about this work experience.] I created the site with the purpose of making the content of my workflows more transparent and applicable based on all of the frequently asked general questions that I received from various parties while in my position (students, parents, admissions representatives, co-workers). I used real content, such as publicly available office phone numbers and relevant transcript and registration information that is available on the actual registrar’s webpage within the main university website. I structured it in a way that provided easy, sensible access to relevant information for students and university employees.
On the site itself, there are various tabs for information regarding registrar services, transcript requirements, registrar-related news items, and a contact form for questions. The home page has a summary of services offered by the registrar office, ranging from transcript ordering to enrollment verifications, as well as information for prospective students to the university about how to submit transcripts for registration and for current students and alumni about how to order transcripts. Additionally, as stated on the “About” page of the website, I created this "functionally updated, proof of concept" registrar site to host online versions of the paper forms used to request registrar services (something that had not been implemented during the time that I was working there), as well as present a published knowledge database of various transcript policies for undergraduate and graduate admission into the university’s various programs. The online forms would facilitate filling out, signing, and submitting such commonly requested registrar services. The working database would be an initial effort towards transparency regarding existing review workflows, so Admissions department representatives and Student Services know what the registrar’s office is looking for regarding specific transcript requirements at the undergraduate and graduate levels. In summary, the goal of creating such as site, even for mock purposes, was to facilitate a greater and wider degree of communication between the registrar and the university’s students, as well as generate transparency towards collaboration between the registrar and other departments such as Student Services and Admissions, all in demonstration of my developing coding ability.
In the process of building this site, I learned important lessons in beta testing and troubleshooting my own work. Early on in INFO 240, I was introduced to the freely available local server program XAMPP. This program creates a local server host environment that allows users to test their web content, to try out new bits of code and troubleshoot issues before making the pages live on a web server. I used XAMPP to test all of my .html and .php files locally to ensure that they would function well. Though the setup of the program itself was relatively tricky at first, I was able to overcome this setup hurdle in order to make my webpage development processes more streamlined. Additionally, I use the browser extension Web Developer, first introduced to me in INFO 240, to help troubleshoot my HTML and CSS pages. Web design and development has standards which are established and updated by the World Wide Web Consortium (W3C). This extension allows me to test my code against the W3C standards, to ensure that my HTML content and CSS styling aligns with those rules to ensure that the content as I created it shows up properly across all web browsers.