Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • dan 3:43 pm on August 28, 2018 Permalink | Reply  

    Toronto WordCamp 2018 site design 

    The 2018 Toronto WordCamp site was redesigned with some visual and esthetic touch-ups to facilitate the upcoming WordCamp on December 1st.

    The redesign process included:

    1. Theme – we are using the WordCamp-Base theme
    2. Images – use of local urban images of Toronto from unsplash
    3. Colors: A 2 color Gradient color scheme from light blue to purple (#511c59 to #3fc7f2). These colors are also used throughout the site for highlights, hover effects, headings etc…
    4. Typography: use of google sans-serif fonts: Montserrat and Lato
    5. Layout: the homepage facilitates 4 cards for the main call to action. Today we are looking for sponsors, volunteers and completion of the planning survey, down the road these cards will be updated to Schedule, Venue, Speakers, After Party, etc..
    6. Icons: The icon set was taken and forked from the open source WordCamp design kit . This kit is an excellent set of resources for any WordCamp.

    Also, signage was created that will be used at the venue to help people get around.

    Home Page ‘Hero’ image with the Toronto skyline, overlayed with branded colors

    Cards with urban images and icons promoting different areas of the site


    Signage for the WP Toronto meetup which will be updated to the WordCamp

    • Andy McIlwain 3:45 pm on August 28, 2018 Permalink | Reply

      Super slick! This is great, Dan. QQ: On the site, are you using a gradient “filter” over top of the Toronto images? In other words, could we periodically replace the photos without fussing with the gradient?

    • dan 3:47 pm on August 28, 2018 Permalink | Reply

      Thanks Andy!
      The footer is with a gradient CSS, the main image and the cards no. I guess for the cards I can do that, but the Hero image is Hard coded into the CSS so it would need updating the css.
      But let me think about it and find a solution…

      • Andy McIlwain 3:51 pm on August 28, 2018 Permalink | Reply

        FWIW I’m doing something similar on WPToronto (background image on parent container, then the rgb colour fill on the child container, then the logo asset). Makes it a bit easier to adjust on the fly.

        For the cards: I noticed the text is embedded in the image instead of overlaying with HTML/CSS. Is there any way for us to do that, or nah? (I know the camp themes can be really finicky.)

        • dan 4:18 pm on August 28, 2018 Permalink | Reply

          Finicky in deed, with the limited tools we have (widgets) it probably can be done, but I will have to see if I have the resources. I will prepare a set of cards (based on the needs) which will be ready in the media library to use.

    • Alex Sirota 8:24 am on August 30, 2018 Permalink | Reply

      This is fantastic Dan. Great work.

      You know I like the image too that was used back from 2015. It’s Gutenberg enough and works well.

      Let’s keep working on this design aesthetic.

      A note : in the mobile view do any of the cards render? I didn’t see them.

      • dan 9:31 am on August 30, 2018 Permalink | Reply

        Thanks Alex. Looking forward we can use this look and feel for other assets in WC and TO meetups.
        I disabled the cards in mobile view as they were filling up lots of space and pushing down the content.Do you feel they are needed in mobile view too?

  • Andy McIlwain 10:33 am on August 27, 2018 Permalink | Reply

    Quick update: The WordCamp Toronto 2018 call for sponsors and call for volunteers are now live.

  • Andy McIlwain 10:58 am on August 13, 2018 Permalink | Reply
    Tags: #meetup,   

    Volunteer details for WCYYZ & WPTO 

    I’ve published a Google doc for finalizing volunteer details for WCYYZ:

    Commenting is open. I’d like to get the Call for Volunteers published by next Monday.

    Related, I’ve published a volunteer application form for the WPToronto group as a whole:

  • Andy McIlwain 3:25 pm on August 10, 2018 Permalink | Reply

    Quick update (x-posting from Slack):

    We’ve sent the venue confirmation paperwork off to Central. With WordCamp Niagara and Montreal both happening this weekend, I feel like we’re in the clear to announce the event + push the site live on Monday and announce via WPTO channels.

    Would be great to have the topic survey ready to go, if possible.

    Aside: Let’s use the tag #wordcamp here on P2 to separate our WordCamp conversations from Meetup and website-related conversations. 🙂

  • Robin 10:12 am on August 10, 2018 Permalink | Reply  

    Survey invitation email v1a issues and questions 2018-08-10 

    I’ve uploaded the draft text of the survey invite email to the Gdrive share, Survey_email_invitation_text_v1a_RAM_2018-08-10, in a text file to facilitate revisions. To read the HTML version, go to Email invitation text v1a 2018-08-10 | Organizing WPToronto.

    There are some issues/questions to resolve in the invitation:

    1. The close date of the survey depends in part on when the invitation is ready to be sent. I’ve provided for 3 weeks assuming we get the invite out by 2018-08-17 Fr.
    2. Can we now refer to the WCTO site and the event date?
    3. The option to complete part of the survey and returned to finish it later depends on which service we use.

    In the setting up of each of the mailings:

    1. personalize each invite with the addressee’s name
    2. add the WCTO 2018 logo
    3. provide the unsubscribe option
    4. use a survey specific email address for contact, questions, etc.

    In the draft, I used an address I created, Change it if another address is available and more appropriate.

    At this time, I envisage one survey for both the Meetup and WC lists. When I finish the survey questions, it may make sense to send a version to each list and thereby get feedback on (say) a generic list versus the other version with single-topics and/or workshop lists.

    Robin Macrae
    2018-08-10 Fr

    • Andy McIlwain 3:14 pm on August 10, 2018 Permalink | Reply

      Timing looks good – with the venue paperwork sent off to Central I feel like we can get the survey up this weekend, and the email out on Monday?

      EDIT: Yes we can refer to the event date and site. Waiting on final confirmation from Central but since the paperwork is cleared w/ the city I’m comfortable announcing tomorrow.

      + Let’s stick with for the email address, better to socialize that since it’s consistent year over year, I think?

    • Andy McIlwain 3:28 pm on August 10, 2018 Permalink | Reply

      Also: I agree on having one survey for everyone. Easier to manage.

  • Robin 10:12 am on August 10, 2018 Permalink | Reply  

    Email invitation text v1a 2018-08-10 

    From: Robin Macrae (WordCamp 2018)
    Subject Line: Tell us what you want at WordCamp 2018 – 3 minute survey

    Hey, [Name]

    This task will take 3 minutes, it’s easy and you can cross it off your list—your good deed for the day.

    We are inviting you because you are a member of the WordPress GTA community and have attended our Meetups or a Toronto WordCamp.

    We’re planning the WordCamp 2018 event scheduled for 2018-012-01 the details of which are on

    Your input is a key to choosing the most useful and relevant sessions for the conference. To do so, we ask you to complete a quick survey for us?

    Survey respondents’ identities will remain anonymous. The results of the survey will shared in the call for speakers.

    Typically, the survey takes just 3 minutes to complete. Please complete it by Friday, September 7th.

    You can complete part of the survey and returned to finish it later.

    Start the survey.

    If you have any questions or any difficulty with the link, please contact me at

    Thank you!

    Robin Macrae
    WordCamp 2018 Organizers

    [WC 2018’s postal address]

    [unsubscribe option]

  • Robin 2:37 pm on August 2, 2018 Permalink | Reply  

    Strategy speakers v2a 2018-08-02 RAM 

    This post is one of a set of posts on the speaker strategy for WCTO 2018 the URLs for which are:

    1. Strategy speakers v2a 2018-08-02 RAM
    2. Generic topics list v2a 2018-07-31 RAM
    3. Single-topic list v2a 2018-07-11 RAM
    4. Workshop topics list v1a 2018-07-27 RAM
    5. Survey questions list v2a 2018-07-27 RAM

    TL;DR This is a 1,000 word text provided as both an update on work-in-progress and a
    request for feedback. You don’t need to read it to participate in the discussion.

    We should go about
    the event’s programming in a way that can be clearly described and explained so that our decisions are transparent to our community. That requires us to articulate a
    strategy and this text is an effort to provide a context as well as specific
    recommendations to that end.

    Strategy options

    In developing the strategy for the programming of WCTO, there are
    several approaches we could take:

    1. random, FIFO
    2. single-topic or themed
    3. session type specific (e.g., tutorials/workshops)
    4. curated for essential topics (e.g., Gutenberg)

    Random/FIFO strategy

    Last year’s WCTO was essentially the random/FIFO strategy in that
    submissions were accepted if their quality was acceptable. The first 40+ that
    met that basic criteria were selected (first in, first out, so to speak).
    Suitable for large events. Not recommended.

    Single-topic strategy

    A single-topic or themed strategy is an event with a topic or
    theme to which all sessions are devoted. It has some distinct advantages. The
    primary disadvantage is for the part of the potential audience that has no
    interest in the topic or theme.

    This strategy includes events that are devoted to a segment of
    users or industry (e.g., beginners, higher education, small business).

    In this strategy, the call for speakers would set out the
    sub-topics in sufficient detail to inform candidate speakers of what each
    session would cover and submissions would be evaluated on the basis of filling
    one of the slots. This is a more structured approach.

    Session type specific strategy

    The third strategy is session type specific and tutorials and
    workshops are a good example. In the case of tutorials and workshops, they may
    be on any topic but the goal is to provide a hands-on experience (à la
    Ladies Learning Code).

    Essential topics strategy

    The fourth strategy is an event curated for essential topics such
    as Gutenberg and, to the extent the number of sessions exceeds the essential
    topics, then any of the other strategies can be used for the balance.

    The process

    We started by discussing the strategies and thought that, given
    the number of sessions, the first strategy to evaluate is the single-topic or
    themed strategy. We decided to generate a list of potential single-topics and
    use that to evaluate the strategy. As an exercise, we thought that ranking the
    single-topics in order of preference from the perspective of potential
    attendees would be something we could quickly do and provide to the organizers
    for discussion.

    We thought it a good idea to include the single-topic list in the

    We have other lists in progress which suit the other strategies.
    The workshop list has sessions the topics of which are again illustrative.

    We have created 3 lists for the strategy process which can be
    included in the survey:

    1. all topics, alpha ordered generic, Generic_topics_list_v2a_2018-07_31_RAM.txt
    2. single-topic or themed, Single-topic_list_v2a_2018-07-11_RAM.txt
    3. tutorials/workshops, Workshop_topics_list_v1a_2018-07-27_RAM.txt

    See Conclusions below on next steps regarding the lists.

    Boston 2018 event

    Alex reviewed
    Schedule |
    WordCamp Boston 2018
    and posted a list of topics to consider. In reviewing
    his list, it looks like a mix of:

    1. topics (e.g., Gutenberg)
    2. skill levels (e.g., Advanced Developers
    3. experience (e.g., Intro to WordPress)
    4. industry (e.g., Higher Education)
    5. session type (e.g., Workshops, Lightning Talks)

    From a strictly topical perspective, the list has 4 topics:
    Content & Social Media, Gutenberg, Intro to WordPress
    and Site Builders. Community would be a 5th.

    It’s noteworthy that the event has 2 Intro to
    sessions on Saturday morning. There are 6
    Gutenberg sessions
    , more than any other topic.

    Another thing that’s noteworthy about Boston is that its
    tracks are the rooms in which sessions are held. That’s what
    Andrea said is what she thinks tracks
    means in our Zoom session on the budget last week.

    The membership survey

    In regard to the survey, there is a draft available for review,
    comments and revisions
    , Survey_questions_v2a_2018-07-27_RAM.docx. When the content of the questions is settled, then the
    text of the questions can be quickly finalized and the survey invitations sent.

    The lists in the survey can be used, revised or dropped depending
    on the feedback and consensus of our group.

    We don’t have any preference regarding the survey service to use.
    SurveyMonkey is the
    most popular and has a free tier. However, we recommend the Advantage
    subscription tier at $34/month for 1-3 months to overcome the free
    subscription’s limits of 100 responses viewable at a time and only a single
    filter. We would also like to use a custom logo, colors and survey URL
    available in Advantage and above.

    Any recommendations for other survey services? (Andy recommended Google Forms and we’ll check it out. That may make the comments on the SurveyMonkey tiers irrelevant. More to follow.)

    Can we spend the amount required for the first subscription

    The next question is to how to send the survey. The
    are options and the recommended one is provide a URL in an email rather
    than include the survey itself in the email (haven’t yet
    checked on the latter technique; see
    Ways to Send Your Survey | SurveyMonkey; some email clients can process the survey responses if within an email message)

    None of the 3 of us has done a survey of this kind before.
    We’ll have no difficulty figuring it out but guidance and help would be

    Survey respondents lists

    The final aspect of the survey planning is the survey respondents

    We have the WPTO Meetup and the WCTO 2017 mailing lists. Are there any issues in using these lists.

    Are there other lists available?

    Let us know if
    you’re familiar with mailing to either list (Andy?).

    Is it an option to
    provide a contacts list to the survey service? In other words, can we generate a contacts list/dump of either list to provide to the survey service? If we used SurveyMonkey, then there are tracking and follow-up benefits to using that technique rather than a Meetup or WC email.


    In conclusion, thanks for getting through this text. Here’s what
    we’d like from you.

    First, review the 3 lists. To revise any one of them, make a copy,
    label it appropriately and fire away. It doesn’t take very long and doing so
    will tune you up for the strategy discussion.

    Second, review the draft survey and provide feedback and changes
    by a means to be determined.

    Third, consider the single-topic list and whether an event using
    one of those topics or another one added to the list could be the strategy for
    the event. If none of them appeal to you and you don’t have any others to
    propose, then this isn’t a viable strategy to you.

    If single-topic doesn’t work, then consider the tutorial/workshop
    list on the same basis. No joy? On to the generic list of topics. This becomes
    our strategy when all else fails. The survey is a key element in learning what
    are the preferences, interests and needs of our members. We would use those
    results to develop a much shorter list as the basis of the call for speakers.

    For the survey, comments and feedback on the questions and use of the lists will be reflected in a new draft and the text edited for clarity and readability. The text for the invitation email is next and can be drafted as the survey is finalized and the respondents list(s) settled.

    • Andy McIlwain 3:19 pm on August 2, 2018 Permalink | Reply

      Regarding the survey tool: Google Forms is free and gives us what we need. There’s also PollDaddy (via Automattic, which we’ve used in the past) and Typeform. For outreach: We have the Meetup members, WPToronto subscribers, and WCTO 2018 subscribers. I can handle distribution through these channels, along with social (FB/Twitter).

      • Robin Macrae 4:29 pm on August 7, 2018 Permalink | Reply

        We’ll check out Google Forms and PollDaddy. Thx.

        When we have the survey in final forms, we’ll provide you with a draft email text and the survey URL.

        Probably a good idea to publish a post on the survey both to announce it as well as encourage people not on our lists to fill out the survey.

        • Andy McIlwain 4:37 pm on August 9, 2018 Permalink | Reply

          Yep – threefold approach: Publish on WPToronto; push out via Meetup email; share via social. Also getting our friendly communities to share out the survey as well, for anyone attending from the extended GTA.

    • Andy McIlwain 3:22 pm on August 2, 2018 Permalink | Reply

      Regarding the balance of topics: Given the focus this year to reboot and simplify (single day, smaller event), I think a balance between essential topics and a secondary “focused topic” is a good mix.

      • Robin Macrae 4:33 pm on August 7, 2018 Permalink | Reply

        Any thoughts at this stage for a split between essential (e.g., Intro to WP) and a focused topic?

        What would you include in essential topics in addition to an Intro to WP?

        Would you see Gutenberg as an essential or focused topic? It looks like it’s a good example of each.

        • Andy McIlwain 4:46 pm on August 9, 2018 Permalink | Reply

          A few essential sessions, focused on what’s happening in the WP world + introducing new users, are always important. For lots of people, WordCamp is their first crash course intro to WP.

          IMO Gutenberg is an essential topic since it’s the cornerstone of WordPress 5.0. With our limited time, I don’t see any sessions going much deeper than an overview.

          So for essentials: intro to WP (broad); using WP (user-oriented); editing in WP (Gutenberg); privacy (since it’s a big focus of 2018’s developments). I could definitely see Gutenberg being a focus topic as well, but I don’t know if it’s mature enough just yet to go all-in as a focus for the camp?

  • Robin 2:37 pm on August 2, 2018 Permalink | Reply  

    Generic topics list v2a 2018-07-31 RAM 

    This post is one of a set of posts on the speaker strategy for WCTO 2018 the URLs for which are:

    1. Strategy speakers v2a 2018-08-02 RAM
    2. Generic topics list v2a 2018-07-31 RAM
    3. Single-topic list v2a 2018-07-11 RAM
    4. Workshop topics list v1a 2018-07-27 RAM
    5. Survey questions list v2a 2018-07-27 RAM
    1. analytics
    2. APIs
    3. business, freelancing (the business of WP)
    4. community, ecosystem
    5. content strategy, development
    6. CSS (styling, frameworks, preprocessors)
    7. customization, admin/dashboard UI
    8. customization, theme (Customizer)
    9. development, DIY vs professional
    10. design, blog and page layouts
    11. domain names
    12. editor, post and page (authoring, TinyMCE, Gutenberg)
    13. functions, hooks, classes, or methods
    14. Gutenberg and the new user experience
    15. hosting
    16. image use, management, optimization, free vs stock
    17. importing and exporting content
    18. installation (getting started with WP itself)
    19. migration (content, site, plugins)
    20. multisite
    21. navigation (menus, TOCs, categories)
    22. optimization (loading speed, images, measurement)
    23. plugins, sets (basic/minimum, key, most popular)
    24. plugins, best in (allow up to 3 categories to be added)
    25. page builders
    26. pages, standard types (about, contact, testimonials,
    27. security (login, HTTPS, firewalls, plugins, hardening)
    28. SEO and SEM
    29. social media (promotion, engagement) (plugins)
    30. maintenance, site (core, theme and plugin updates, backups,
      subscription services)
    31. tags and categories
    32. templates (customization, custom post type, plugins)
    33. theme selection
    34. theme development
    35. themes types and their use cases (child, starter, basic,
      framework, etc.)
    36. traffic, high traffic tips
    37. trends in WP as a publishing platform, a CMS, SaaS
  • Robin 2:36 pm on August 2, 2018 Permalink | Reply  

    Single-topic list v2a 2018-07-11 RAM 

    This post is one of a set of posts on the speaker strategy for WCTO 2018 the URLs for which are:

    1. Strategy speakers v2a 2018-08-02 RAM
    2. Generic topics list v2a 2018-07-31 RAM
    3. Single-topic list v2a 2018-07-11 RAM
    4. Workshop topics list v1a 2018-07-27 RAM
    5. Survey questions list v2a 2018-07-27 RAM
    1. Authoring/Gutenberg (the change and changeover
      mechanics, strategy (incl adoption, customization), custom blocks,
      opportunities/impact on themes, adoption techniques)
    2. Digital workplace/business/transformation or
      digital marketing: what you can do with WP to provide and/or use web services
      for your own business or clients’ marketing, CRM, event management,
      information/data management, project and task management (pick 3 or 4 and
      describe the service provided or received, how implemented, costs,
    3. Ecommerce and competing with Magenta, Shopify
      (comparisons, WooCommerce and other plugins, SEO
      strategies (including local), payments and gateways, success stories)
    4. Mobile-first design and development (why it’s
      important and perhaps crucial, how theme designers address mobile now, the
      changeover options for existing sites, what makes mobile different, native vs
    5. Moving to a more secure world: HTTPS/SSL
      (overview and context, compliance, strategies (absolutism), plugins (there are
      many guides and the challenge is how to deliver the content at the event, not
      the content itself)
    6. SEO/SEM: importance (its role), latest
      developments (the arms race), keywords, what “intent” means, Yoast/AIO plugins,
      analytics, structured data, penalties for insecure sites)
    7. SEO and lead conversion without wrecking your theme and
      : how to select, configure and use banner ads and CTAs, popup or
      slide-in mailing form or special sales offers; chatbots for converting casual
      scanners; push notification; social media icons; related posts and sponsored
      readings; tooltip and popups for getting noticed ads (JS
    8. Theme/page builders (the context (developments
      in the last couple of years), design trends (color palettes, typography,
      animation, sticky elements, mobile first, micro-interactions), design’s
      relevance (who can and should use them), best practices, Gutenberg impact),
      changeover from PHP to JavaScript (JS #4), site,
      page and landing page builders including theme included, addon and slider
      plugins (JS #9)
    9. WP beginners: starting from zero, getting a WP
      site up and running for the new beginner: why WP (set the context); defining
      basic requirements (business, hobby, personal), hosting, 5-minute install,
      theme selection, essential plugins, security, privacy, backup, updates plus a
      start-up checklist, important WP limitations, getting help
    10. WP open to the world: APIs rule, WP’s
      REST APIs (purpose, level of development), headless,
      WP as an app (incl POC, MVP), using WP content in other systems/platforms and
      visa versa (use cases), GraphQL (a competitive spec
      for building and consuming APIs (JS #8))
    • Jack Surveyer 12:43 am on August 3, 2018 Permalink | Reply

      Here is my fast assessment:
      Any of the single topics will easily provide tthe needed 9-10 lectures.
      But will the lectures submitted a)be top notch, b)of broad interest to the WP DIY community that supports it but is clearly wavering towards Wix, Squarespace and Shopify – plus c)will they unlock interest in downstream Meetup some of which could be announced at the WordCamp.
      Here are the topics that MIGHT fit the bill:
      2) and 7) might be combined into WP Promotions and Conversions as a great topic of broad interest. But can we get top notch and not boring specialized presentations.. This combo could absorb some of 6)
      3) and 4) are specialized and not Newbie and/or DIY friendly. Combined to produce great presentations this might be a sleeper.
      5)Mobile is 53% of all browsing and growing. And Pagebuilder/Gutenberg are starting to really cater to Mobile first designs. Also PWA, SPA, and AMP are plugin-able. But will DIYs/Newbies care?
      9)usable but boring – leaves out the WP specialists. So which makes up the bigger segment of our WCamp audience?
      10)usable but to specilized – leaves out DIY and Newbies.
      1) and 8) definitely should be combined. Gutenberg is not replacing or competing with the Classic Editor. It is competing with the fast improving PageBuilders becoming SiteBuilders. And Gutenberg is losing bigtime. Elementor was released 3 months after the the launch of Gutenberg effort. And Elementor now has 1 million+ active installs. I test Gutenberg 2-4 times per week and it is serviceable but no match for Divi, Elementor, Thrive, etc.

      But of more concern is how Gutenberg is released. With or without the Classic editor on board? For existing pages and posts does it take precedence and insert itself in the edit session or does it yield to the previously chosen editor? Howbug free will it be on release? And how will it interface with existing Pagebuilders and Sitebuilders?

      On the stock exchange one can buy VIX investments that measure volatility and vulerability. Right now the VIX price for Gutenberg being a Mess must be increasing.

    • Robin 11:04 am on August 8, 2018 Permalink | Reply


      Should “5)Mobile is 53% …” read “4)Mobile is 53% …”?

      I’ve used the hash symbol to designate the topic number as in #1 Authoring/Gutenberg.

      The idea behind the single-topic strategy is have sessions geared for the various segments of the audience and to devote sufficient time for attendees to feel that they really got something tangible from that topic.

      The one exception is #9 WP beginners. It’s devoted to novices and beginners and so wouldn’t be of interest to the rest of the community. That’s the trade-off to having a day devoted to the intake of new people.

      #2 and #7 could be combined and include some of #6. I don’t know from this comment whether this combination is because neither #2 nor #7 had enough content and interest on their own or that combining them would be a better “topic” albeit without half of each as now described.

      Combining #2 and #7 would mean a focus on digital marketing and marketing automation which admittedly is what most of us think the Digital workplace/business/transformation topic would be. In fact, there’s a lot more to the topic than the marketing aspects. However, I do agree that combining the 2 topics and changing the slant as described would be a popular single-topic event.

      Again in your thought to combine #3 and #4, Ecommerce and Mobile-first design and development, what’s your thinking? Newbies are keen to learn more about ecommerce. I think that Ecommerce is one of those topics that you can easily see novice, intermediate and advanced levels. Doing mobile right is more of a developer topic to my way of thinking although, from a newbie point of view, I think that Mobile-first design and development is a missionary sell well worth making.

      I think #3 Ecommerce may be a popular topic and worth devoting a day.

      IMHO, combining #1 and #8, Authoring/Gutenberg and Theme/page builders would be a mistake. The initial release of Gutenberg is not expected to have any page building capabilities. Those are regarded by many as capabilities coming in future releases. For that reason, as a single-topic, that combination is premature.

      In addition, each of the Authoring/Gutenberg and Theme/page builders topics are ones with substantial interest and relevance with Gutenberg being the topic of the year to my way of thinking. To do it justice for a mixed group of attendees would mean it would have to be the single-topic of the event.

      In regard to “#10 usable but too specialized – leaves out DIY and Newbies.,” I agree but would argue that that is the trade-off in a single-topic event. Any topic devoted to DIY and newbies is by definition unlikely to appeal to intermediate and advanced devs. Ditto for Mobile-first design and development.

  • Robin 2:36 pm on August 2, 2018 Permalink | Reply  

    Workshop topics list v1a 2018-07-27 RAM 

    This post is one of a set of posts on the speaker strategy for WCTO 2018 the URLs for which are:

    1. Strategy speakers v2a 2018-08-02 RAM
    2. Generic topics list v2a 2018-07-31 RAM
    3. Single-topic list v2a 2018-07-11 RAM
    4. Workshop topics list v1a 2018-07-27 RAM
    5. Survey questions list v2a 2018-07-27 RAM
    1. create a custom post type (template) in InVision or Sketch and
    2. design a landing page in a page builder
    3. install a new site (beginner)
    4. create a post in Gutenberg
    5. add privacy (GDPR, plugin)
    6. back up a site (beginner)
    7. use an SEO plugin
    8. promote a post in social media
    9. when and how to use CSS flexbox and grid
    10. when and how to use PWA, AMP
    • Alex Sirota 8:40 pm on August 11, 2018 Permalink | Reply

      I really like the idea of 1 or 2 workshops side by side. Gutenberg hands on is a treat and I think fears are totally unfounded. It’s a really important step forward.

      I think a beginners security backup choosing plugins type workshop would be good too.

Compose new post
Next post/Next comment
Previous post/Previous comment
Show/Hide comments
Go to top
Go to login
Show/Hide help
shift + esc