Meet Make, your friendly small business site builder: Start making for free

Make & Make Plus 1.7

by Corey McKrill on May 4, 2016 / Leave a comment

Today we released Make and Make Plus 1.7. As we mentioned in the beta announcement, it has a lot of big changes under the hood. It also has some great new features! Let’s take a look:

Instant style previews in the Customizer

In 1.7, Make now takes greater advantage of the “postMessage” feature of the Customizer to instantly update the Preview Pane when modifying a style-related theme setting. This includes all Typography, Color, and Background Image settings, as well as many others. Waiting for the preview pane to reload after every font size increment is now a thing of the past!

social-iconsNew interface for managing social icons

In previous versions of Make, you could choose to add icons for your social profiles via a simple form in the Customizer, or as a custom menu. The form was easy to use, but only a limited number of icons were available. The custom menu could accommodate a greater variety of icons, and had more flexibility, but it was not very intuitive to use. With Make 1.7, the two methods have been consolidated into one interface within the Customizer. Paste your social profile URL into the field and watch the icon appear instantly. Drag and drop the icons into any order you want. And with the Social Icons API, you can add even more icons to the list of 53 that are currently available.

Color and typography settings for buttons

Now you can customize the colors and fonts of built-in buttons (comment form, search) and Gravity Forms buttons from right in the Customizer.

One-click migration of theme settings from the parent to the child

Have you ever started a new Make site and gotten everything configured just the way you want it in the Customizer only to realize that there are a few more tweaks you need to make with a child theme? And then, when you activate the child theme, you realize that everything is back to the defaults in the Customizer, because WordPress treats it like an entirely separate theme? Well, we know from supporting our users that it happens a lot. Now when you have a child theme activated, there’s a new “Migrate Settings” entry in the Appearance menu where you can copy all those changes you made in the Customizer from the parent over to the child. Hallelujah!

Make Plus: Sticky headers

With this oft-requested feature, you can choose to have either just the Header Bar or the entire site header remain fixed at the top as you scroll down the page.

Make Plus: Improved Typekit interface

The process of entering your kit ID and loading the contents of your kit into the list of available fonts has been significantly streamlined. Simply paste your ID into the field, and it will instantly test the kit and indicate whether the fonts loaded successfully. Then just head over to any Font Family dropdown and your fonts will be there!

Make Plus: Improved interface for post and page layout settings

We heard from a lot of people that the interface with “the double checkboxes” was confusing at best, so we changed it to be more intuitive.

New users can download Make 1.7 today. Make Plus users — make sure you’ve authorized your plugin to get one-click updates in your WordPress dashboard.

Closed vs Open Communities (and why we choose one over the other for The Theme Foundry)

by Melissa Hill on April 8, 2016 / Leave a comment

You can make a pretty good case that an engaged community ultimately forms the basis of any healthy business. At The Theme Foundry, we have several levels of community. We have our premium support forums here, where we give help and think through solutions with our users. We have our community support forums that we maintain on WordPress.org — which anyone can access to get help with Make. And we have specialized communities — like our Slack channel for Make Plus Professional members.

For the most part, due to the sensitive nature of the topics posted in our forums, we’ve chosen to keep our communities closed. Our members overwhelmingly prefer this for privacy and security reasons. Our Slack communities are more akin to “masterminds” and we try to foster collaboration and share in one another’s successes. So far, we’ve chosen to embrace the closed model for our communities, but lately, we’ve also been considering a more open community for Make users to jam on their site ideas and needs.

In last week’s episode of #CMGRHangout, I had the opportunity to chat with other community managers on the subject of open vs. closed communities. Watch the replay here:

And catch up on the Twitter feed from the show on Storify.

Do you maintain an online community for your business? How do you feel about the open vs. closed model?

Make 1.7 Beta 1

by Corey McKrill on March 30, 2016 / 7 comments

Make 1.7 is now in beta! This release has a lot of big under-the-hood changes, and we need your help with testing so we can make sure the update is as seamless as possible. Especially if you are using a child theme that makes any customizations involving PHP, we need your feedback!

As they say with WordPress core betas, this software is still in development, so we don’t recommend you run it on a production site.

The beta of the Make theme is available here.

The beta of the Make Plus plugin is available to Make Plus license holders. Find it in the Downloads section of your account.

Update: Make & Make Plus 1.7 have been released!

If you think you’ve found a bug, please create an issue on the Make GitHub repo, or send an email to support@thethemefoundry.com and note that you’re testing the beta.

What’s new

The focus of this release was improvements to theme settings and how they are presented in the Customizer.

Here’s a rundown of the front end and admin changes in Make 1.7:

  • Instant style previews in the Customizer
  • A new, improved interface for managing Social Icons
  • Color and typography settings for buttons
  • Support for the Custom Logo functionality introduced in WordPress 4.5
  • One-click migration of theme settings from the parent to the child (coming soon)

