The links to reports under the "Teaching Resources" section are broken links (because they are empty). They need to linked properly once the links are available.

@amirad any updates on turning those report Google Docs into Github pages?

The case study section of resources does not have any links attached yet. This was done on purpose since there was a comment in the spreadsheet containing the resources to not publicly expose them until they're ready.

Once they're ready, we should update the links.

first post!

Adds the basic stuff for getting the site up.

Change existing quote to this instead:

"Through Mozilla clubs I aim to help end the gender technology gap and empower women and girls to create innovative solutions to advance equality in their communities." Baratang Miya, Mozilla Clubs Regional Coordinator.

It seems that the automated deployments triggered from commits to master aren't happening.

The last deploy to gh-pages was March 31, but there have been commits since then.

This may have something to do with the failure of this commit.

We only see the last photo in the "Mozilla Clubs for Women and Girls" section in mobile view. Dunno if we care or not.

Showing up as left aligned (rest are all nicely centered) on mobile, in iOS.

Doesn't add to the list, and reads a bit off.

Hey @amirad, moving this issue to here instead of email.

Right now, I've got this design running locally...

Desktop

Mobile

The logo links to https://www.stickermule.com/

Let me know if you'd like any changes and I'll push it live.

FYI: The following changes were made to this repository's wiki:

• defacing spam has been removed

• Restricting write access to contributors is strongly encouraged. Please make that change (documentation).

These were made as the result of a recent automated defacement of publically writeable wikis.

Add Travis to enable tests and deployment

Based on the project and its timeline outlined here: MozillaFoundation/plan#826, we should talk a little bit about what we can learn from the whole experience.

It would be awesome if @flukeout, @gvn, @hannahkane, @amirad and @kaythaney would share their thoughts that might help inform how we approach future projects similar to this. This is not a requirement at all so if you think that your thoughts are captured by other comments, it's ok to not repeat.

Some things you can comment on could be:

• The development process
• The QA process
• Defining the scope of the project
• Stakeholder communication
• Team communication
• Determining the timeline
• Parallelization of work
• etc.

You could talk about any/all of this and anything else you would like to add (things we did right as well as things we did wrong along with suggestions on how we can improve).

cc @simonwex and @xmatthewx

• A single web page will be generated from markdown partials.
• We will leverage mofo-bootstrap for styling.
• Editing of markdown will take place on master branch. Travis will monitor master for changes, run the build task, and deploy to gh-pages automagically. #6
• For development purposes, there will be a live-reload task monitoring the markdown and CSS for changes, which will rebuild and reload the local page in browser.

When commits are made to master it should trigger a deploy task to gh-pages.

-Mozilla Club Web Titans directs to the wrong link. Needs to be updated to https://thimbleprojects.org/amira/75088/

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please see Mozilla-GitHub-Standards or email [email protected].

(Message COC001)

It would be good to setup a video call to onboard Amira to this repo and explain how the site goes live, how to make edits to the site, when will a dev be needed etc.

This will have to wait until the implementation is done (mostly).

The blog posts fall one below the other in mobile view but they are joined without any demarcation like so:

We should add an OG Image (primarily for when people share the site on Facebook).

https://github.com/mozilla/womenandweb/blob/master/source/index.pug#L13

@gideonthomas will spin up a heroku instance on the changes in #27 so that we can do some QA. Once the link is ready, I'll add it to this issue and assign some tasks to the holders of the stakes.

Milestone has no due date

To be run as part of npm test...

It looks like the close quotation mark is way down. Don't know if this is a real issue though

Thoughts I'm having as I go along...

• Not a fan of these .p-y-3 and .m-x-3 classes
  • Why are their rules !important?
  • Mostly I just want to ditch them, but not sure if that has some unforseen repercussions
  • The difference between a 2 and 3 is often too big
• The indented HTML style is hard to work with, especially when borrowing markup from existing properties (like for the footer)
• Hard to implement proper footer styling, even though it exists in a few places
  • Tried taking markup and CSS from the Science site
  • Had to copy over a few SCSS variables in the process
  • Would like a one-stop-shop link or copy & paste source for complete footer styling
• When adding new images to a subfolder in the /images folder the server needs a manual restart for the image to be available to the front end
• Several times I've "lost" images, they've either reverted to a previous version or disappeared entirely. Not sure how to reproduce. Could it be something in the build process?

Create preliminary wireframes based on this content doc.

Main Goals

• Determine navigation style
  • Side-menu with different sections like the Clubs Guides
  • Fixed header when page scrolls
  • None - just a long scrolling page
• Determine order and placement of content
  • Desktop & mobile
• Identify any missing content or asserts

Questions

• What is the primary objective of the site?
  • To get people to Sign Up?
• What is the main title of the site?
  • Women and Web Literacy?
  • Is there a tagline to go with that?

Assets & copy needed

• Large hero image
• Partner org logos

@amirad - are we able to link to a name? (otherwise, it could be anyone / even made up). would add (getting permission first). it strengthens the call-out.

Currently "open, safe and innovative" - reads better (and more to the program's mission) as inclusive.

The opening quotation mark is almost fully out of view in mobile view. Side-note, can we change the quotes to be less typewriter-y and more like what the design shows?

Text: Privacy
Target: https://www.mozilla.org/privacy/websites/
Position: After Legal, on the far right

I want to create easy to share report templates in github - like we did for web lit https://mozilla.github.io/content/web-lit-whitepaper/

The template above looks great to use - @flukeout anything I need to know or do before adapting it for WWL?

We are moving forward with this design...

• https://redpen.io/pg566c3520217fb839

We're still deciding some aspects of the intro text treatment, but it's not important.

Plan of Attack

• @gvn will set up the necessary HTML scaffolding and markdown files
  • Includes setting up columns where necessary
  • Use placeholder content roughly in the length of what is in the design
• @flukeout will populate with final content and style the page
• @amirad will dig up Collaborator logos
• @amirad to shorten the 2 existing Blog Post descriptions
• @amirad to provide 3rd piece of content for Inclusion section
  • Where the two existing blog posts are

Some extra files

• Annotated PDF with some HEX values
• Source Illustrator File

Moving on from #4 - let's get into some visual design. I made two options based on the wireframes.

• Option 1 - https://redpen.io/wt2d220d6e4acb9655
• Option 2 - https://redpen.io/mw37f8040fc3d8f4a2

Please leave your thoughts and feedback, looking for big-picture stuff like

• Overall feel & tone
• Color palette
• Choice of imagery for the header
• etc.

Will ping the design team for a review as well.

cc @amirad

We've also gathered feedback on the Wireframes during our crit, which raised some good questions. I haven't acted on them yet so as not to delay the visual design phase, but it would be good to address them so we can make changes now or soon...

• Should we include content & calls to action for people looking to find an existing club?
  • We only really target the organizers with our current CTA
• Should we include a case study or a more personal story of some sort?
  • We could expand on the quote that is currently in there maybe, add a face and name?

Add the footer to the site with all the relevant links