Feature Page Package Contents Best practices: 

  • (Re-Write this one) Include Josie in kickoff meetings for visuals if the feature will include unusual assets (e.g., Jerry’s music and memory story, which had an embedded Spotify list and audio files). 
  • Submit a design request once you have all of these assets assembled. Written information (such as the IRI tags) should be compiled in a single Word doc Include the final story draft in a separate document. You can use the file upload area for these. As noted below, visual assets should be linked from Chris’s files or uploaded to the cloud and then linked. 
  • Rename all images with descriptive information tied to the individuals, labs, article name etc. (DO NOT leave it as DSJ_3928374.JPEG - Use Hyphens or Underscore NO spaces, Thanks)
  • All questions/discussion about a feature story should take place in its Monday.com project, to streamline and consolidate communications. 
  • Try to avoid rush jobs: Allow at least 3-4 days for the design and review process. 

Checklist:

  1. A final copy of the story. If it is necessary to send a document that is not finalized, please enable track changes to show all subsequent modifications. 
  2. Please show full links (not embedded URLs) in the Word doc. Note: This expedites the process of finding and building out the page. You can drop the links in as comments, instead of directly linking in the text. 
  3. Use the “Research People” URLs. When linking to research profiles, please use the research profile URL, NOT the individual’s home school/unit profile. 
  4. A paragraph summary of the feature that is 450 characters (including spaces) or fewer. Note: This can also serve as both the Mercury node and YouTube summaries. 
  5. A sentence summary of the feature’s main focus that is 160 characters (with spaces) or less. Note: This should be the story’s dek. 
  6. List of related IRIs where the feature should appear in newsfeeds. 
  7. List of credits for photos, videos, graphics, etc. (for the contributors’ list at the end of the feature). Note: This can include the writer/media contact, the videographer/animator/series designer, and the copyeditor (usually Stacy Braukman). If the media contact is separate from the writer, list that as well. 
    If the photos require individual attributions, please indicate that and identify the photos/videos, etc. by their file name. 
  8. List of 2-3 selected pull quotes 
  9. List of selected photos with their file names and drafted captions If your photos require captions, please let the web team know in advance. Ideally, this is when you put in the design request ticket, even if final image selections have not been made. 
  10. List of YouTube links to embed — or if we need to upload videos to YouTube to embed, include a title and description of the videos. 
  11. Related content: This is a list of three stories related to the feature, whether by IRI, topic or researcher/SME. 
  12. Special items: Anything else out of the ordinary needed for the feature page design, e.g.: 
    * Spotify playlist 
    * Animation 
    * Is the feature part of a series? Which one? 
    * Any component that is not copy, a photo, or a video (ideally, us know about this in advance, with the understanding that projects evolve as they’re being developed)
  13. Upload visual assets to the cloud, rather than to the project in Monday (so: Sharepoint, OneDrive e.g.), and provide us with an accessible link and test that we can gain access.
Date
Note Type
Comms