And in Make Plus 1.7:

  • A new, improved interface for Typekit
  • An improved interface for single post and page layout settings
  • An option to make the site header “sticky” (coming soon)
  • Style Kits and the Builder’s Quick Start templates feature have been removed

The biggest changes are actually behind the scenes. As Make has continued to evolve and grow in popularity, we’ve realized that we need to be more strategic in how we maintain code and build out new features.

Modular architecture

When we first built Make, most of the functionality was implemented the same way you see a lot of things in WordPress core: lots of procedural, global functions. This strategy keeps the code easy to follow and familiar to those who develop themes and plugins for WordPress. However, it also tends to lead to a couple of common coding pitfalls:

  • Big, complex functions that do too much and can’t be reused
  • A lot of small utility functions in the global public scope that may become dependencies for unintended purposes

What we’ve done in Make 1.7 is deprecate a lot of these global functions and encapsulate related functionality into “module” classes (Note, though, that we aren’t using namespaces, so Make is still compatible with the same minimum version of PHP as WordPress). This allows us to have smaller, more abstract functions that are kept to their intended scope, which makes our code DRYer, more flexible, and easier to test. This in turn lays a robust foundation for future enhancements to the theme and plugin.

Moving away from pluggable functions

The other thing we did when we first built Make was to make nearly all of the functions in the theme “pluggable”. This allows child themes and plugins to override an entire function by defining it before it gets defined in the theme. WordPress core also has pluggable functions, although it is no longer considered a best practice and they are no longer being added.

These pluggable functions in Make can cause problems, because they limit the effectiveness of improvements and iteration of the code. If a child theme overrides a function, we can no longer be sure that the function will return the expected value. If we change the logic within the parent function, the child theme’s version may still be using some or all of the outdated logic.

Many of Make’s pluggable functions are now deprecated in 1.7. In some cases we’ve added new action/filter hooks to maintain customizability.

A full list of deprecated functions is included at the end of this post.

Error reporting

WordPress has a class for handling errors, but it doesn’t have a very good way of surfacing these errors. Since Make 1.7 deprecates a lot of code, we needed a way to display the deprecation notices that would get the site administrator’s attention without disrupting or breaking the layout of the site for visitors.

What we came up with is a notification in the Admin Bar that only displays for logged in users who have the capability to install/change themes.

make-errors

Click on the notification, and an overlay will appear that displays the Make error messages and a backtrace to the location of the error in the code, when possible.

make-error-overlay

These notifications can also be turned off via a filter, but it is more advisable to fix the errors instead. ;)

New APIs

Moving to a modular architecture gave us the opportunity to expand the theme’s APIs to improve developers’ abilities to go further with their Make sites. We haven’t completed the documentation for these APIs yet, but here are a few example uses:

  • Settings: change default values, specify sanitize callbacks that automatically run when the setting value is retrieved.
  • Fonts: add your own web fonts and make them available in the list of font families in the Customizer.
  • Social Icons: change or add to the available icons in the site header/footer.

Deprecated functions

The following functions are deprecated. They will trigger a Make error if used or overridden in a child theme. If there is a direct replacement for the function, it will be called instead.

  • ttfmake_action_backcompat
  • ttfmake_add_customizations
  • ttfmake_admin_notice
  • ttfmake_all_font_choices
  • ttfmake_all_font_choices_js
  • ttfmake_backcompat_action
  • ttfmake_backcompat_filter
  • ttfmake_body_classes
  • ttfmake_builder_banner_css
  • ttfmake_builder_css
  • ttfmake_category_transient_flusher
  • ttfmake_check_package
  • ttfmake_choose_google_font_variants
  • ttfmake_content_width
  • ttfmake_convert_px_to_rem
  • ttfmake_css_background
  • ttfmake_css_color
  • ttfmake_css_fonts
  • ttfmake_css_layout
  • ttfmake_customizer_add_panels
  • ttfmake_customizer_add_section_options
  • ttfmake_customizer_add_sections
  • ttfmake_customizer_background
  • ttfmake_customizer_background_image_group_definitions
  • ttfmake_customizer_control_autoload
  • ttfmake_customizer_convert_theme_mods_filter
  • ttfmake_customizer_convert_theme_mods_values
  • ttfmake_customizer_define_background_images_sections
  • ttfmake_customizer_define_colorscheme_sections
  • ttfmake_customizer_define_contentlayout_sections
  • ttfmake_customizer_define_general_sections
  • ttfmake_customizer_define_typography_sections
  • ttfmake_customizer_get_key_conversions
  • ttfmake_customizer_get_panels
  • ttfmake_customizer_get_sections
  • ttfmake_customizer_init
  • ttfmake_customizer_layout_breadcrumb_group_definitions
  • ttfmake_customizer_layout_comment_count_group_definitions
  • ttfmake_customizer_layout_content_group_definitions
  • ttfmake_customizer_layout_featured_image_group_definitions
  • ttfmake_customizer_layout_post_author_group_definitions
  • ttfmake_customizer_layout_post_date_group_definitions
  • ttfmake_customizer_layout_post_meta_group_definitions
  • ttfmake_customizer_layout_region_group_definitions
  • ttfmake_customizer_navigation
  • ttfmake_customizer_preview_script
  • ttfmake_customizer_register_autoload
  • ttfmake_customizer_scripts
  • ttfmake_customizer_set_transport
  • ttfmake_customizer_set_up_theme_mod_conversions
  • ttfmake_customizer_sitetitletagline
  • ttfmake_customizer_staticfrontpage
  • ttfmake_customizer_stylekit
  • ttfmake_customizer_typography_group_definitions
  • ttfmake_cycle2_script_setup
  • ttfmake_edit_page_script
  • ttfmake_embed_container
  • ttfmake_excerpt_more
  • ttfmake_filter_backcompat
  • ttfmake_font_choices_placeholder
  • ttfmake_font_get_relative_sizes
  • ttfmake_formatting
  • ttfmake_formatting_init
  • ttfmake_frontend_builder_scripts
  • ttfmake_get_all_fonts
  • ttfmake_get_choices
  • ttfmake_get_css
  • ttfmake_get_default
  • ttfmake_get_font_property_option_keys
  • ttfmake_get_font_stack
  • ttfmake_get_gallery_slider
  • ttfmake_get_google_font_subsets
  • ttfmake_get_google_font_uri
  • ttfmake_get_google_fonts
  • ttfmake_get_logo
  • ttfmake_get_plus_link
  • ttfmake_get_relative_font_size
  • ttfmake_get_social_links
  • ttfmake_get_standard_fonts
  • ttfmake_get_view
  • ttfmake_has_sidebar
  • ttfmake_head_early
  • ttfmake_head_late
  • ttfmake_hex_to_rgb
  • ttfmake_is_plus
  • ttfmake_is_preview
  • ttfmake_jetpack_infinite_scroll_footer_callback
  • ttfmake_jetpack_infinite_scroll_has_footer_widgets
  • ttfmake_jetpack_infinite_scroll_render
  • ttfmake_jetpack_remove_sharing
  • ttfmake_jetpack_setup
  • ttfmake_load_textdomains
  • ttfmake_maybe_add_with_avatar_class
  • ttfmake_maybe_show_social_links
  • ttfmake_option_defaults
  • ttfmake_page_menu_args
  • ttfmake_parse_font_properties
  • ttfmake_parse_link_underline
  • ttfmake_plus_styles
  • ttfmake_plus_upgrade_notices
  • ttfmake_pre_wp_nav_menu_social
  • ttfmake_refresh_logo_cache
  • ttfmake_register_admin_notice
  • ttfmake_require_files
  • ttfmake_sanitize_choice
  • ttfmake_sanitize_float
  • ttfmake_sanitize_font_choice
  • ttfmake_sanitize_font_subset
  • ttfmake_sanitize_text
  • ttfmake_scripts
  • ttfmake_setup
  • ttfmake_sidebar_description
  • ttfmake_sidebar_list_enabled
  • ttfmake_upgrade_notices
  • ttfmake_widgets_init
  • ttfmake_woocommerce_after_main_content
  • ttfmake_woocommerce_before_main_content
  • ttfmake_woocommerce_init
  • ttfmake_wp_title
  • ttfmake_yoast_seo_breadcrumb
  • ttfmp_add_admin_notices
  • ttfmp_admin_notice
  • ttfmp_edd_add_color_css
  • ttfmp_edd_get_section_definitions
  • ttfmp_get_app
  • ttfmp_get_duplicator
  • ttfmp_get_edd
  • ttfmp_get_page_duplicator
  • ttfmp_get_perpage
  • ttfmp_get_perpage_metabox
  • ttfmp_get_perpage_options
  • ttfmp_get_post_list
  • ttfmp_get_quick_start
  • ttfmp_get_section_duplicator
  • ttfmp_get_shop_settings
  • ttfmp_get_shop_sidebar
  • ttfmp_get_sidebar_management
  • ttfmp_get_style_kits
  • ttfmp_get_template_collector
  • ttfmp_get_template_url
  • ttfmp_get_text_column_layout
  • ttfmp_get_typekit
  • ttfmp_get_typekit_customizer
  • ttfmp_get_widget_area
  • ttfmp_get_woocommerce
  • ttfmp_post_list_get_section_definitions
  • ttfmp_register_admin_notice
  • ttfmp_register_sidebar
  • ttfmp_register_template
  • ttfmp_sideload_image
  • ttfmp_style_kit_definitions
  • ttfmp_woocommerce_add_color_css
  • ttfmp_woocommerce_get_section_definitions
  • ttfmp_woocommerce_legacy_color
  • ttfmp_woocommerce_product_grid_shortcode
  • ttf_recursive_stripslashes

Deprecated action and filter hooks

The following hooks are deprecated, but will continue to work without disruption. They will still trigger a Make error, however, so their use should be discontinued.

