marquee-pressnomicswp

PressNomics Recap

We were fortunate enough to be asked to attend the 2nd annual PressNomics conference in Tempe, AZ. The 3 day conference was held at the lovely Tempe Mission Palms, and was led by Josh Strebel (@strebel) and Sally Strebel (@BizGirl) of Page.ly (@Pagely). The goal was to host a discussion with a diverse group of passionate and successful WordPress entrepreneurs and experts who are driving the WordPress economy and ecosystem alike.

The conference was kicked off with an absolutely killer talk by Chris Lema (@chrislema), who inspired us to think about our businesses and staff as a way to “draft and develop” teams and people, and to create and grow well-rounded talent. Following Chris was an entertaining talk by Bill Belew (@billbelew_com) on SEO and marketing, with the takeaway ”Hit the Publish button”, “Hit the Publish button”, “Hit the Publish button”… well you get the idea. Bill was one of the most captivating speakers we’ve ever seen; it’s hard to describe, but his speed and delivery kept  us enthralled.

The inspiring talks and speakers continued throughout the two-day conference and moved from theory into practice. Industry leaders offered stories of strategies and innovations that are making an impact for clients, customers and communities and explored what the impact of WordPress can and should be in our economy.

New to the discussion format this year was the introduction of a two-stage setup — essentially allowing a more seamless speaker transition. One speaker would be finishing up on the left side of the stage and the next speaker on-deck would prepare on the right side of the stage. Great idea, great upgrade. One thing we would have liked to see was more small group sessions, with leaders in specific areas of the WordPress-ecosystem chatting more intimately with others about specific topics and concerns that other business owners are experiencing. Our friend Shane Pearlman (@justlikeair) of Modern Tribe (@ModernTribeInc) drove one of these group dialogues in-between speakers. Imagine if this was a standard interactive feature of PressNomics in the future — could be amazing!

pressnomicspress2press4

Oh and we ran into Pauly Shore TWICE.

Want to werk here?

Want To Werk Here?

We’re growing and looking for a full-time, front-end developer with WordPress experience. If you are looking to join a fun and collaborative team, we would love to meet you!

The Job.
We are WerkPress and we are Westwerk. Working alongside our team here at WerkPress, you will be responsible for building, learning and breathing everything web/app and WordPress. You will be bringing designs to life, working on projects both in small teams and independently.

About Yourself.

You’re the right person if you:

  • Know HTML5/CSS, cross-browser development
  • Have PHP/WordPress experience
  • Have  Javascript & jQuery experience
  • Have experience with version control (GIT, SVN)
  • Work well as part of a team, but proactive alone as well
  • Can manage workloads and time efficiently
  • Experience building custom WordPress plugins is a plus
  • Experience with WordPress hosting is a plus
  • Professional experience a plus

Compensation.
This will be determined on your skills and experience. Let us know what your expected salary might be. This is a full-time job.

Location.
We have an Office in NE Minneapolis, MN and prefer on-site, but we’re open to remote employment based on geography.

Do it.
If you want to join our team, fill in the form below. What you should send us:

  • Details of your experience and development background/Resume
  • Links to your previous work, code samples, sites, etc.
  • What makes you the right fit
  • How we can contact you

Other.
Not what you’re looking for? We are always looking for individual qualified freelance contractors – please send all inquires via email to travis AT werkpress.com

And please, no solicitations.

Continue reading

Sign Up

Sign Up for our newsletter here. We’ll send you cool WordPress tips, tricks, and news. No spam, we promise.

  • This field is for validation purposes and should be left unchanged.