{"action":"created","issue":{"url":"https://api.github.com/repos/ebeshero/Amadis-in-Translation/issues/27","labels_url":"https://api.github.com/repos/ebeshero/Amadis-in-Translation/issues/27/labels{/name}","comments_url":"https://api.github.com/repos/ebeshero/Amadis-in-Translation/issues/27/comments","events_url":"https://api.github.com/repos/ebeshero/Amadis-in-Translation/issues/27/events","html_url":"https://github.com/ebeshero/Amadis-in-Translation/issues/27","id":110795651,"number":27,"title":"Website for Amadis-in-Translation","user":{"login":"ebeshero","id":4014518,"avatar_url":"https://avatars.githubusercontent.com/u/4014518?v=3","gravatar_id":"","url":"https://api.github.com/users/ebeshero","html_url":"https://github.com/ebeshero","followers_url":"https://api.github.com/users/ebeshero/followers","following_url":"https://api.github.com/users/ebeshero/following{/other_user}","gists_url":"https://api.github.com/users/ebeshero/gists{/gist_id}","starred_url":"https://api.github.com/users/ebeshero/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ebeshero/subscriptions","organizations_url":"https://api.github.com/users/ebeshero/orgs","repos_url":"https://api.github.com/users/ebeshero/repos","events_url":"https://api.github.com/users/ebeshero/events{/privacy}","received_events_url":"https://api.github.com/users/ebeshero/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ebeshero/Amadis-in-Translation/labels/help%20wanted","name":"help wanted","color":"159818"}],"state":"open","locked":false,"assignee":{"login":"setriplette","id":13948197,"avatar_url":"https://avatars.githubusercontent.com/u/13948197?v=3","gravatar_id":"","url":"https://api.github.com/users/setriplette","html_url":"https://github.com/setriplette","followers_url":"https://api.github.com/users/setriplette/followers","following_url":"https://api.github.com/users/setriplette/following{/other_user}","gists_url":"https://api.github.com/users/setriplette/gists{/gist_id}","starred_url":"https://api.github.com/users/setriplette/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/setriplette/subscriptions","organizations_url":"https://api.github.com/users/setriplette/orgs","repos_url":"https://api.github.com/users/setriplette/repos","events_url":"https://api.github.com/users/setriplette/events{/privacy}","received_events_url":"https://api.github.com/users/setriplette/received_events","type":"User","site_admin":false},"milestone":{"url":"https://api.github.com/repos/ebeshero/Amadis-in-Translation/milestones/9","html_url":"https://github.com/ebeshero/Amadis-in-Translation/milestones/data%20visualization","labels_url":"https://api.github.com/repos/ebeshero/Amadis-in-Translation/milestones/9/labels","id":1333854,"number":9,"title":"data visualization","description":null,"creator":{"login":"HelenaSabel","id":8516387,"avatar_url":"https://avatars.githubusercontent.com/u/8516387?v=3","gravatar_id":"","url":"https://api.github.com/users/HelenaSabel","html_url":"https://github.com/HelenaSabel","followers_url":"https://api.github.com/users/HelenaSabel/followers","following_url":"https://api.github.com/users/HelenaSabel/following{/other_user}","gists_url":"https://api.github.com/users/HelenaSabel/gists{/gist_id}","starred_url":"https://api.github.com/users/HelenaSabel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/HelenaSabel/subscriptions","organizations_url":"https://api.github.com/users/HelenaSabel/orgs","repos_url":"https://api.github.com/users/HelenaSabel/repos","events_url":"https://api.github.com/users/HelenaSabel/events{/privacy}","received_events_url":"https://api.github.com/users/HelenaSabel/received_events","type":"User","site_admin":false},"open_issues":1,"closed_issues":3,"state":"open","created_at":"2015-10-01T20:22:37Z","updated_at":"2015-11-03T07:46:54Z","due_on":null,"closed_at":null},"comments":30,"created_at":"2015-10-10T13:50:56Z","updated_at":"2015-12-19T15:34:36Z","closed_at":null,"body":"@setriplette @HelenaSabel We need to do some large-scale thinking about the web presence of this project. Stacey, you and I have discussed this in very early stages, back when we were just pipe-dreaming this project, and I know that what we make on a public-facing website is something you want to complement your long-range work on Amadis and perhaps on translation studies more broadly. \r\n\r\nNow, Helena and I have started extracting data and transforming it for web view, almost without thinking about the bigger picture of what we are designing for the long term. Before we go any further, I want us to discuss what kind of web presence we want for this project, so we are all clear on our goals and so we can share the stylistic decisions. It's too easy for either Helena or me to dig material out of our other web projects and run with it, without discussing it first--and before long we commit ourselves without thinking to design decisions we should have made together. So, before we do any more web work, I need you both to help me with answering some fundamental questions. I'm going to give my own sense of the answers first, but I'd like you each to add your thoughts, perhaps just by editing this Issue page here on our GitHub site, and adding your initials as I'll do here:\r\n\r\n### What are the purposes of a Website for this project? ##\r\n\r\n(ebb): Short-term: We want a way to project and share information at the TEI Conference, and future conferences.\r\nLong-term: Web views should help us to see patterns and learn from our markup. We should be able to see:\r\n1) where Southey's translation aligns with, deviates from, or alters Montalvo.\r\n2) what kinds of changes are applied:\r\n* from chapter to chapter, and\r\n* across the whole of the two books (or at least the \"whole\" of what we've encoded so far.\r\n\r\nWe also want to provide a good digital edition and reading experience of each text, since this is especially difficult to find on the web. If I understand this correctly, we want to make the site a useful resource for students and first-time readers of Amadis--and thus our work with tracking and annotating proper names should help make it easy for readers to \"jump in\" at any point of interest and learn something of who the characters are and their backstory. \r\n\r\nWe might imagine people coming to read chapter by chapter, either Montalvo or Southey, or both. But those interested in our studies in translation (including our own selves, who may be the most frequent visitors of our own site) may want to jump quickly to the chapters that feature the most omissions or alterations by Southey. \r\n\r\n## How shall we design our website? ##\r\n\r\n(ebb) Let's think about the hierarchy of the site. Please modify as you have ideas!\r\n* **Main index page**: describes project as a whole and surveys site content. \r\n\r\n* **\"Global\" Table of Contents (TOC) page**: to show the intro and chapter contents of Montalvo and those of Southey side by side, and how they align with each other (See Helena's book skeleton post). Montalvo sits on the left and Southey on the right. This page links to the chapter views. Perhaps it also contains small \"summary\" visualizations to help highlight which chapters feature the most extreme alterations of Southey(?) I imagine these could be perhaps plotted as narrow horizontal bars, color coded (with a legend) according to our color scheme for omissions, additions, (other things?).  Perhaps we could position 1 to 3 small horizontal color-coded bars to sit directly beneath each chapter title of Southey? Here's [a not-so-great example of small horizontal bar plots](http://stackoverflow.com/questions/26976161/flot-data-labels-on-horizontal-bar-chart), perhaps enough for an idea. Basically, my idea is to put a clear signal on the TOC page of which chapters feature the biggest alterations or the Most Interesting Stuff we want to be studying. \r\n\r\n*  Consistent and unobtrusive **navigation menu bar** across all pages. Horizontal, because we do a lot of side-to-side work on internal pages? What goes on the menu bar? Note: We can make this in its own separate file to call (as a \"server-side include\") across our pages, so we can keep modifying it easily just in one place as we develop our site.\r\n\r\n* Detailed page(s) on **Editorial Methods**. With this, our **Punctuation list with images**.\r\n\r\n* **Site Index** --pull info from this as needed, as referenced in mouse-over pop-up boxes throughout site, but also feature and present as its own page? Note: we may (eventually?) want to look for small image files to complement site index entries...\r\n\r\n* **Montalvo-Southey side-by-side reading views**. Anchor start points in Southey to be illuminated with small (unobtrusive) ornament marks. \r\n  On click of an anchor ornament, the corresponding Montalvo passage aligns on the left. \r\n  On scroll of Montalvo, or similar on click of ornaments, corresponding alignment point in Southey on right?\r\n\r\n* **Table pages** to analyze translation changes: sortable based on ______? (discuss...) Where do these sit in relation to the reading views and the main project site? Should we be able to enter a table page for a particular chapter from the side-by-side reading view of that chapter, and vice versa? \r\n\r\n--We may want chapter by chapter table pages, as well as a \"global\" table--a table or chart that lets us see at a glance a chapter-by-chapter summary of our major findings. And we may not be ready to make that yet. \r\n\r\n\r\n## Color Scheme and Fonts! ##\r\nGive me some leads here: background colors, font color, font type. Colors for dividers and such. What colors and font are appropriate to Amadis?\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/ebeshero/Amadis-in-Translation/issues/comments/165997134","html_url":"https://github.com/ebeshero/Amadis-in-Translation/issues/27#issuecomment-165997134","issue_url":"https://api.github.com/repos/ebeshero/Amadis-in-Translation/issues/27","id":165997134,"user":{"login":"HelenaSabel","id":8516387,"avatar_url":"https://avatars.githubusercontent.com/u/8516387?v=3","gravatar_id":"","url":"https://api.github.com/users/HelenaSabel","html_url":"https://github.com/HelenaSabel","followers_url":"https://api.github.com/users/HelenaSabel/followers","following_url":"https://api.github.com/users/HelenaSabel/following{/other_user}","gists_url":"https://api.github.com/users/HelenaSabel/gists{/gist_id}","starred_url":"https://api.github.com/users/HelenaSabel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/HelenaSabel/subscriptions","organizations_url":"https://api.github.com/users/HelenaSabel/orgs","repos_url":"https://api.github.com/users/HelenaSabel/repos","events_url":"https://api.github.com/users/HelenaSabel/events{/privacy}","received_events_url":"https://api.github.com/users/HelenaSabel/received_events","type":"User","site_admin":false},"created_at":"2015-12-19T15:34:36Z","updated_at":"2015-12-19T15:34:36Z","body":"Yes, I think we made some decisions in a different issue, and when I sorted out a little bit the repository, I changed some file names.\r\nI guess one of the following steps to take is the implementation of the reading views, so we'll need to change the table of contents to include the new information once is ready. "}}