Update: Some of the hooks that were previously listed under “no longer used” have been moved up to the “continue to work” list.

  • make_css
  • make_all_font_choices
  • make_all_fonts
  • make_font_variants
  • make_format_builder_format_models
  • make_get_default
  • make_get_google_fonts
  • make_get_standard_fonts
  • make_get_view
  • make_read_more_text
  • make_sanitize_choice
  • make_sanitize_font_choice
  • make_sanitize_font_subset
  • make_setting_choices
  • make_setting_defaults
  • make_supported_social_icons
  • ttfmake_builder_js_dependencies
  • ttfmake_custom_logo_information
  • ttfmake_custom_logo_max_width
  • ttfmp_color_highlight_description
  • ttfmp_perpage_keys
  • ttfmp_perpage_post_types
  • ttfmp_perpage_view
  • ttfmp_post_list_output
  • ttfmp_post_list_query_args
  • ttfmp_post_list_template_paths
  • ttfmp_shop_layout_product_description
  • ttfmp_shop_layout_shop_description
  • ttfmp_woocommerce_product_grid_output
  • ttfmp_woocommerce_product_grid_query_args

The following hooks are no longer used in the code. They will trigger a Make error, and functions added to the hooks will no longer be called.

  • make_css_font_properties
  • make_customizer_background_image_group_definitions
  • make_customizer_background_sections
  • make_customizer_colorscheme_sections
  • make_customizer_contentlayout_sections
  • make_customizer_header_sections
  • make_customizer_footer_sections
  • make_customizer_control_path
  • make_customizer_general_sections
  • make_customizer_typography_group_definitions
  • make_customizer_typography_sections
  • make_get_google_font_subsets
  • make_required_files
  • make_sidebar_list_enabled
  • make_social_links
  • ttfmp_perpage_allowed_keys
  • ttfmp_style_kit_allowed_option_keys
  • ttfmp_style_kit_definitions

Don’t avoid plugins

by Melissa Hill on March 29, 2016 / 4 comments

If you’re ever interested in the pain points associated with WordPress, you should ask someone in the trenches of providing technical or customer support. We’ve heard it all, over and over again. One recurring theme I’ve noted since my tenure in the support forums is this: users are afraid of installing plugins.

The original tickets are usually about some feature they need on their website. I’ll pick a common example we’ve dealt with — a mailing list subscription form. A user, we’ll call her Jane — asks her theme authors, “How do I add a mailing list subscription form to my website?” and we explain, “The theme doesn’t include this kind of functionality. But you can install a plugin to do this for you.”

Jane balks, “I’m trying to avoid plugins.”

***

I’m sure the first time Jane installed WordPress, she was giddy with power. She instantly sought out a new theme to change the look and feel of the front page. Because the more modern-looking and featured themes on WordPress.org are typically well-maintained, this experience likely went pretty well for her. Change theme = success.

Next, Jane learns about plugins. Understanding that plugins add all kinds of cool things, Jane searches for a social sharing plugin. “This plugin hasn’t been updated in two years…” Well, it’s here in the search! “This plugin hasn’t been tested with your version of WordPress.” What does that even mean? Install, activate. Best case scenario? Sidebars look wonky. Worst is the white screen. What kind of experience has Jane had now? Plugins = things breaking.

Then something magical happens. Jane notices a theme that includes social sharing functions. A lightbulb goes off in her head. It will just work, and that’s all that matters to her.

***

It turns out, the WordPress plugin directory is not the greatest resource for people seeking out well-maintained plugins. Developers might initially have altruistic intentions when they added their plugin, but it’s all too easy to get overwhelmed by the demands of support and maintenance, so abandoned plugins abound. It’s one thing for WordPress folks to understand this is essentially a volunteer gig — but it’s not easily communicated to the other sixty million users out there who expect things to just work by virtue of it being listed on the website.

On the other hand, there are also so many brilliant and useful plugins out there — built by passionate, professional, and generous community members. It’s just harder for new WordPressers to sort those out in the search results.

We shouldn’t be avoiding plugins at all. In fact, I wholly advocate going plugin crazy. Just be smarter and more responsible about it. Look for plugins that have been updated in the last year (at least!). Check out the developer’s other work and suss out whether they’re valued members of the community. And…

Don’t avoid plugins, review them

Most of all, I think we all should be writing useful and insightful reviews for the plugins we’re using — when they work well, and when they don’t. Keep in mind that a review is not the appropriate place to request support. If something is broken, it’s really important to open a thread on the appropriate support forum — even if you end up moving on and using a different plugin.

If the WordPress community would be better about those two items, users would have an easier time sorting through the results for well-supported and updated plugins. I recently went through my own website plugin list and left a review of each one I’d activated and used. I even wrote a review for one I activated and liked, but ended up going with another I liked better. I explained the feature difference in my review, and I hope it’s useful to the next person whose looking for a fancy Instagram integration. 🤓

