Icons to replace CSS formatted sections on GitHub

I researched The Noun Project icons and learned some interesting things. I have a concern about their giving credit each time we use the icons (that’s a small but added burden with each LP).

With that said, I have some examples below. I’m using links (to avoid having to give attribution).

Otherwise, I’ve looked at a few “free” icon sites and they seem to be aggregators of other people’s work. Having used images and sound files, I know that sometimes the licensing information can be incorrect, either accidentally or intentionally.

Our symbols are simple. I can’t draw a straight line, but I could use Sketch or whatever to duplicate what we already have. In our meeting Thursday we can discuss what the group would prefer.

This is from their FAQ:

What’s the difference between a paid and a free account?
Both free and paid members get access to all the icons. As a free member, you must give credit to the icon’s designer each time you use their icon. NounPro members get unlimited royalty-free licenses (no need to worry about attribution), can download icons in any color, and get access to all of our apps for quicker access.

Note: free icons are black and white only. To use colors (like the WP standardized colors) we must become paid members.

WARNING: Icons must come from the url thenounproject.com. There is a malware site called nounproject.org that installs wonderful “extensions” to the user’s button if they click “continue.”

INFO

Serifed “i” in black dot
https://thenounproject.com/search/?q=info&i=598163

Serifed “i” alone
https://thenounproject.com/search/?q=info&i=817990

Sans Serif “i” in black circle
https://thenounproject.com/search/?q=info&&i=407794

Italic “i” in black dot
https://thenounproject.com/vityavorobyev/collection/information/?i=817950

TIP

Line drawing of light bulb
https://thenounproject.com/search/?q=tip&i=1309839

Black lightbulb shape
https://thenounproject.com/maxim221/collection/lightbulbs-pt2/?i=1502297

ALERT

Black waving flag shape
https://thenounproject.com/search/?q=flag&i=233075

line drawing of waving flag
https://thenounproject.com/search/?q=flag&i=102470

WARNING

Warning triangle line drawing
https://thenounproject.com/search/?q=warning&i=229734

Black warning triangle
https://thenounproject.com/search/?q=warning&i=209187

Circle with “X”
https://thenounproject.com/search/?q=X&i=323767

Black dot with “X” outline
https://thenounproject.com/search/?q=X&i=327740

Black dot with white “X”
https://thenounproject.com/search/?q=X&i=653848

Recap of February 15, 2018 Meeting

@Josh McIntyre did get the project set up in GitHub for moving lesson plans over. https://github.com/orgs/wptrainingteam/projects/2

@chetan200891 got his first lesson plan converted from Make to GitHub. Yay! It’s a nice confirmation that the video that @pbrocks put together can help new folks get started. https://github.com/wptrainingteam/widget-areas

@Josh McIntyre will add all the LPs to the GitHub Project Board. He created issues for the ones that already had a repository. The issues can be assigned to people so we know who is working on what.

@juliekuehl We may actually have to recreate images and perhaps even rewrite some lesson plans in the process. But that can be done once things are in GitHub. Those can be issues we create on the new repo.

@juliekuehl: So, the update on the GitHub transition is that the project board is set up, the process to move lesson plans from Make to GitHub is documented, and a new team member successfully migrated a lesson plan.

@juliekuehl: We still need to work on the style guide due to the limitations of Markdown and GitHub.

@donkiely has been helping with the style guide but might not be available for the next few weeks

@estes.chris will get options on icons to replace the color notation on Make.

@juliekuehl: So the action items for the week are:

1) @Josh McIntyre will set up the remaining lesson plans on the project board
2) @estes.chris will identify possible icons that can be used as visual cues in Markdown
3) we can all move lesson plans over as needed.

@chetan200891 I have copied some other lessons. I think they are ready to commit. He used the Markdown editor: https://www.browserling.com/tools/html-to-markdown

@jillbinder: Much progress on the final pieces of the diversity speakers trainings. And a question, a request, and a double-checking something.

1. I finished the workbooks and got them up. For now they are google documents in my own account, just because people needed them and they needed to go somewhere. Do we have a google account I can use or is there another way I should be doing this?
2. I did the changes needed to the workshop materials. One of the things I did was removed the sections that repeat in the first three lessons. In lessons 2 and 3 I say basically “go refer to lesson 1 for this section.” Could someone could look it over and let me know if it works as is?
3. Just a note that I haven’t started on slides yet but will very soon. The last decision we made on those is I’m creating them in reveal.js.

@juliekuehl said it’s fine to have the Google Docs in @jillbinder‘s Google Drive but we will will eventually want a team-owned space. The LPs in Make isn’t going anywhere just yet. We’ll leave it up until we have a full process in place in GitHub. The Reveal.js files will go into the GitHub repository.

@jillbinder will keep the docs in her Google Drive for now but move them over when the transition to GitHub is complete.

@pbrocks put a reveal.js presentation on GitHub at https://github.com/wptrainingteam/info-presentation/tree/master/js. It can be used as an example.

@juliekuehl suggested it is worth documenting how to best upload reveal.js slide decks.

@jillbinder requests that someone can look over how she solved the repeating sections. @juliekuehl will review them by next week.

Meeting Agenda for 15 February 2018

Please join us later today at 20:30 UTC in the #training Slack channel for our weekly meeting! A brief agenda for today:

1. Welcome
2. Update on GitHub transition
3. Updates on other current projects
4. Open announcement/discussion time

If you have any other items to add to the agenda, please list them in the comments. If you have progress updates but will not be able to make the meeting, please comment on this post or leave a note for the team in Slack. We’ll see you soon!

Recap of February 8, 2018 meeting

