Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data stewardship landscape analysis: Create a home #4830

Closed
4 of 6 tasks
kristinashu opened this issue Jun 30, 2020 · 6 comments
Closed
4 of 6 tasks

Data stewardship landscape analysis: Create a home #4830

kristinashu opened this issue Jun 30, 2020 · 6 comments
Assignees
Labels
Milestone

Comments

@kristinashu
Copy link

kristinashu commented Jun 30, 2020

We need a place to intro and link to all the PDFs and the AirTable created in #4829 as well as a newsletter signup.

Deliverables

  • Determine a URL.
  • Determine the template type (probably Bannered Campaign style)
  • Gather copy for the page
  • Create evergreen graphic style for the banner and possibly social media
  • Determine where on fo'mo we will link to this home
  • Add newsletter signup (can put IHR snippet for now but final signup is blocked by Insights (IHR): Email signup viability #4848)
@taisdesouzalessa
Copy link
Contributor

Taís to think about the URL - where does it fit considering the current information architecture (under initiatives? on its own?) - explore 3 options or so

@taisdesouzalessa
Copy link
Contributor

Determine a URL. Status: waiting on feedback
Here is a doc with 2 suggestions of URL. My current recommendation is the proposal #2 but I want to send this to design review before reaching the final decision. @kristinashu is there anybody else that should be involved in this decision besides the Design Team? Please let me know so I can loop them in.

@taisdesouzalessa
Copy link
Contributor

taisdesouzalessa commented Jul 9, 2020

chosen URL: /initiatives/data-stewardship/

Site potential entry points for this page: Blog (if we have a Blog post for this content) and if the content has any participatory element we can also add it as a card in the Participate page - this is a diagram with the current flow

Questions for Insights team:

  1. Will we have a blog post dedicated to this project? If so, the project will be displayed in our Blog Page.
  2. Will this project have any participatory element? If so, the project will be displayed in our Participate Page.

Mockups:
Proposal V1: recommended if 3 PDFs are a collection, meaning they all have to be read to get full understanding of the subject.
Proposal V2: recommended if the 3 PDFs are independent, meaning people can read 1 of them and get enough information.
NOTE: images are placeholders only! We will have proper images once we have defined content.

Next steps:
• Request Insights team to choose between V1 or V2, depending on the connection between PDF docs
• Get answers from questions 1 and 2 from Insights
• Once Insight team chooses the version, Taís will build it in prod and they can start populate the template with content. Currently, V1 is already built in the live site .

@kristinashu
Copy link
Author

Any update on this? I talked to Kasia this morning and it sounds like they feel a little blocked on the content because the PDFs aren't final yet. For this sprint I would recommend doing everything that we can do but then handing it off to them to populate when they feel ready.

@taisdesouzalessa
Copy link
Contributor

I think the only thing we can move forward on this task is doing the evergreen banner graphic during this sprint. That is what is in my queue.

@taisdesouzalessa
Copy link
Contributor

taisdesouzalessa commented Jul 16, 2020

Since the PDFs' content is blocked and the team can't make a decision on the version of the page until they decide on the PDFs' content I am closing this ticket and opened a new one to the following sprint - #4915

The 4 items achieved on this sprint are checked in the ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants