¶ 1 Leave a comment on paragraph 1 0 After organizing into teams and assigning roles and responsibilities to team members, we’ve certainly entered the “praxis” phase of this course. While the proposal process dealt mostly in generalities, the past week has forced us to transform some of our vague ideas into actionable tasks by cataloging data types, clarifying project resources, and wireframing important prototype components.

Data Types

¶ 2 Leave a comment on paragraph 2 0 We began last Wednesday’s class by itemizing all potential data types for end/line in a shared Google document. As Lisa suggested we moved from the front- to the back-end and then turned our attention to some of the supplemental material that will support the project.

¶ 3 Leave a comment on paragraph 3 0 Two forms will drive much of the user experience on end/line: one form to submit a poem, another form to encode it. The first form will need to record usernames, titles, authors, and the actual poems. It will also need to associate first and last names and email addresses with usernames and assign each entry a unique identifier and timestamp. While the second form will also need to record usernames (and associate and assign the same metadata), it will record and validate XML encodings of poems. We’ll manage both forms through a front-end framework—either Angular or Node. Meanwhile, we’ll then need to log all of this information in a back-end database—either Postgres or Mongo. This setup will obviate the need for a CMS to manage “About,” “FAQ,” “Terms of Service,” “Privacy Policy,” and other static pages. We’ve also planned to host our code, under an MIT license, in a public GitHub repository.

¶ 4 Leave a comment on paragraph 4 0 The community management team will oversee some of the supplemental data types, like our Commons blog and Twitter account. And the project manager will ensure the archival of our collaborative Trello and Google Drive work.

Project Resources

¶ 5 Leave a comment on paragraph 5 0 Because we all expect to learn new, necessary skills during this project, we’ve made sure to clarify either from whom or where to find help. For example, our “Project Roles and Agreements” document clarifies that Brian may consult on front-end development, Greg on project management, and Tom on community management, while Iuri explains the intricacies of TEI and Michael leads some of the course-specific deliverables. Furthermore, we’ve agreed to post all general questions, tips, and suggestions in Slack, and Tom has shared the credentials for Safari Books Online—a subscription library for developers, project managers, and other technology professionals—with the team. We’ll also avail ourselves of Graduate Center and other workshops as needed.

Wireframing

¶ 6 Leave a comment on paragraph 6 0 By the end of Wednesday’s class, we began wireframing some key pages and forms—including the homepage, search flow, submission and encoding forms, and comparison views—on pen and paper. Greg transferred these sketches onto Adobe XD later in the week, and they will help guide much of the front-end development work and help the community management team explain the project’s potential to early users and the wider public.