nlottig94
commented
8 years ago @laurenmcguigan @jlm323 @mjb232 @mmm202 Hey guys! Here was one of the first homepages for the Dickinson site: http://htmlpreview.github.io/?https://github.com/ebeshero/EmilyDickinson16/blob/master/Old%20Files/lawrence.dickinsonhomepage.xhtml
Just an example, and we didn't use it at all!
To start, as we discuss on Monday, you should try setting up an HTML splash page for the project (just a placeholder for now) in our new decameron project space on newtFire. Here's how to navigate there via SFTP.
You may wish to coordinate your web development here in GitHub: In your SFTP client, you can set up a session profile for Decameron so when you click on that option it opens to your decameron GitHub directory on your local computer on the left and the PSC decameron project directory on the right.
So, one question will be: how to coordinate this? Each of you might try making an html page with a CSS stylesheet to begin and then decide which style, colors, fonts, etc. that you like. To decide on a style, you may want to look around at other sites that present studies of medieval material, and look around for pictures, too! You could all help out in looking for image files you might want to put on the site.
How to decide on colors?
Here's a suggestion: When I started the website for the Amadis project, I asked for my team members to send me some illustrations from print editions of the book, and then I actually made my color palette based on the colors in the images! I was able to upload an image--actually not the one pictured on the site, but this one--into a color palette generator, which separated out the various colors for me, and then I could decide what colors I wanted to use in the background, for the font, on the menu bar, for active and already-visited links, etc. I didn't use every color on the palette, but it helped me to get started. For newtFire I did something completely different, which was to use the Paletton color generator: http://paletton.com/#uid=1000u0kllllaFw0g0qFqFg0w0aF and look for a trio of colors! I was surprised at the interesting balance of greens with reds, since I'd never tried to make a green website before!
How to coordinate with each other:
If each of you is experimenting with making an index.html page, and saving it to the same GitHub space, there are a couple of ways to proceed: 1) Everyone shares an html folder here, and posts files named index-userid.html, with userid.css to help prevent writing over each other's files (What's tricky here is that when you choose one, you'll need to have to change the file name before you send it to the website (so there it will just be index.html).
2) Each of you might make an experimental fork or branch on the repository in your OWN GitHub space. This is what we call a "get smart" task--you'll learn a lot about how GitHub works by doing this. The returning DH students have just been learning how this works, so we can all help you, and it's a good way to operate. If your work sits in your own fork, when you want the team to look at it, you issue a "pull request" to Jessica who looks after this main repository. Jessica can decide which ones to incorporate in her main repository here. Becca's GitHub tutorial will explain how this works. I'd still recommend saving your tester index files with your userid in the name to make it so you don't write over each other, and once you decide which one to use. You don't need to set up forks and branches just yet, but it's not a bad idea to try them early to get used to them...and we'd like you to get some experience with this since it's a great way to collaborate. I think we'll want a special project meeting to show you how to use these features of GitHub and how to work at command line--because you really want to work in command line when you fork and branch.
@jlm323 @mjb232 @mmm202 @laurenmcguigan @RJP43 @brookestewart @spadafour @nlottig94 @ghbondar @djbpitt