As a content editor, I want to be able to create, edit and manage my blog posts. As an admin editor, I want to be able to create, edit and manage all blog posts.

As an admin user, I want to be able to create and manage content pages that will use templates for landing page and content page styles so that I can arrange and publish content.

• add page setup functionality to Mezzanine
• create templates for landing pages w/ full-bleed image
• customize template for generic content pages

Notes for testing

Blog post archive is listed under "updates" in the new site. Archive links are provisional and not yet styled, we can test that separately.

Notes for testing

Updates 9/22:

• now displaying tagline/subtitle on project detail page
• confirmed drag and drop order works the way I think, updated import script to flip order
• tweaked styles for profile education section
  Updates 9/21 for second round of testing.
• Ran a complete import on fresh data from production this morning 9/21, so content should match what is there today.
• See comment for notes on changes made in response to first round testing feedback: #2 (comment)
• Be aware of manual cleanup that needs to be done after import (including updating the menus) #41 I have left things largely as is after the import so you can test the clean up as well, with the following exception: I associated images for one event and two projects and marked those projects as highlighted to test image and homepage display.

import content:

• people
• events
• projects
• blog posts
• content pages
• display tagline on project detail page
• check drag & drop sort order
• check formatting on profile page education

dev notes

• create separate branch to track #359 and remove/reset code related to it from this branch
• add tests for SiteSearchView
• implement search result styles from #364
• implement search bar styles from #367
• add new snapshots/states to percy for visual testing of search

d

Notes for testing

• very much related to #9, but go ahead and test and sign off independently

Notes for testing

• for this story, test adding main project information: title, images, tagline, text content
• test grant type and associating grants with projects via #33
• test editing project roles and associating contributors with projects via #34
• test editing resources via #35

As an admin user, I want to be able to create and edit project information, so that I can inform the Princeton community and public about contributions to DH projects. These include:

• Setting a large image
• Thumbnail image
• tagline
• Project contributors (linked to people in the site's database)
• Project contributor roles
• Paragraph text

Notes for testing

Navigate to blog posts and pull up any individual post. At the bottom, you should see links for the next and previous blog post. Check that they display ok, that the link works. Check that the first post doesn't error (only has a previous and no next), check at least one middle post with both next and previous links, and check the last post (no error, only has next and no previous).

Notes for testing

iCal download link is accessible on the event detail page.

Testing Updates 9/5:

• Fixed timezone logic. Please double check time display on project card, since I had to update that as well. (You may have to update existing test events since the timezone configuration has changed).
• Test with and without location set.

If people log in with CAS or we use a script to create their account, here is the information that should be populated:

• basic user information: username, email, first and last name
• people section, people list: more information under the 'profile' section. Title set from the person's display name; a slug based on the display name is autogenerated for use in the url; it also pulls in phone number and office location if available (currently has a small bug where it's pulling in "[]" for people without that).
• If you go to the people / title list, job titles are created based on the imported person's job title in the directory, although they will have to be manually associated with people so you can add dates.

Provide MVP functionality that duplicates the current site functionality in the new database model and page framework

Determine the levels of access we want for now and create a migration to define groups with the appropriate permissions. Customize admin user display to add more detail to the display, including group memberships.

admins, content editors, blog contributors?

Maybe one group for each app (mix and match as needed): event editor/admin, project editor/admin, etc.

As an administrative user, I want to be able to login to my account using Princeton's CAS Login system. (Included in PUCAS, added for legacy)

Notes for testing:

• a few resource types will be pre-populated
• sort order displayed and editable on the list view (eventually this will be used to determine sort order in public display site; later we plan to make sort order drag & drop here and elsewhere in the admin site)

Notes for testing

• should be visible on content pages, blog posts, projects, events, profiles

Notes for testing

To be included in the list, people must be marked as is_staff and profile must be published.

Notes for testing

Update 9/21: I think the image display issue was a media/deploy problem that's been resolved, please retest.

light grey is used on pages with cards, such as home, projects, people... blog and individual project page, staff page, has white background.

Notes for testing

• Blog post fields currently include a "featured image" but it isn't in the design we have, so that might change.
• We'll probably want to refine the styles and options in the wysiwyg editor but I don't know how much customization we'll have time for now. Feel free to make notes/suggestions about how it works so we can prioritize.

• banner image goes all the way to he top (there are area of overlap) so there won't be space between image and the navigation bar
• banner image aligns center when resizing the window (might be a away to borrow the code from Derrida? same behavior)

Notes for testing