Here’s a template you can use for your own plugin reviews:

I installed[plugin name] on my blog/business site/portfolio.

The plugin has these features which I really like:

I wish these features could be improved upon:

These features didn’t work for me, even after I tried to get support in the forum:

Overall I would recommend/not recommend this plugin if you’re trying to accomplish __________.

***

I get that reviews and open threads in the WordPress.org forums alone won’t solve the problem of abandoned or poorly coded plugins. I know that we’ll still see unfortunate conflicts between plugins and themes. But I think as a community, we could do a lot better about flagging what we notice. Who knows, your review or your open ticket just may save some new WordPresser from the panic that goes along with their very first white screen of death. It could even save someone from getting so frustrated with WordPress that they jump ship altogether.

Maira Martins #iusemake

by Melissa Hill on January 7, 2016 / 3 comments

Screenshot 2015-12-23 15.12.37

Maira Martins is a Brazillian photographer living in Stockholm, Sweden. She specializes in wedding and portrait photography, defining her style as natural, honest and emotional. On her about page, she explains, “I don’t want to be yet another photographer, shooting yet another wedding… that’s just boring. I am looking for meaningful stories and evocative images.”

Martins recently redesigned her website using Make, and despite not having a background in development or design, managed to capture both her style and purpose with effortless perfection. Her website and blog are full of small touches that convey her personality and philosophy to potential clients.

“I am totally in love with what I crafted for my business using Make,” Martins told us. “I have used other [themes and frameworks] before but was tired of them being so heavy, you know? Everything takes hundreds of clicks to achieve and the website was slow.”

Part of what makes Martins website so wonderful is how she’s leveraged different aspects of the page builder, along with the content features of Make and Make Plus. Martins explains, “I upgraded to Make Plus because I wanted the Post List section, but I ended up finding lots of other things I love and had no idea I needed!”

Screenshot 2015-12-23 14.47.08

Her homepage and portfolio galleries use the Posts List section, along with different taxonomy tags to filter her favorite posts and categorize the types of photography she specializes in. She brilliantly uses the Gallery Slider on her photobooth page, and she makes liberal use of the Format Builder. “The Icons! I love them! I’m always using the hearts on my blog posts and have little diamonds on my pricing list”

Screenshot 2015-12-23 13.06.37

Using Make and Make Plus, Martins also plans for expanding the current site. “One thing I’m planning to do is to create a one page ‘mini site’ with info about my commercial and editorial work! It will be just a page on my normal site, but I’m planning to try some Parallax and use the Banner, Columns, and Posts Lists sections. I have already drafted on paper how I want this page to be and it shouldn’t take me more than 3 minutes to create it with Make Plus.”

Martins enthusiasm for Make and Make Plus lies in its ease of use and efficiency. “I think Make is brilliant! First off, it’s easy to use. Anybody can customize a website and actually understand what they are doing. Secondly, I discovered there is something liberating about Make’s minimalism. I love that I don’t need to struggle with millions of options. All the options are actually linked to my own creativity.” Not only has the redesign impacted the way she showcases her work, it’s also rekindled her love of blogging.

Screenshot 2015-12-23 15.10.21

“The simple but powerful approach of Make has taken me off that bad habit of constantly tweaking my website instead of writing. I now blog more often, because I’m finally free to focus on my content! And my wedding inquiries kinda doubled now that my website is looking amaaazing!”

If you’re looking for a photographer in Europe, check out Maira Martin’s services or follow her on Instagram.

How do you use Make? If you’d like to be featured on our blog or in our #iusemake showcase, reach out via email, Facebook, or Twitter.

An introverted community manager’s guide to surviving WordCamp US

by Melissa Hill on December 21, 2015 / Leave a comment

Since I’m the community manager at The Theme Foundry and I can get to Philly in just a few hours and on one tank of gas, it made sense for me to attend the inaugural WordCamp event earlier this month.

If we’ve met in person, you know I’m pretty introverted. Conferences, and especially high-energy conferences, can take their toll. So instead of writing another standard #wcus recap, because I’m sure you’ve read a million of them by now (Learn Javascript, Deeply, right?), I’d like to offer some insight on how to find connection and value at WordCamp when you’re a hopeless introvert.

IMG_1519

The view from my Instagram at #WCUS. That’s a lot of WordCampers!

Make friends with at least one person who knows everyone else.

While I’ve been involved with WordPress on the ancillary (as a writer, blogger, user, etc.) for years, I’m newer to the WordCamp scene. It’s awkward to go to an event alone and not know anyone though! What I’ve discovered about WordCamps in particular, is that there are always a few people there who actually make a concerted effort to notice those loners and reach out. Inspired by those connections I’ve made, I’ve decided to make a special effort in 2016 to introduce myself to anyone who seems to be struggling to find their footing at WordCamps.

So if you find yourself at a WordCamp I happen to be at, and you look lonely and lost, I’m going to find you. And I’m going to introduce you to that one person I know who knows everyone else.

