Project Checkpoint 3 due Mon Oct 29

[ghbondar]

Project Checkpoint 3 is coming-up on October 29th. In grading this checkpoint, we will be looking for the following:

• [ ] 1) Collection: A reasonably complete collection of the documents on which your project will be based. You can always add to these as you discover additional ones, but you should have a functional and representative collection of documents by this point.

• [ ] 2) XML Markup: Your XML markup of these documents should be well underway now, so by October 29, your collection should consist of well-formed XML documents with basic structural markup, at least down to the level of paragraphs, and other major parts. We would like to see content markup that you're applying to address your research questions as well, but we do not expect the mark-up of any of these documents to be complete, so plans for later additions are OK. Please document those plans (write up task lists for the team on the repo).

• [ ] 3) Schema: This mark-up should be controlled by one or more schema files linked to these documents. Again, we don't expect that the schemas will be complete and fixed-in-stone, but they should conform to the current state of the mark-up at that time.

• [ ] 4) Webpages: The development of the webpages should be progressing on-pace with the mark-up. A descriptive and attractive home page should lead to several logical and developing pages of content. Although we don't expect your XML documents to be in a web-ready state, there should be some indication of where they will be located. All of these pages should use CSS and SSI's (for your site menu). Also, because you should not be storing all of your files in the same (root) file-directory on your website, you should have a logical hierarchy of directory folders (which was supposed to be developed for Project Checkpoint 2).

• [ ] 5) GitHub Repo: GitHub should be at the core of your project development: Just as your webspace should have a logical structure of directory folders, so too should your project repo on GitHub. All of your project files (text, XML, schemas, webpages, CSS, etc.) should be on GitHub so that the entire project team, and you instructors, can access them.

We've designed this as a task list that you can mark off as you complete the tasks. (You can generate one for your team using markdown like we did here. Use the icon above with the checkmark to create a task list entry on a GitHub Issue)

@KSD32 @Julegirl @quantum-satire

[ebeshero]

@Julegirl @KSD32 Can you two check and see if Julegirl's a member of the repo? We can't tag Julie on assignments...something's up.

[KSD32]

I checked and it appears that Julegirl needs to accept the invite into the repo.

[ebeshero]

@KSD32 Aha! My guess is that you'll need to send a new invitation (you can do that from the settings on the repo.), since the original one might be lost by now...I think it's under Settings -> Collaborators (and you may be looking there already). @Julegirl can you find an invitation to join this repo?

[ghbondar]

@Julegirl Yay!

[ghbondar]

Please see CourseWeb for Feedback on this checkpoint.