Updated 9/21. Menu is dynamic but styles are keyed to the content we currently expect (so it could be possible to break things if we're not careful).

• Contact & Directions is no longer hard-coded in the footer and can be set via menu controls in admin; I think the Subscribe page is going away or just becoming a link, but either way should be handled in admin.
• Social links in the footer have been added.

Notes for testing

• Updated 9/19/2017 with revised styles. Both desktop and mobile footer styes working; layout is based on expected content and presence of submenus.

Notes for testing

• Project list page should be accessible from the top-level navigation (I added a placeholder link to the test site), or by clicking the projects heading on the home page.
• I just noticed the user story says "current projects", but it's not actually filtered right now (except based on published/unpublished). I think we should revise the user story to say all projects since that matches the current site functionality, and add a feature later to revise project display (filters, project archives, or something).
• Note that a logged admin can see unpublished content. We plan to add a visual indicator for draft content, but that won't be included in this release.
• Projects are currently sorted by title.

As an admin user, I want to be able to control the organization of links on the header so that I can direct users of the site to content efficiently.

• create migration to autoload place-holder content pages for dynamic content (events, projects, staff) so the links can be managed by admins

notes for testing

Project membership can be edited either on the project edit page or under projects -> memberships.

Notes for testing

Styles for generic content pages have been improved. Should be easier to test this with content imported from production site.

Notes for testing

• Attachments should now be included in the top level content menu in the admin.
• Attachments can be edited there or on each of the other individual items (rich text page, landing page, project, event, profile, blog post). Please test both ways.
• A single attachment can be associated with multiple different pages or kinds of content.

Notes for testing

I have it configured so the author defaults to the current user, since I figured that was the most likely scenario.

Initial event types will be preloaded.

Notes for testing

• currently only website url is displayed on project detail page (other items have not been incorporated into the design yet)

• e.g., project website url, twitter, etc

See #36 for editing resource types.

Notes for testing

Admin editor preview doesn't match the styles of published version (will have to be a later enhancement). There are not yet styles for all variants of formatting, but Xinyi and I will work out the specifics on that. (Feel free to note any important styles or issues we need to address in the short term.)

Tested in both Chrome and Safari, brown and lyon are not loading.

Notes for testing

• Provides both RSS and Atom feeds. Should be linked at the bottom of blog index and blog detail pages and also included in the header for autodiscovery.
• Easiest way to test is probably to install a browser RSS tool like chrome rss extension which will show the auto-discover url and also give you a nice preview of the content.

Notes for testing

• CDH should be automatically preloaded

Notes for testing

Edit the location in your browser to access a non-existent url. You should see a 404 page with a picture of Claus.

Notes for testing

• test event types management separately - #37
• test event locations management separately - #38

These events need to capture:

• title
• location
• schedule / time
• description of event
• large image
• thumbnail photo

Notes for testing

• links to archive are not styled yet, but logic should be working

In small view port, the it will only display one column of cards.

https://test-web.cdh.princeton.edu/projects/

Notes for testing

• edit under profiles -> people
• the profile section defaults to collapsed but I haven't been able to figure out an easy way to change that, so we'll just have to live with that for now
• update 9/20 added username to edit form, should fix the problem encountered before

Detailed items that this should include are:

• large photo for detail page
• thumbnail photo for listing
• job title
• education section
• contact info
• paragraph text

Notes for testing

Updated 9/21 to improve project member handling. Now displays project members associated with the most recent grant, even if the grant period has ended. Now also displays project alumni (project members not associated with the most recent grant.) Also better handling for person name display.

• display current members or members of last active grant if no current grant
• automatically display project alumni? (if easy)

Notes for testing

• update 9/21: I think the image display issue was a media/deploy problem that's been resolved, please retest
• displays next three upcoming events.
• displays 4 random projects that are current (i.e. has a grant that is active now based on the dates) and active marked as highlighted
• only displays events and projects that are published (but logged in admins will see draft content even though we don't yet have a marker for draft content)

updates for re-testing 9/5

• "upcoming" events now includes events starting any time on the current day, even if it is already started. Please test with events before today, current day, and future.
• Discussed project logic with Jean and renamed is_active to highlight and added help text. This is now the only qualifier for inclusion in home page rotation (although project must still be published).
• Admins no longer see draft content anywhere on the site (disabled until/if we add a visual indicator for draft content so it can be distinguished from published content)

Notes for testing

• Event list list page should be accessible from the top-level navigation (I added a placeholder link to the test site), or by clicking the events heading on the home page.
• Currently displays upcoming events only; event archive functionality still needs to be done and will be tested separately.

• clean up pages in top and footer menus (remove coming soon, make contact footer only)
• landing page images
• tag lines for landing pages
• images and file attachments are not included in the import and will be handled manually
  • profile thumbnails [partially complete]
  • profile images
  • event thumbnails
  • event images
  • project thumbnails
  • project images
  • blog post images
  • file attachments uploaded & associated with pages & events
• blogpost
  • associate actual authors with posts
  • clean up formatting, remove extra underlining on urls
  • fix any broken embedded images
    • images missing in congrats to valedictorian
    • images missing in grassroots minstrelsy
    • images missing in materials across empire
    • images missing in challenges to neutral data
• sort order for staff roles for staff will need to be manually assigned.
  • review sort order (Jean?)
• duplicate roles will need to be standardized.
• review project slugs and clean up / add redirects where needed
• associate speakers with events
• designate highlighted projects
• manually assign values to project roles for proper sort order
• credits page