Attend the talks that interest you, but don’t panic if you miss one (or six).

Courtney OCallaghan

While at WordCamp US I attended a handful of really fabulous talks — and missed more than a handful because I was having fabulous conversations with other folks in the hall, dining room, and around town.

Just a few of the amazing talks I watched included:

What I learned when my blog post went viral – With humor and humility, Happiness Engineer and comedy writer Dennis Hong shared the pitfalls and rewards of accidentally creating viral content.

Open Source and Museums – My inner super-nerd was fascinated by the challenges Mel Choyce and Courtney OCallaghan overcame by embracing open-source culture, technology, and practices when faced with the task of digitizing the Freer and Sackler Galleries entire collection.

Teaching the next generation of WordPress bloggers and hackers – Charlie Reisinger shared an amazing talk about how he and his IT department at Penn Manor School District in Pennsylvania gave students a voice and a platform by choosing WordPress and other open-source technology. The results were nothing short of inspiring.

All the talks that I missed were recorded anyway, and I was able to catch up later (I’m still catching up). I get the FOMO that introverts sometimes struggle with — especially if you just need a quiet break. But it doesn’t have to be that way at WordCamp. While it’s awesome to support the amazing speakers who are innovating in WordPress, you shouldn’t pressure yourself to do ALL the things.

Approach the speakers (and developers, designers, community organizers, etc.) that you admire. Say thanks!

I tried to personally thank the speakers of all the talks I watched, though I missed a few. I also made sure to reach out to WordPress community members that I’ve interacted with on Twitter, in Slack, etc. People go to WordCamp to network, after all. I’ve learned through experience that a simple hello at a WordCamp can lead to business ideas, partnerships, brainstorming sessions, and professional development. Introducing yourself to strangers is hard! Make it easier by just saying, “I saw your talk and thought it was great! Thanks so much for that!”

Use this break from the confines of the desk to move your body! In fact, move all over Philly…

Sometimes reaching out and making friends leads to wacky misadventures. Like walking six miles across Philadelphia at night, experiencing falafel fail, and crashing sponsor after parties with fellow geeky developers (you know who you are! Let’s do it again next year!).

My advice: wear comfortable shoes.

Come ready for surprises. And bring extra bags for the surprises.

Almost every time I introduced myself as a member of The Theme Foundry team, I heard, “Oh! You guys built Make! I love that theme!” Which was super encouraging and exciting. The fact that The Theme Foundry is now synonymous with Make means we’re doing our jobs here. I’m going to work on getting more Makers at WordCamps and meetups in 2016 and if you end up going, I hope you’ll find me and say hello!

One of the differences between WordCamp US and the smaller WordCamps I’ve attended is how busy and crowded the sponsor hallway was. The sponsors really came all out, showing off their enthusiasm and knowledge of WordPress and really engaging the community. I learned a ton — especially about hosting, security, and the Automattic suite of products.

The swag haul alone could have filled another bag and I came home with nearly an entire wardrobe — shirts, hats, socks, and gloves. I’d like to challenge the 2016 sponsors to print up pants of some variety — leggings (my vote!) or sweats? — so I can be fully clothed in swag when I leave.

Notable promotions included the SiteGround Christmas socks and GoDaddy Pro commemorative coins that Michelle Schulp designed. I happened to pull a special black coin from the bag — for which I was rewarded a new Blue Yeti Microphone (was hoping to snag a GoPro to attach to my motorcycle! I’ll console myself by starting a podcast).

And finally, I was surprised by how much I ended up enjoying myself. It’s always difficult for me to venture outside my bubble. One reason I love our distributed team is that I don’t have to interact with the outside world. While the idea of attending a conference with a thousand other people, in a city I don’t know very well is scary, I was surprised by how quickly it is to find a rich and diverse community at WordCamp.

Tickets for WCUS 2016 are already available. Will I see you next year?

Ahead of 2016: A redesigned home for Make

by Melissa Hill on December 10, 2015 / 2 comments

header

Ahead of exciting new features and improvements on deck for 2016, we’ve been busy this fall, brainstorming, planning, and visioning the future of the theme. Today we’re launching a fully redesigned home for the project. Check out the new Make site.

We’ve spent a lot of time chatting with community members, talking with other developers, and getting to know our users and their projects. A multi-purpose theme like Make can be a lot of things to a lot of different people. Make powers the websites of big corporations, local shops, educational institutions, startups, consultants, coaches, artists, writers, and even hobby bloggers. But even with all that variance among our users, we started to notice certain trends emerge. Uncovering those patterns has helped us refocus the future of Make around what matters most:

Your business.

To that end, we spent some time remodelling our branding, retooling our copy, and reimagining our product showcase and documentation in ways that help you find the most important information first. We also chose to redesign the site using cutting-edge Flexbox — a nod to the future of Make.

We’ve rolled out a fully functional demo of Make and Make Plus, so if you’ve been wanting to check out the admin side of things, you can now do so.

