Thirteen Blog Tips from a Thirteen Year Old

Notes taken during from E Lema’s presentation at WordCamp Orange County.

Take your own photos

Avoid stock photos, use your own artwork. Otherwise your website looks like everyone else

Use Headings

Everyone skims, keep it short.

Have an opinion

If you have an opinion, share your take. Facts are interesting, but not helpful your opinion is

Put your picture on the website

Build a personal connection

Always be helpful

Tips, opinions, expertise,

Allow comments

A great way to connect with your audience.

Don’t worry about looks

Content is what’s important

Have an About page

Why should people read your page, who are you. Make it personal. You can trust your friends.

Finish when your thought is out

Don’t write more or less than you need to.

You Don’t have to hit publish

Save it and decide later

Hit Publish

What will it take you to feel comfortable to hit publish. Use it.

Keep at it

Breaks are okay, promise to come back

You will find your voice

Don’t be worried it will come naturally with time. Let your voice come to you.

Tips

How do you deal with writers block? Start with a blank page. Choose a theme such as Inktober.

How do you choose a topic to write about about. Choose something you know well.

How often do you post? Once a week, fit it in where you can.

How many incomplete posts do you have? None at the moment. When it goes nowhere… scrap it.

Journal, smartphone notes apps are useful.

Web Accessibility made easy for WordPress

Joseph LoPreste

Joseph LoPreste | https://stpetedesign.com Audits websites for accessibility

NFB, discovered how difficult it is for low-vision users to use the internet

Title 3 lawsuits

Easy Steps

  • WCAG 2.1
    • Text alternative, media, adaptable, distinguishable
    • Keyboard access, time, navigation, seizures
    • readable, predictable, input assistance

11 Steps to Accessibility

11 steps to accessibility
11 steps to accessibility slide from presentation
  • Don’t use click here and read more on links. actually link to what it is.
  • don’t use color to convey meaning
    • such as required fields in red
    • instead use required fields are red and have an asterisk.
  • make the font at least 16px or higher — dependent on actual font size
  • error handling — input fields — review errors below, title is required.
  • tools such as Skip to content, menu, footer.
Free Tools for for web developers slide
Free Tools for for web developers slide
Resources Slide
Resources Slide

Being a model contributor

https://desrosiers.party/wcoc | Jonathan Desrosiers| @desrosj

  • 2007 started using WordPress
  • 2009 started taking a deeper drive
  • 2013 contributions to WordPress
    • a simple css bug fix 🙂
  • WordCamp Providence 2013
    • Contributor Day met @nacin
    • Ticket, Improving passwords for users
    • First experience in actual collaboration to core
  • Lurking Phase
    • watched Slack at .org
  • Volunteering Phase
    • testing patches, administrative tasks
  • 2015 Community Summit
  • 2018 Core Committer
  • 2019 Triage Team
    • Reduce open tickets
  • Why Contribute?
    • Knowledge and Experience
    • Career Advancement
    • Cultures and backgrounds
    • New Friendships
    • FOSS contributions transcend jobs

What makes a great FOSS contributor

  • Be through and careful
  • attention to detail
  • provide very strong details and examples on how to recreate the problem
  • be patient
  • be curious
  • be empathetic
  • Tips to be successful
  • Understand the time requirements and be realistic. Don’t take on to much.
  • Set realistic expectations
  • Understand the projects priorities
    • IE block editor, phase 2 and phase 3
  • All contributions are valuable
  • Remember that you’re not alone
  • Assume good intent, even if frank feedback sounds rough or personal (cultural differences)
  • Don’t be embarrassed by your code
  • Master specific topics. Be an expert it a couple areas
  • Being a generalist has value

How to Contribute

  • Join WordPress Slack
  • Observe Phase
    • Attend meetings and get a sense of how they work — Slack
  • New Contributor meetings
    • Second and Fourth Wednesday every month
  • Do research
  • Volunteer
    • even if its something as simple as meeting summaries
  • Convince the boss
  • Ask for help