Based on previous iterations and with the tremendous graphic design help from Erik Resly, Brown University, I have stitched together the
, which we will use as the basis moving forward.
and tell me what you think.
Issues that arose as a result of the new mock-ups are addressed in the "notes" field of the DHQ Web Site Requirements. The mockups are by no means polished; they should not be considered final versions, especially in terms of look and feel.
These requirements have been compiled based on DHQ-Production email exchanges in response to the
. Please review notes below as there are pending issues. Patrick will maintain more technical requirements separately that he will later post to the wiki. These requirements function more as guidelines for proceeding.
| Area | Requirements/Interface Description | Notes |
| Global | Design for 1024 x 768 resolution with font increase +1/+2. | Need to fix the navigation links from wrapping as they do. |
| Global | Persistent link/directory structure throughout the website | index.html needs to be redirected to /winter2007/index.html for the duration of the issue feature |
| Global | Keep Quarterly model; add "Preview" area/link for upcoming issue | The next issue will be available in "preview" mode until "official" quarter launch |
| Global | New Banner Image per Issue | Current mockup is randomly cycling through a set of banner images; need to change this to be one banner image per issue |
| Global | Use include files to better manage consistent content areas like banner, top navigation, side navigation, blog features, announcements, and footer | We will need to implement this as JSP includes in OpenCMS? . Currently this is hardcoded in the mockups. |
| Global | Announcements section | Need interface in OpenCMS? for News Editor to easily update/add news? Or TEI template for news editor? |
| Global | Blog section | The DHQ blog is down so I didn't have a DHQ-minded point of reference, but I imagine we'll be randomly featuring posts from the blog on the website with a link to the entire blog itself. We need to determine how we will handle this (through RSS?). |
| Global | ISSN/DOI | There's a space on the website for this information. We won't be able to apply for an ISSN until after sometime live (right?). I am not sure what's involved in registering for DOI and how that will impact our infrastructure. |
| Global | Side Navigation for issue-specific navigation | Winter launch will only contain Current Issue and Preview Next Issue |
| Global | Keyword Search | Index full text and article metadata; Need to mock up results page. Need to distinguish between article results and website. Or do we want to only search articles for initial launch? Do we launch without search for winter? |
| Global | Automatically populate keywords and description in the META HTML tags for each page | Some search engines rely on these for retrieval. Can they be customized for the articles? |
| Globa | Privacy policy | Need statement from editors. Any additional policies? |
| Home | Need to support abstracts in multiple languages; Need to be able to Hide/Show abstracts | How many languages? Mockup shows English and French |
| Home | ToC? Headers: Article, Interactive Media, Issues in Digital Humanities and Reviews | Is this correct? |
| Home, IM page | IM will launch a new window | |
| Article | Include Article metadata | |
| Article | Number paragraphs | |
| Article | Display article in one page | We can explore chunking later. |
| Article, IM | Link out to bios | Display bios on a per issue basis. Bios currently not mocked up. |
| Article | Include Toolbar with the following features: Print, Download (XML? PDF?), Add Comment, TAPoR Tools | Do we want to provide an XML version of the article for download? Do we have a mechanism in place for generating PDFs? Can we call TAPoR? Tools something more meaningful like Text Analysis Tools? |
| Article, IM | Comments to appear beneath each article | |
| IM | Include toolbar with the following features: Download Plugin, Add Comment (Is this info captured in the TEI? If so, we can dynamically generate link to appropriate plugin | What else? |
| Registration | Collect name, email, password. Send email verification. | Also collect affiliation, website and research interests as optional. Need intro text from editors. |
| Registration | Database should contain a mechanism for suppressing a registrant with mal-intent |
| Login | Send username and forgotten password over email | Is this ok? |
| Comments | Registration process | Must be registered before adding comments. If commenting and not registered, redirect to registration page. Verification link should keep session information and return reader to the 'Add Comment' section of the article upon verification. |
| Comments | Comments will be posted immediately. Send Comments Editor an email. | Database should contain a flag for showing/hiding comments. Interface for comments editor? |
| Comments | Can be posted anytime | |
| Comments | Tied to article-level | Later, experiment with paragraph-level granularity |
| Comments | Will display the person's name linked to email address |
| About DHQ | Overview, DHQ on Digital Humanities, Technical Overview, What Else? | Need editors to define additional content areas. Need content from editors. |
| DHQ People | Lists all DHQ contributors, staff, etc.: Editors, Staff, Steering Committee | Need missing bios. Need editors to make sure content is still accurate. |
| Submissions | Submission Guidelines, Text Guidelines and IM Guidelines | Static HTML for now. |
| Contact | Email and Post contact info |