Last year we started using Twitter hashtags to connect with Make users and we’ve been blown away by the response! We wanted to feature the #iusemake community more prominently in our redesign, so we’ve created a dedicated page to the amazing sites you’ve been building with Make and Make Plus.

#iusemake

And finally, based on feedback, we’ve changed the name of our Make Plus Developer plan to Make Plus Professional — because we know that there are others in the WordPress ecosphere — marketers, designers, coaches, and implementers putting together client sites. Make Plus Professional has the same features and benefits, access to our Slack channel and partner discounts as Make Plus Developer did, it’s just a new name to better reflect the diversity of our users.


Make is the most exciting project our team has had the pleasure to work on, and looking ahead we only see good things — for both the theme and for the businesses that rely on it to market their work and connect with their communities.

Check out the new Make site and let us know if you have any questions, feedback, or feature requests for an upcoming release!

10 Little Known Make Plus Features

by Melissa Hill on November 19, 2015 / 4 comments

We’ve packed Make & Make Plus full of great features. The builder. The 100+ Customizer options. The eCommerce capabilities. But we’re also proud of the details. Here are ten details we think you ought to know about.:

1. Per page options

With Make Plus, you can remove the header on any page, show or hide sidebars on your default pages and posts. Yes, you read that right. You can choose to show or hide the sidebars on a per-post basis.

2. Typekit integration with the Customizer

Screenshot 2015-11-12 19.11.49

Typekit offers over 130 fonts for free, and if you’re an Adobe CC member, a Portfolio Typekit account is probably included in your subscription. With Make Plus installed, you can add a kit to your site and control the fonts through the Customizer.

3. Widgetized Columns sections

Screenshot 2015-11-12 19.13.13

We know you want the flexibility to add widgets to your page builder pages, so we made the Columns section columns widgetizable (is that a word? It is now!). Click, name your widget section, and then add your widgets in the Customizer (or the Widgets screen). Stumped for what kinds of widgets would go on your page? Maybe a Twitter or Instagram feed? Or perhaps…

4. Post Lists widget

Make Plus includes a Post Lists widget that you can add to a widgetized Column. Why would you want to do this? To replicate a posts-page style list with sidebar on your home/front builder page, of course!

5. Remove padding from bottom of each section

Screenshot 2015-11-12 19.13.44

With Make Plus, you can choose to remove the padding below each section in the builder. How is this useful? If you want to stack Banner sections on top of each other, or hide the site background color between elements with different backgrounds, you’ll want this handy check option (the alternative is to do it via custom CSS in your child theme).

6. Custom HTML IDs

Speaking of custom CSS, Make Plus gives you the ability to add a custom HTML ID or class to each builder section. If writing code is your fancy, you can use this to easily style up similar elements or easily add internal page links (to build a one-page site).

7. Page and section duplication

Does your site use duplicate sections throughout? Perhaps a common banner element unites your pages? With Make Plus you can easily make a copy of any builder page or section and then edit it before you republish.

8. Insert Icon button

Screenshot 2015-11-12 19.14.08

Using icons as part of your site design can help your visitors scan for and find key information on your pages. We made it easy. You can insert any of the 585 icons in Font Awesome’s collection right from the content editor. Bonus: This is actually a feature in Make, you don’t need Make Plus to get your icon on.

9. Format Builder

Screenshot 2015-11-12 19.14.37

The Format Builder lets you select text in the visual editor and create stylized notice boxes, lists, and buttons. Choose the background and border color, font size, and add an icon — without adding any special coding or touching a line of CSS. Use this feature to add button-style Call To Actions on sales pages and in Banner sections — simple!

10. Action Hooks & Filters

We’ve included documentation on Make’s action and filter hooks, so dev savvy Make & Make Plus users can customize and modify the theme to their heart’s content. How far can you push the limits of Make & Make Plus?

Do you have a favorite feature in Make or Make Plus? Any features you’d like to see in a new version? Let us know on twitter with the hashtag #iusemake.

WPCharitable & Studio 164a: #iusemake

by Melissa Hill on November 10, 2015 / Leave a comment

Screenshot 2015-11-06 12.17.10

We’ve featured nonprofit organizations that put Make to use for the greater good in this #iusemake series on the blog before. Today we’re excited to have the folks at Studio 164a — a design and development studio out of Australia. They recently released Charitable, a WordPress plugin designed to help nonprofits achieve even greater success online — and they built their own site using Make & Make Plus.

From the Charitable website:

Thousands of non-profits choose WordPress because it’s free, easy to use and boasts an unparalleled collection of plugins that extend its capabilities.

Charitable is a fundraising plugin that helps non-profits build awareness, empower ambassadors, and raise more money – all with their own website.

Tell us a little bit about your business and what you do?

Studio 164a is a 2-man team in Darwin, Australia. Wes is our Director of Design and helps our clients (a mix of non-profits, startups and social entrepreneurs) create unique brand identities and goal-driven websites. Eric is the Director of Code, and most of his time goes towards building Charitable, a donation plugin.

