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.

Sign up for GitHub

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

Jump to bottom

Women & Web Literacy - Create a Web Presence #826

Closed
5 tasks done
gideonthomas opened this issue Jul 27, 2016 · 10 comments
Closed
5 tasks done

Women & Web Literacy - Create a Web Presence #826

gideonthomas opened this issue Jul 27, 2016 · 10 comments
Assignees
@gideonthomas @hannahkane
Labels
Local Impact
Milestone
September 2, 2016

Comments

@gideonthomas
Copy link

gideonthomas commented Jul 27, 2016 •
edited

DARCI

Driver: @gideonthomas
A: @hannahkane
R: @amirad, Local Impact team
C: @kaythaney
I: @chrislarry33, @simonwex

Overview

The Women and Web Literacy(WWL) hub is taking the next step in solidifying their presence in communities and in MLN. Now, they need a web presence to showcase the amazing work done by @amirad and the communities. What is envisioned here currently is a website exclusively for this hub that will serve as the home for this content.

Outcome(s)

  • Design and develop a web interface (effectively a website) that will host content for WWL and signify its status as a new and growing hub.

Links

Key Deadlines

  • August 5, 2016 - Acquire content that is ready-to-use for the website (@amirad)
  • August 19, 2016 - Finalize content(after edits) for the website (@amirad)
  • August 26, 2016 - Website is ready for user testing (Local Impact team)
  • September 2, 2016 - Website is production ready based on the go-live checklist (Services team)
  • September 6, 2016 - Website is on production (Local Impact team)
@gideonthomas
Copy link
Author

gideonthomas commented Jul 27, 2016 •
edited

Clarifications (@amirad)

Project (Done in the doc linked above)

  1. Who is the target audience for this website?
  2. The primary purpose of this website is to broadcast information, stories and experiences related to WWL while CTAs and community engagement incorporation is something we want to approach iteratively in the next phase. Is this a correct assertion?

Content (Done in the doc linked above)

  1. What "static text" will be needed to convey the purpose of this hub (expected length, content type, etc.)?
  2. The following questions about resources (reports, teaching kits, images, etc.)
    1. Do they already exist? If so, in what format and does the format need to be changed (for e.g. into html)?
    2. How many of each will be on the website?

Design Considerations (Done)

  1. Is completion within the timeline do-able? Any time estimate on the design work?
  2. Does it make sense to make this a "single-page" project based on @amirad's content clarifications (especially from a deadline perspective)?
  3. It is important that the design (including copy) conveys the idea of WWL being a new and emerging program
    • Determine the use of logos/branding
  4. Determine the subdomain to access the website (tracked here: URL for Women & Web Literacy hub Design#194)

@hannahkane hannahkane added this to the August 19, 2016 milestone Jul 27, 2016
@hannahkane
Copy link
Collaborator

Since this project will include a launch of a new product, it might be good to grab the pre-flight checklist that exists somewhere. @gideonthomas - do you have that? or @cadecairos?

@gideonthomas
Copy link
Author

gideonthomas commented Jul 27, 2016 •
edited

Ah nice reminder, thanks!
I will update the links above.
The checklist will be used once a devops ticket is filed to get the subdomain and release the product and will be completed by someone on the Services team. However, we should definitely consider this in our timeline - I will add it to the "Key Deadlines".

@amirad
Copy link

amirad commented Jul 28, 2016

Thanks all!

@gideonthomas I tried answering all the questions you had in the google doc. Let me know if I missed something.

I also started organizing resources here: https://docs.google.com/spreadsheets/d/1dDkmnkT7aKA1yga-oNappC-87JpXJXf6GbO5vPmYK3w/edit#gid=0

@gideonthomas
Copy link
Author

gideonthomas commented Jul 28, 2016 •
edited

Woo thanks for the responses @amirad, that clarifies a lot.

Production Planning Meeting Goals

We have an engineering/design planning meeting scheduled for this week to come up with a strategy for approaching this project. The outcomes of that meeting are:

  • Introduce the project to the production team
  • To have a broad plan about what needs to be done
  • Determine the order of things to be done
  • Be aware of the key deadlines for the deliverables

Questions answered

  • Anticipated design time - 1 week to 1 heartbeat
  • Anticipated engineering time - 1 heartbeat
  • Time left for QA - 2-3 days

Next Up

  • Determine how we plan to disperse the work in the next two heartbeats
    • What will the anticipated development "end-date" be?
  • How we're going to resource the project based on the Local impact team's current roadmap
    • When will development on the project commence?
  • File website design ticket

@amirad there are a few more questions in the Google Doc on the first page. Would you be able to answer them?

@hannahkane
Copy link
Collaborator

This project will begin as soon as we land the two Clubs related tasks from the current heartbeat. As discussed in stand, there's an 80% chance the Club Captain application form will land this heartbeat, and a...uh...12-96% chance the Clubs page changes will land (IIRC, the discrepancy is based on unknowns about localization).

This project will bump the previously scheduled next project which was to be merging Gigabit and Hive content from their respective websites into the Learning site. (I will let those stakeholders know about this change.) The WWL project has been deemed more urgent.

Assuming the Clubs work finishes as planned, the Design ticket for WWL will go into the August 22nd heartbeat, potentially finishing a week in. The dev work will immediately follow. Based on the estimates above, it seems we're looking at a September 5 or September 12 launch date.

@amirad
Copy link

amirad commented Aug 3, 2016

Thanks for all the questions in the initial design document @hannahkane and @gideonthomas

I wrote out site text and info which I think answers a bunch of the questions and can be the next place for your feedback. https://docs.google.com/document/d/1ehB2zgBH6XIAif6rUyLyHmGWQQSdQrxQpounPk9bPI8/edit#

@gideonthomas
Copy link
Author

gideonthomas commented Aug 12, 2016 •
edited

Progress Tracker

  • Repository has been set up
  • Design has been finalized
  • Engineering work has been done
  • Content/Copy has been added
  • Website is accessible
  • Launch

@gideonthomas gideonthomas mentioned this issue Aug 12, 2016
Closed
@hannahkane
Copy link
Collaborator

Awesome job to everyone who worked on this!

@gideonthomas gideonthomas mentioned this issue Sep 6, 2016
Closed
@kaythaney
Copy link

+100! :)

On Tue, Sep 6, 2016 at 12:24 PM, hannahkane notifications@github.com
wrote:

Awesome job to everyone who worked on this!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#826 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAh17ykLFaclVGi15mc9blI_JIbxC8coks5qnZPQgaJpZM4JWlDy
.

@kaythaney http://twitter.com/kaythaney/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gideonthomas gideonthomas

@hannahkane hannahkane

Labels
Local Impact
Projects
None yet
Milestone
September 2, 2016
Development

No branches or pull requests
4 participants
@kaythaney @gideonthomas @hannahkane @amirad