@juliekuehl announced the screencast for using GitHub is up at https://github.com/wptrainingteam/contributor-resources.

Regarding transferring LPs:

@juliekuehl
I’m not sure if we’re ready for the next step to start moving lesson plans.
We might be, but here’s a couple of things to think about first.
1) We will need to tweak our style guide to reflect the realities of working in GitHub with Markdown rather than at Make with HTML.
2) We’ll need a process to track what’s been done/needs doing.

I’ll start with some thoughts on those action steps:
1) Set up project board in GitHub
2) Work on updating style guide (icons included)
3) Assign lesson plans for transferring/editing
4) Screencast of how to upload images and other supporting files
5) Screencast of how to do pull requests for updates once lesson plans are in place in GitHub

@Josh McIntyre volunteered to do step 1 by looking at the audit file from WCUS and create a list in the project board. Then they can be assigned from there.

@juliekuehl: Regarding the icons, perhaps we could use inline images from The Noun Project. https://thenounproject.com/

@pbrocks posted a “Markdown to GitHub Converter” screencast at http://take.ms/MsLvH.

@juliekuehl requested for @Josh McIntyre have the project board set up by next meeting.

If all tasks are done we may be ready for “The Big Move.”

Meeting Agenda for 8 February 2018

Please join us later today at 20:30 UTC in the #training Slack channel for our weekly meeting! A brief agenda for today:

1. Welcome
2. Update on GitHub transition
3. Updates on other current projects
4. Open announcement/discussion time

If you have any other items to add to the agenda, please list them in the comments. If you have progress updates but will not be able to make the meeting, please comment on this post or leave a note for the team in Slack. We’ll see you soon!

Recap of 1 February 2018 Meeting

@juliekuehl is still working on the GitHub screencast

@jillbinder gave an update on the Diversity Speaker Training: both small and medium to-do items need doing but there is now a deadline of the end of February for an event in Vancouver. Promotion for the the training to be used worldwide in meetups will start soon too, so that helps with motivation!

Also a question about handouts and slides and whether that should just wait for GitHub. @melindahelt suggested to just create what is needed and we’ll figure out the best way to share them, even if it isn’t the final way.

Work on lesson plans has been a little slow because of the anticipated shift to GitHub.

@jillbinder asked about how she could be “gatekeeper” for future changes in some lesson plans. That should also be addressed in the move to GitHub.

Meeting Agenda for 1 February 2018

Please join us later today at 20:30 UTC in the #training Slack channel for our weekly meeting! A brief agenda for today:

1. Welcome
2. Updates on current projects
3. Tasks from lesson plan audit
4. Open announcement/discussion time

If you have any other items to add to the agenda, please list them in the comments. If you have progress updates but will not be able to make the meeting, please comment on this post or leave a note for the team in Slack. We’ll see you soon!

Recap of January 25, 2018 meeting

Meeting called off due to lack of attendance.

Meeting Agenda for 25 January 2018

Please join us later today at 20:30 UTC in the #training Slack channel for our weekly meeting! A brief agenda for today:

1. Welcome
2. Updates on current projects
3. Tasks from lesson plan audit
4. Open announcement/discussion time

If you have any other items to add to the agenda, please list them in the comments. If you have progress updates but will not be able to make the meeting, please comment on this post or leave a note for the team in Slack. We’ll see you soon!

Recap of January 18, 2018, meeting

@juliekuehl review of the work in GitHub

We have an organization page at https://github.com/wptrainingteam/.

We’re going to have a separate repository for each lesson plan.

That’s the repo that I’ve been using as an example to begin with. The idea is that each lesson plan would be its own repo with a README.md file where most of the work is done and an images folder where we could store screenshots. That way they’d be in the same place and easily changed when needed.

Notice there are a bunch of topics associated with the repo. We’ll need to use those to both make our lesson plans searchable as well as use them for our own organizational purposes.

RE: alerts, code sample formatting: the formatting looks to be mostly the same, but I haven’t tested everything. It’s Markdown and not HTML, so there’s that.

@melindahelt: GH has the option to quote things, etc. We should come up with suggested formatting from that.

@juliekuehl: Also, I’ve created a GitHub Page https://wptrainingteam.github.io/. We can use that as a more public-facing page to help organize lesson plans and/or provide additional info to contributors.

@juliekuehl: The other thing I wanted to point out is the organization projects, such as https://github.com/orgs/wptrainingteam/projects/2. This is what I’m hoping would replace the hot mess spreadsheet as a place to keep track of where things are at.

GitHub account required to view projects but content viewable to all.

@melindahelt: As we talked at WCUS, if someone wants to participate but is against joining GH (say, to just write one lesson plan) they can write and submit ands someone on the team can add it.

@juliekuehl: As far as the process of getting lesson plans into GitHub, it’s pretty manual. It’s a copy and paste from make.wordpress.org and then doing some reformatting. Then it’s a matter of downloading any images from Make and then uploading them in GitHub. Then switching over the links in the lesson plan.

Standard tools for source control (commits, pulls track issues, etc.) work.

@juliekuehl: I’d love it if everyone would test it out a bit more. Take an exisiting lesson plan and try to bring it into GitHub and see where you get hung up. Play with the projects / issues / pull requests to work out the processes. I’d like to break it learning now before we get serious about moving everything over.

We need to document some of the processes. Things like creating issues and working in the projects. We’ll need some information for other folks who want to help out.

@juliekuehl is working on a screencast to cover much of this.

Perhaps next week we will delegate some of the GitHub tasks, such as setting up the public page and organizing the projects a bit better if needed.

Any questions should be referred to @juliekuehl in Slack.

@estes.chris to take recently edited LPs and move them to GitHub.