We launched Charitable just a few months ago, after many discussions with non-profits who were frustrated with traditional fundraising software. We created Charitable so that non-profits have a powerful fundraising solution that plugs directly into WordPress, without any transaction fees.

Even though there are a few other donation options out there for WordPress, we feel like there is still a lot of room to help people solve problems that other plugins aren’t solving. For example, we have a peer-to-peer fundraising extension, which offers a really powerful way for non-profits to grow their fundraising efforts.

Why did you pick Make & Make Plus for the website? Were you looking for specific features?

We needed a website to show off Charitable’s features and sell extensions. We wanted to speed up the development process, so rather than building a site from scratch we decided to look at a few of the page builder themes. Make caught our eye because of its combination of simplicity, flexibility, and ease of use.

Once we started using Make, we realised we could really use the features of Make Plus, so upgrading was a no-brainer.

Make’s integration with Easy Digital Downloads made the process of setting up an eCommerce store quick and easy.

When it came time to relaunching the Studio 164a website, we didn’t think twice about using Make again.

How long did it take you to put a site together? What was the process like? Any favorite plugins?

It took us about three weeks to put the Charitable site together, although it is constantly evolving.

We put together some initial ideas of how we wanted each page to look, and then the process of implementing them was fast and enjoyable. It allowed Eric, our Director of Code, to spend most of his time building Charitable, rather than being held up with website development.

Some of our favourite plugins include:

Ninja Forms
Yoast SEO
WP Rocket
Jetpack

When it came to rebuilding the Studio 164a website, we chose to use Make again. We iterated live on a staging site, and launched within a week!

Has the new site made an impact on the business/brand?

We only had a basic landing page before, so we don’t have much to compare it to, but wpcharitable.com has certainly helped us position Charitable as a professional, reliable fundraising platform.

We’ve been able to use Make to quickly create landing pages where we can focus on specific segments of our target market.

How can we follow you?

We love connecting with people in the WordPress/non-profit/fundraising arenas:

Like us on Facebook: https://www.facebook.com/wpcharitable
Follow us on Twitter: https://twitter.com/wpcharitable

For Studio 164a news and updates, connect with us here:

Like us on Facebook: https://www.facebook.com/Studio164a/
Follow us on Twitter: https://twitter.com/Studio164a

If you’re using Make & Make Plus as the foundation for your site, we’d love to hear about it! Reach out on Twitter using the hashtag #iusemake to grab our attention!

Launching tomorrow? Here’s your to-do list

by Melissa Hill on November 2, 2015 / 2 comments

hands

Do you remember, before WordPress, how long it used to take to put a website together? To code out, from scratch, each page, hardcode each link and image, duplicating your menus and footers across your site (and then editing each page if you needed to update one thing!). Through the #iusemake series on the blog, we’ve seen how people are launching faster and more efficiently than ever. We’ve heard everything from 24 hours to 30 days to put a site together, which is astounding really, when you consider what kind of impact a professionally built web presence can have on a business.

If you need to launch tomorrow, we’ve prepared a helpful checklist of items to go over before you send that announcement email or tweet.

Launch checklist

1. Edit copy

It should go without saying that misspellings and typos are going to impact the professional veneer of your website. But not only should you edit for small mistakes, now’s a good time to take a fine tooth to your website copy for style consistency.

Look for:

  • Headers that have the same format (first letter capitalization, etc.)
  • Consistent use of text header tags (H1, H2, H3, etc.)
  • Brand and industry specific word consistency

After you’ve finished with your site copy, now’s a great time to recheck your social media also — just to make sure your profiles match the new site.

2. Check for broken links (and also on social media icons)

Click every link. Yes. Every link. Even click links you’re certain work. That one dead link could mean the difference between a purchase and a bounce, so take the time to tidy up your menus, site copy, and social icons.

3. Make sure images/banners look good on all devices

In case you haven’t looked at your site on a mobile device before, make sure you get in one good round of testing before you launch. Your images might not be cropping and scaling how you imagined they would, and your content might not be breaking across the screen sizes in a way that makes the most sense to your visitors — and better to fix those tiny details before you go live.

Tip: Start with your mobile design when you begin putting together your site. If it looks good on mobile, tweak it for larger screens, instead of vice versa.

4. Double check your contact form and optin form

Join your own mailing list to see what the confirmation emails look like. Make sure your optin gifts are downloading correctly. Send yourself a test message from each and every form on your site, using different email addresses to test your spam filters.

And finally, if you moved your site from a development site to the live site, David Sutoyo, a Make Plus Developer in our Slack channel mentioned, “One point that I’ve learned to always check: make sure the live site isn’t blocking search engines, since sometimes the staging environment might be set to block them.”

What do you check for when you launch a site? Let us know in the comments or on Twitter. I’ll be collecting your ideas in a tutorial for our Make docs.