away and continue his entrepreneurial journey. He’s working on a few projects, and Post Status is a significant part of where he’s dedicating his time and energy.</p>\n\n\n\n<p>Cory is a long-time friend, and iThemes has been a Post Status sponsorship partner since 2015. Cory understands the community, the role Post Status plays in the space, and he brings so much to the table, from established community relationships to product and business experience.</p>\n\n\n\n<p>We’ve known one another going back to 2010 or so. I got to watch as he navigated the WordPress space as the CEO of a theme company turned plugin company, from inception to exit.</p>\n\n\n\n<p>Cory has so many qualities I admire. Most of all, I admire his honesty, his compassion, his passion for people, and his vision for what’s possible. I look forward to working with a true partner on Post Status after so many years of managing the primary responsibilities with much help from many friends and contractors along the way.</p>\n\n\n\n<p>In addition to Cory and myself, David Bisset and Dan Knauss continue to be integral parts of the Post Status effort. Cory and I are thankful for their energy, consistency, and talents.</p>\n\n\n\n<p>We are working together in Oklahoma City this week to finalize our plans for the 2020 year. We already have a lot planned and are looking to get these new initiatives and processes off to a rocking start.</p>\n\n\n\n<h3>Potential in the WordPress community</h3>\n\n\n\n<p>There is so much potential in the WordPress community, and Post Status plays an important role through news, community, and professional development. We are going to continue to do that, and we are also going to make changes that we think will benefit the community as a whole and Post Status Club Members in particular.</p>\n\n\n\n<p>If you’ve ever thought about joining the <a href=\"https://poststatus.com/club\">Post Status Club</a>, it’s a great time to do so. At a minimum, anyone in the WordPress community should subscribe to the <a href=\"https://poststatus.com/newsletter\">newsletter</a>. If you’ve been a member before, we thank you, and we hope we are able to continue to serve you for years to come — better than ever, better together.</p>\n\n\n\n<h3>Cory\'s thoughts</h3>\n\n\n\n<p>I asked Cory to share a couple of his own thoughts on why he’s investing in Post Status, both with his money and energy.</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>I’ve been a fan and supporter of Post Status since the beginning. At iThemes we were one of Brian’s first sponsors. Over the years I leaned on Brian’s insights and counsel — personally as well as through Post Status — to inform and grow iThemes.</p><p>When Brian approached me about becoming a partner my first reaction was, “Heck yes!” Over our weeks and months of conversations, my excitement grew and grew as our goals and aspirations for Post Status were revealed to be so well aligned.</p><p>I truly believe in what Brian has built. And I only want to be a value add and look forward to coming alongside Brian, the Post Status team and this great community.</p></blockquote>\n\n\n\n<p>We\'re so excited to finally be able to make this official. We look forward to continuing to serve you our readers, our Club members, our partners, and the broader community.</p>\n\n\n\n<p>Onward!</p>\n\n\n\n<h3>Audio & Video Q&A; with Cory and Brian</h3>\n\n\n\n<p>We’ll be announcing more specific plans over the coming weeks, and below is our conversation post-announcement by audio and video:</p>\n\n\n\n\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<div class=\"embed-vimeo\"></div>\n</div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Jan 2020 13:55:21 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Brian Krogsgard\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:36;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:16:\"Matt: Thirty Six\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=50760\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"https://ma.tt/2020/01/thirty-six/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3332:\"<p>I am now solidly entering my late thirties, and fortunately I am in good health, good cheer, and doing one of my favorite things — exploring a part of the world and culture I haven’t experienced before (Maldives and Sri Lanka).</p>\n\n\n\n<p>The past year has included a number of professional milestones including <a href=\"https://ma.tt/2019/09/series-d/\">a significant amount of fundraising</a> and related activity, bringing in <a href=\"https://ma.tt/2019/08/tumblr-the-day-after/\">a major new product to the Automattic family</a>, the <a href=\"https://ma.tt/2019/11/state-of-the-word-2019/\">maturation of Gutenberg in the WordPress ecosystem</a>, launching the <a href=\"https://distributed.blog\">Distributed blog and podcast</a>, and a growth in the breadth and depth of the Automattic team.</p>\n\n\n\n<p>Partially because of the schedule those milestones required, this ended up being my year with the most travel ever since I started tracking: I flew over 515k miles, to 124 cities in 24 countries. I was able to incorporate a <a href=\"https://photomatt.tumblr.com/post/186959053572/some-beautiful-trails-near-aspen-ran-the-heavy\">good amount of running</a> in my routine, started picking up musical instruments again, and learning more about sound and its impact on our lives. I found <a href=\"https://streaksapp.com/\">small daily habits</a>, like a little bit of exercise or stretching first thing in the morning, to be sustainable and high-impact.</p>\n\n\n\n<p>What suffered in 2019 was my <a href=\"https://ma.tt/2020/01/29-books-in-2019/\">book reading time</a> and making a dent on the <a href=\"https://www.theworlds50best.com\">top 50 list</a>. I still check <a href=\"https://www.techmeme.com\">tech news every day</a>, but I had to unplug from daily non-tech news because it was just too hectic — I’ve found a lot of value in <a href=\"https://www.economist.com\">weekly publications like the Economist</a> to make sense of what’s going on in the world with the benefit of a little distance and time.</p>\n\n\n\n<p>Personally my main goals this year are for the health and wellness of my family, incorporating more playing music and photography into my life, and strengthening <a href=\"https://www.calm.com\">my meditation practice</a>. If you’re reading this, I hope to run into you online or in person and this year let’s do our best together to leave the world a little better than we found it.</p>\n\n\n\n<p>All birthdays: <a href=\"https://ma.tt/2003/01/bday/\">19</a>, <a href=\"https://ma.tt/2004/01/so-im-20/\">20</a>, <a href=\"https://ma.tt/2005/01/hot-barely-legal-matt/\">21</a>, <a href=\"https://ma.tt/2006/01/matt-22/\">22</a>, <a href=\"https://ma.tt/2007/01/twenty-three/\">23</a>, <a href=\"https://ma.tt/2008/01/twenty-four/\">24</a>, <a href=\"https://ma.tt/2009/01/twenty-five/\">25</a>, <a href=\"https://ma.tt/2010/01/twenty-six/\">26</a>, <a href=\"https://ma.tt/2011/01/twenty-seven/\">27</a>, <a href=\"https://ma.tt/2012/01/twenty-eight/\">28</a>, <a href=\"https://ma.tt/2013/01/twenty-nine/\">29</a>, <a href=\"https://ma.tt/2014/01/matt-3-0/\">30</a>, <a href=\"https://ma.tt/2015/01/thirty-one/\">31</a>, <a href=\"https://ma.tt/2016/01/thirty-two/\">32</a>, <a href=\"https://ma.tt/2017/01/thirty-three/\">33</a>, <a href=\"https://ma.tt/2018/01/thirty-four/\">34</a>, <a href=\"https://ma.tt/2019/01/thirty-five/\">35</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Jan 2020 09:15:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:37;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"WordPress.org blog: WordPress Leaders Nominated for CMX Awards\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8288\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:78:\"https://wordpress.org/news/2020/01/wordpress-leaders-nominated-for-cmx-awards/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3074:\"<p>Two members of the WordPress leadership team were nominated for excellent work in their field in the first ever Community Industry Awards. <a href=\"https://profiles.wordpress.org/andreamiddleton/\">Andrea Middleton</a> is nominated for <a href=\"https://cmxhub.com/awards-executive\">Executive Leader of a Community Team</a> and <a href=\"https://profiles.wordpress.org/chanthaboune/\">Josepha Haden Chomphosy</a> is nominated for <a href=\"https://cmxhub.com/awards-professional\">Community Professional of the Year</a>.</p>\n\n\n\n<img src=\"https://i0.wp.com/wordpress.org/news/files/2020/01/josepha_and_andrea.jpg?fit=632%2C281&ssl=1\" alt=\"\" class=\"wp-image-8292\" />\n\n\n\n<p><a href=\"https://cmxhub.com/\">CMX</a> is one of the largest professional organizations dedicated to community builders. The awards were open to public nomination, and finalists were chosen by panels of their peers in the CMX community.</p>\n\n\n\n<p>Andrea has been a vital community strategist for the WordPress project since 2011. Her work to build and support a vibrant community has played a part in the success around the popular open source CMS. Her work is sponsored by Automattic, where she leads a team that focuses on educational efforts, funding, and in-person community-driven events that serve a global base.</p>\n\n\n\n<p>Josepha has been the Executive Director of the WordPress project since 2019. Her work to coordinate and guide volunteer efforts spans 20 teams and involves thousands of volunteers. Her work is also sponsored by Automattic, where she leads the open source division that focuses on all aspects of open source contribution including design, development, volunteer engagement, and the health of the overall WordPress ecosystem.</p>\n\n\n\n<h2>Votes are Open</h2>\n\n\n\n<p>Final recipients are chosen with open voting — if you feel like either Andrea or Josepha have had an impact on your careers, your trajectory in the WordPress project, or the health of WordPress as a whole, there are three ways you can show your support:</p>\n\n\n\n<ul><li>Stop by and vote for them (Andrea&nbsp;<a href=\"https://href.li/?https://cmxhub.com/awards-executive\">here</a>, Josepha&nbsp;<a href=\"https://href.li/?https://cmxhub.com/awards-professional\">here</a>)!</li><li>Share this post with your own communities!</li><li>Tweet some inspirational thoughts about your time/experience/learnings with WordPress (using&nbsp;#WordPress, naturally)!</li></ul>\n\n\n\n<h2>Thank You Notes</h2>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>A lot of care and passion goes into making the WordPress Project as fantastic as it is. I think these awards are a reflection of how wonderful the community and ecosystem are, and I appreciate everyone&#8217;s continued trust in my stewardship!</p><cite>Josepha Haden Chomphosy</cite></blockquote>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>WordPress community organizers are some of the most generous and creative people in the world — working with them is exciting and interesting every day. I’m humbled by this nomination; thank you!</p><cite>Andrea Middleton</cite></blockquote>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 15 Jan 2020 21:42:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:16:\"Francesca Marano\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:38;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"WPTavern: Get Involved With Block-Based WordPress Theme Experiments\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96502\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:78:\"https://wptavern.com/get-involved-with-block-based-wordpress-theme-experiments\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4426:\"<p>As the WordPress theme review team wound down their team meeting yesterday, they were finalizing what their focus area for 2020 would be.  The general agreement among members was that block-based themes should be at the top of the list.  There was some pushback from a minority that did not want to see block-based themes at all.  The reality is that themes will be changing in the next year or two.</p>\n\n\n\n<p>As a team, this is the group of people who will ultimately need to set guidelines based on something WordPress has never done before.  They will also need to work diligently to bring theme authors up to speed on how themes of the future will be built.</p>\n\n\n\n<p>At this point, there are many unknowns, but work on <a href=\"https://github.com/WordPress/gutenberg/labels/%5BFeature%5D%20Full%20Site%20Editing\">tickets for full-site editing</a> is happening at a quick pace.</p>\n\n\n\n<p>Allan Cole, Theme Imagineer at Automattic, later invited team members to get involved with the <a href=\"https://github.com/WordPress/theme-experiments\">Theme Experiments project</a> on GitHub.  It is a way for developers in the WordPress community to help steer the theme-development ship.  Currently, the repository is fairly bare-bones and represents only the early work toward creating themes from blocks.  Each sub-directory in the repository will be an individual experiment that explores creating themes using blocks or block templates.</p>\n\n\n\n<p>The <a href=\"https://wptavern.com/initial-documentation-for-block-based-wordpress-themes-proposed\">initial documentation</a> for block-based themes was introduced in early December 2019.  Since then, a handful of contributors have put together some working theme examples to get the ball rolling.</p>\n\n\n\n<p>The repository is <a href=\"https://github.com/WordPress/theme-experiments/blob/master/CONTRIBUTING.md\">open to contributions</a> from anyone.  This would be a good moment for members of the larger theme development community to start sending in pull requests to share their experiments.</p>\n\n\n\n<p>To test any of the experiments in this repository, you need to be running the latest version of the Gutenberg plugin.  You must also enable the &ldquo;Full Site Editing&rdquo; and &ldquo;Full Site Editing Demo Templates&rdquo; options from within the plugin&rsquo;s &ldquo;Experiments&rdquo; screen.</p>\n\n\n\n<h2>Parisienne Theme</h2>\n\n\n\n<img />Screenshot of the Parisienne theme.\n\n\n\n<p>Currently, the only approved theme experiment is the Parisienne theme.  It&rsquo;s a test of how block templates and template parts work.  A <a href=\"https://parisiennetheme.mystagingwebsite.com/\">live demo</a> of the theme is available.</p>\n\n\n\n<p>Don&rsquo;t expect to be blown away.  There are many missing pieces in the Gutenberg plugin, such as blocks for displaying posts and similar items.  The idea is to explore how templating will work and provide feedback to the Gutenberg development team.</p>\n\n\n\n<p>One major concern I have at this point is the flat nature of the two sub-directories for housing templates and template parts.  With the seven template part files in this theme, I worry that we are not learning from the mistakes of the past.  The sub-folders could become unruly, particularly <code>/template-parts</code>, and house dozens upon dozens of files in a real-world scenario.  This is no different from how themes currently work other than the location of the template files.  Now would be a good time to reimagine the folder structure and optimize the organization of theme templates.  For example, group sidebar templates under a <code>/template-parts/sidebar</code> folder instead of dumping everything into one location.</p>\n\n\n\n<h2>Twenty Nineteen and Twenty Twenty</h2>\n\n\n\n<img />Early look at a block-based Twenty Nineteen theme.\n\n\n\n<p>The repository has two open pull requests for experimenting with blocked-based versions of the <a href=\"https://github.com/WordPress/theme-experiments/pull/4\">Twenty Nineteen</a> and <a href=\"https://github.com/WordPress/theme-experiments/pull/5\">Twenty Twenty</a> default themes.  Of the two, the Twenty Nineteen Blocks theme seemed the least broken, despite the original not being designed specifically for the block editor.</p>\n\n\n\n<p>Porting the most recent default WordPress themes is important because it provides theme authors a way to compare how old methods of handling features will work in the new block system.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 15 Jan 2020 21:39:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:39;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:116:\"HeroPress: How WordPress Enabled Me To Work Remotely – Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=3037\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:118:\"https://heropress.com/essays/starting-early-in-tech/#utm_source=rss&utm_medium=rss&utm_campaign=starting-early-in-tech\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:34324:\"<img width=\"960\" height=\"480\" src=\"https://s20094.pcdn.co/wp-content/uploads/2020/01/011320-min-1024x512.jpg\" class=\"attachment-large size-large wp-post-image\" alt=\"Pull Quote: WordPress people tend to be generous, trusting, and helpful.\" /><p><a href=\"https://heropress.com/feed/#indonesian\">Esai ini juga tersedia dalam bahasa Indonesia.</a></p>\n<p>Growing up, I’ve always been surrounded by technology.</p>\n<p>My dad is a programmer, he created my Gmail account and my first blog on Blogger (Blogspot) when I was 10 years old (it’s around 2006?). I filled up my blog with posts resembling diary entries. The content became too private eventually, so I decided to set it on private.</p>\n<p>Besides that first blog, I had about 5 other blogs on Blogger. One was for posts I believed not too private and could be consumed by the public, one was for my class’ blog in middle school, and one for me to learn how to write in English. I don’t remember what the other blogs are for, since I just kept creating and deleting them. I got satisfaction and happiness from pouring my thoughts in writing and publishing them in my blog. Many times, writing my thoughts and feelings helped me process them, even until now.</p>\n<p>Fast forward to high school graduation. Since I love languages (English is one of my favorite subjects!), I actually wanted to major in English in a top public university in my country, but I didn’t get in, so my second option was Information Systems in a private university. There, I learned a lot about IT and business, I learned Java, HTML, CSS, Javascript, and Android programming. I even took some Coursera and Codecademy courses to learn Bootstrap and Ruby on Rails. I was a good student, I love learning the algorithms and I did more than okay, but I didn’t love programming. I’m not that people who can stay calm finding errors in their codes, and then finding out that it’s only missing a character.</p>\n<h3>Meeting WordPress for the first time</h3>\n<p>At that time, my parents built some websites to sell backlinks (don’t hate me). I helped them with the sites, mainly proofreading and formatting the articles, and they would pay me. That’s when I first encountered WordPress. I saw WordPress as something more advanced than Blogger, with more themes and plugins to choose from. The default WordPress websites already looked more professional than Blogger does.</p>\n<p>I also like to earn extra money (who doesn’t?), so I helped a teacher in my neighborhood teaching high school students from my old high school. I don’t know how to explain this, but in Indonesia, it’s common to take extra courses (outside the school) to learn what you’re already taught at school and prepare for tests. So it’s another 2-hour study time after school.</p>\n<p>During another semester, I taught English at a Kumon center (it’s a Japanese franchise for math and English). I also taught about 10 of my peers for 2 semesters and got a pretty good discount for my tuition as a reward. At home, I tried every legal and safe method available to make money online. Some worked, like translating texts from English to Indonesian on Gengo and writing articles in English on Zerys. Some, like online surveys, didn’t. I also created an Upwork account and applied to some jobs there, but I never got one.</p>\n<p>In my last year at university, I had to do a year-long full-time internship. I got mine at a big general insurance company as their IT QC Staff. I learned a lot and met many amazing people there, but when I was offered to continue working there as a Business Analyst, I said no. I wanted to apply for a scholarship for a masters’ degree. And I don’t really like the fact that I have to wake up at 6 and be back home at 7 in the evening and do it all over again the next day.</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2020/01/image2.jpg\"><img /></a>With my colleagues, I’m the one with the white blouse.\n<p>But one thing I realized just now when I’m writing this is, the whole remote work wouldn’t have happened without the internship. My daily 1.5-hour commute to work made me read Medium everyday. And reading people’s stories on Medium made me want to write and share my stories, so I started writing and sharing my stories there. You’ll see in the next 2 paragraphs the significance of this Medium profile in my career.</p>\n<h3>Start working remotely</h3>\n<p>So after the internship, while I prepared for the scholarship application, I went back to my Upwork profile, revised it, and applied to some jobs as a virtual assistant. Starting from a very low pay, I did everything, like formatting WordPress posts (surprise!), designing social media posts, and processing orders for online shops. I work with people from Singapore, Australia, Europe, and America. After a few happy clients, I increased my hourly rate, slowly but surely. I got familiar with common tools used in a remote work setting, like Slack, Asana, Trello, and Google Suites. I also started writing in English a lot more, on my personal blog on WordPress.com and my Medium.</p>\n<p>One day, around 3 months after I started, a job opening on Upwork caught my attention. They’re a WordPress plugin company called Caldera Labs/Caldera Forms, and they’re looking for someone who could deliver consistency on their blog. They want to publish one blog post per week. I sent my proposal along with my Medium profile URL. <a href=\"http://christiechirinos.com\">Christie Chirinos</a> then replied to my proposal. I remembered she mentioned checking my writings on Medium and that I have a ‘great writing tone’. She wanted to ‘meet’ me in video, so she sent me a Calendly link. I notified her that I would be available at 5 a.m. my time. That was my first time seeing Calendly.. (Calendly is awesome!).</p>\n<p>That was also my first time having to be interviewed via video call. I was ecstatic, but panicked. On the day, I woke up at 4, got dressed, and opened my laptop. Weirdly, my wi-fi died that morning. So I went to the nearest McDonalds to get the interview done, and it went great!</p>\n<p>Long story short, I continued to work with my other clients and started working with Caldera Forms for 15 hours a week. Besides Christie, I also met <a href=\"https://twitter.com/Josh412\">Josh Pollock</a>, Ariella, Anchaal, Rosa, Nico, and Swapnil. At first, I was only tasked with formatting blog posts on WordPress following their style guide. Then I was involved in their overall content strategy, like crafting onboarding emails and coordinating with guest writers. But I’ve always felt welcomed since day one at Caldera Forms. We’re a team of only 5-6 people, we had monthly all-hands video meetings, we talked about our day in Slack. It wasn’t like with any of my clients.</p>\n<p>Christie and Josh are also very active in the WordPress community, they had introduced me to the ‘right’ people to connect with. In order to do that, I had to make an account on WordPress’ Slack. I got to know the amazing community behind WordPress. How people voluntarily contribute their time, energy, and skills to the community, from development, marketing, to translating. It was really inspiring. During my time with Caldera Forms, I also went to my first WordCamp, WordCamp Jakarta 2018, sponsored by Caldera Forms!</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2020/01/image3.jpg\"><img /></a>Some swags from WordCamp Jakarta 2018, that’s Wapuu ondel-ondel!\n<p>It’s only natural then that I wanted to have my own WordPress website. I had a WordPress.com blog once, but this one is different. You can see <a href=\"http://ascenciafike.com\">my blog here</a>. I felt like a grown-up using WordPress.</p>\n<h3>Transitioning to full-time</h3>\n<p>One day, Caldera Forms was acquired by <a href=\"http://saturdaydrive.com\">Saturday Drive</a>, the company behind <a href=\"http://ninjaforms.com\">Ninja Forms</a>. Josh, Nico, Rosa, and I ‘moved’ there, too. Josh introduced me to <a href=\"http://jameslaws.com\">James Laws</a>, the CEO. But because I was still freelancing and have a few other clients, we used my old contract on Upwork. Saturday Drive was much bigger than Caldera, with 20+ people onboard, and I was really excited! They have product team, support team, and communications team. When we moved there, they’re also in another big transition, which was switching to remote work.</p>\n<p>After a month working with Saturday Drive using the old contract, James offered me a full-time position to manage their affiliate program. It was morning in the U.S., but it’s already 8 p.m. where I live. I was <i>really</i> excited, but it’s also a really hard decision to make. Taking the offer would mean letting go all of my clients and specializing in one side of digital marketing, which is affiliate marketing. I would also have to work 8 hours a day. I stayed up late that night, discussing the possibilities with my parents.</p>\n<p>The next day, I replied to James’ message and accepted his offer.</p>\n<p>It’s been more than 4 months since I started working with Saturday Drive now (time of writing: January 2020). Obviously, it’s different from freelancing, but I love almost every moment of it.</p>\n<p>We use Basecamp instead of Slack, where we set up different questions for different times of the week. Every Wednesday, we would be asked: “What do you look like today?”. There are also questions like “What are you looking forward to most this week?”, “What were the highlights of your work day today?”, and “Read any good books lately?”. We even have fiction and non-fiction book clubs!</p>\n<p>We also use Basecamp’s method of working, called <a href=\"https://basecamp.com/shapeup\">Shape Up</a>. We work on projects in a six-week cycle, and then we’ll have two weeks of cooldown. In the cooldown period, we get to work on things we want to work on. And before the next cycle starts, we’ll submit pitches about the projects we want to work on next.</p>\n<p>What about video calls? We have a big monthly meeting with all team members, and occasional coffee break chats with 4-5 people. If urgently needed, we would also have video calls for projects. Except for these calls, I work in my time zone’s working hours.</p>\n<p>So far, I love working with Saturday Drive and getting to know the people. Although I can’t really relate to the U.S. culture (almost all of the team members are U.S. based), I relate to the values that Saturday Drive has. Most importantly, I’m proud of the work we’re doing!</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2020/01/image1.png\"><img /></a>We have virtual ‘coffee breaks’.\n<h3>Giving back to the WordPress Community</h3>\n<p>Notice the pattern in my story?</p>\n<p>WordPress people tend to be generous, trusting, and helpful, because the WordPress itself is open-source. WordPress is powered by volunteers, kind people from all over the world doing development, marketing, translation, support, and many more. There are WordPress meetups, local and regional WordCamps, which are organized by organizers and volunteers.</p>\n<p>Because I’ve experienced the generosity of the WordPress people, I wanted to give back to the community. Several months ago, I tried contributing to the Marketing team by attending a few weekly meetings on Slack. But I eventually stopped attending because I was too busy with work (and the meetings are at 10 pm my time).</p>\n<p>Around November 2019, Devin Maeztri from WordPress Indonesia contacted me through Instagram DM. She invited me to join PerempuanWP, an initiative for Indonesian women working in the WordPress world, similar to WomeninWP. So I followed <a href=\"https://twitter.com/PerempuanWP\">@PerempuanWP</a> on Twitter and joined the WordPress Indonesia’s Slack. Not long after that, I contributed to Indonesia’s polyglot team as well, translating the Code of Conduct and revising our Translation Style Guide.</p>\n<p>Currently, I’m preparing an <a href=\"https://wp-id.org/kulgram-4-onboarding-e-mail/\">‘online webinar’ on Telegram</a> and <a href=\"https://wp-id.org/wpjkt-meetup-21-onboarding-email-and-woocommerce-theme-for-your-business\">a talk for WordPress Meetup Jakarta</a>, both about email marketing (both will be done by the time you’re reading this).</p>\n<p>By putting myself out there, or here in this article. I want to represent Asian women. In the future, I hope I can inspire more women, especially Asians, to work remotely.</p>\n<h3>What you should do if you want to work remotely</h3>\n<p>If you’re an introvert, working remotely may sound like a dream come true. Without leaving the comfort of your house (or even your pajamas), you can still work and earn money. But, it’s not all rainbows and butterflies. From my experience, here’s what you should prepare if you want to work remotely.</p>\n<ol>\n<li>You should be comfortable working with computers. All day.<br />\nAt least you can do a basic Google search, because that’s where most of the answers are, especially if you want to start as a general virtual assistant. Take care of your eyes. Stand up and walk around once in awhile.</li>\n<li>It gets boring. You should be OK with <i>not </i>meeting people all day.<br />\nSometimes you just have to focus on your work so much that you can’t afford to get out of the house. But sometimes, the only way to have that focus is to get out of the house and work from a cafe. Just find the balance you need, it’ll get better with experience.</li>\n<li>Learn the English language. Or other international languages.<br />\nIf you want to work internationally, this one is crucial. You won’t be able to work with people from another country if you can’t speak their language.</li>\n<li>Do your best in your current job.<br />\nOne of the best books I’ve read this year was So Good They Can’t Ignore You by Cal Newport. “Don’t follow your passion; rather, let it follow you in your quest to become, in the words of my favorite Steve Martin quote, “so good that they can’t ignore you.”” So, instead of trying to find your passion, enjoy the work you’re doing at the moment, try to master it, and adopt the craftsman mindset. Collect as many skills as you can, and see what those skills can do for the world.<br />\nTLDR; don’t be obsessed with wanting to work remotely. The opportunity will come, eventually.</li>\n<li>Don’t settle for mediocrity.<br />\nJust learn things. As much as you can. From anywhere, about anything. Keep an open mind. Read books, listen to podcasts, and learn new skills.</li>\n<li>Join the community.<br />\nIf you’re working in the WordPress world, join the WordPress community. It’s a great place to learn from and connect with great people.</li>\n</ol>\n<p>Of course, I won’t be able to tell you to follow the same path that I took, but I hope my story and the pointers above can help you to pursue the (remote) career you want.</p>\n<hr />\n<h2 id=\"indonesian\">Bertumbuh bersama teknologi</h2>\n<p>Saya sudah dikelilingi teknologi sejak kecil.</p>\n<p>Papa saya adalah seorang programmer yang familier dengan teknologi. Saat umur saya 10 tahun, Papa membuatkan akun email Gmail dan blog pertama saya di Blogger (Blogspot). Saat itu, artikel blog saya kebanyakan menyerupai diari, catatan dari kejadian sehari-hari yang saya alami. Akhirnya, saya merasa konten tersebut terlalu pribadi, sehingga saya atur aksesnya menjadi pribadi.</p>\n<p>Selain blog pertama itu, saya mempunyai 5 blog lain di Blogger. Satu untuk tulisan yang saya nilai tidak terlalu privat dan bisa dibaca oleh publik, satu untuk blog kelas saya di SMP, dan satu untuk saya belajar menulis dalam Bahasa Inggris. Saya tidak ingat blog yang lain untuk apa, karena banyak yang saya buat lalu saya hapus. Saya merasa puas dan senang saat bisa menuangkan pikiran saya dalam bentuk tulisan. Menulis membantu saya memroses pikiran dan perasaan saya, bahkan sampai saat ini.</p>\n<p>Setelah lulus SMA, saya tadinya ingin kuliah Sastra Inggris di salah satu universitas negeri (saya suka bahasa, Bahasa Inggris mata pelajaran favorit saya!), tetapi karena tidak berhasil masuk, akhirnya saya berkuliah di universitas swasta, mengambil jurusan Sistem Informasi. Di kuliah, saya belajar banyak mengenai TI dan bisnis, saya mempelajari bahasa pemrograman Java, HTML, CSS, Javascript, dan pemrograman Android. Saya juga belajar Bootstrap dan Ruby on Rails secara otodidak lewat Coursera dan Codecademy. Saya bisa memahami pelajaran pemrograman dan mendapat nilai bagus, tetapi saya tidak suka <i>‘coding</i>’. Saya merasa saya tidak cukup sabar untuk menulis kode dan mencari kesalahan dalam kode saya.</p>\n<h3>Bertemu WordPress pertama kali</h3>\n<p>Saat saya kuliah, orangtua saya membangun beberapa website menggunakan WordPress untuk menjual link. Saya membantu mereka mengecek kualitas artikel dan menyusunnya di WordPress, dan mereka membayar saya. Ini pertama kalinya saya bekerja dengan WordPress. Saya ingat, saya menganggap WordPress sebagai platform yang lebih canggih dari Blogger, karena ada lebih banyak cara untuk modifikasi lewat tema dan plugin.</p>\n<p>Saya suka mendapat uang tambahan (siapa yang tidak suka?), sehingga saya membantu mengajar bimbel di dekat rumah. Di semester lain, saya mengajar Inggris di Kumon, di dekat rumah juga. Selain itu, selama 2 semester, saya menjadi mentor di kampus, mengajar 10 orang teman saya yang butuh pelajaran tambahan. Sebagai gantinya, saya mendapat potongan uang kuliah.</p>\n<p>Di rumah, saya juga mencari semua cara yang legal dan aman untuk mencari uang. Saya menerjemahkan teks dari Inggris ke Indonesia menggunakan Gengo dan menulis artikel dalam Bahasa Inggris di Zerys. Saya juga mendaftar di Upwork (marketplace untuk freelancer), apply ke beberapa pekerjaan, tetapi tidak pernah mendapat satupun.</p>\n<p>Di tahun terakhir perkuliahan, saya diwajibkan menjalani magang selama 1 tahun. Saya mendapat kesempatan untuk magang di Asuransi Astra sebagai Staff IT Quality Control mereka. Selama 1 tahun tersebut, saya belajar banyak dan bertemu banyak orang hebat, tetapi saat ditawari posisi tetap menjadi Business Analyst, saya menolak. Saat itu saya ingin mendaftar beasiswa untuk melanjutkan pendidikan S2. Dan saya juga tidak terlalu suka harus bangun jam 6 pagi, sampai di rumah jam 7 malam, dan harus mengulanginya setiap hari.</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2020/01/image2-1.jpg\"><img /></a>Foto dengan teman-teman kantor, saya yang berbaju putih.\n<p>Tetapi satu hal yang baru saya sadari saat menulis ini, kesempatan remote work yang saya miliki sekarang ini tidak mungkin ada tanpa pengalaman magang tersebut. Perjalanan bus ke kantor setiap hari membuat saya rutin membaca Medium. Membaca cerita-cerita orang di Medium membuat saya ingin menulis dan membagikan cerita saya, sehingga saya melakukannya di Medium.</p>\n<h3>Mulai bekerja remote</h3>\n<p>Setelah magang, saat saya mempersiapkan diri untuk mendaftar beasiswa, saya teringat dengan profil Upwork saya. Saya perbarui info diri dan CV, dan mendaftar ke beberapa lowongan sebagai asisten virtual (virtual assistant). Saya lakukan segala hal mulai dari bayaran yang kecil, seperti mem-format artikel di WordPress, desain pos media sosial, dan memroses pesanan untuk toko online. Saya bekerja dengan klien dari Singapura, Australia, Eropa, dan Amerika. Setelah beberapa review yang bagus dari klien, saya menaikkan tarif per jam saya perlahan-lahan. Saya menjadi mahir menggunakan aplikasi yang sering digunakan di lingkungan kerja remote, seperti Slack, Asana, Trello, dan Google Suites. Saya juga mulai menulis lebih banyak artikel lagi dalam bahasa Inggris, di blog pribadi saya di WordPress.com dan Medium.</p>\n<p>Suatu hari, 3 bulan setelah mulai kerja di Upwork, ada sebuah lowongan yang menarik perhatian saya. Sebuah perusahaan plugin WordPress bernama Caldera Labs/Caldera Forms sedang mencari seseorang yang dapat menjaga konsistensi blog mereka. Mereka ingin menghasilkan satu artikel per minggu. Saya mengirim proposal beserta URL profil Medium saya.</p>\n<p>Tidak lama kemudian, proposal saya dijawab oleh salah satu co-founder mereka, <a href=\"http://christiechirinos.com/\">Christie Chirinos</a>. Saya ingat Christie berkata bahwa ia sudah melihat profil Medium saya dan saya mempunyai ‘nada menulis yang bagus’. Lalu, ia mengirimi saya link Calendly (aplikasi untuk mengatur pertemuan secara online, bisa melihat jadwal kosong dari orang yang bersangkutan), dan saya memberitahunya bahwa saya akan dapat bertemu jam 5 pagi keesokan harinya.</p>\n<p>Itu juga merupakan kali pertama saya diwawancara lewat video. Saya senang dan bersemangat, tetapi juga panik. Pada hari H, saya bangun jam 4 pagi, bersiap-siap, dan membuka laptop. Anehnya, hari itu wi-fi saya putus! Saya akhirnya pergi ke McDonalds terdekat untuk mendapatkan koneksi internet. Untungnya, wawancara tersebut berjalan lancar.</p>\n<p>Saya diterima bekerja di Caldera Forms, sambil terus bekerja dengan klien yang lain, karena beban pekerjaan Caldera Forms saat itu hanya 15 jam seminggu, bahkan kurang. Selain Christie, saya juga bertemu dengan Josh Pollock (co-founder), Ariella, Anchaal, Rosa, Nico, dan Swapnil. Mereka berada di Amerika Serikat, India, dan Perancis.</p>\n<p>Awalnya, saya hanya ditugaskan untuk menyusun artikel di WordPress sesuai dengan style guide yang sudah mereka susun. Setelah beberapa bulan, saya dilibatkan di dalam strategi konten mereka secara keseluruhan, seperti membuat email onboarding dan berkoordinasi dengan penulis tamu. Dari awal, walaupun kami belum pernah bertemu secara langsung, saya merasa disambut oleh tim Caldera Forms. Dalam satu waktu, tim kami hanya berjumlah 5-6 orang, dengan pertemuan bulanan melalui video, dan ‘ngobrol’ harian melalui Slack. Pengalaman dengan Caldera Forms tidak seperti dengan klien saya yang lain.</p>\n<p>Christie dan Josh juga sangat aktif di komunitas WordPress, mereka mengenalkan saya ke orang-orang yang tepat. Untuk berkomunikasi dengan orang-orang tersebut, saya harus membuat akun di Slack Make WordPress. Saya jadi kenal dengan komunitas di balik WordPress, bagaimana orang secara sukarela menyumbangkan waktu, energi, dan kemampuan mereka untuk kemajuan komunitas, kode, pemasaran, hingga penerjemahan. Melihat itu semua sangat menginspirasi saya. Selama di Caldera Forms, saya juga dikirim untuk menghadiri WordCamp pertama saya, WordCamp Jakarta 2018!</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2020/01/image3-1.jpg\"><img /></a>Merchandise dari WordCamp Jakarta, Wapuu Ondel-ondel!\n<p>Setelah menghadiri WordCamp tersebut, tentunya saya ingin mempunyai website WordPress sendiri dengan domain nama saya sendiri. Teman-teman dapat melihat blog saya <a href=\"http://ascenciafike.com\">disini</a>. Mempunyai blog dengan domain nama saya sendiri terasa seperti langkah selanjutnya dalam perjalanan karir saya.</p>\n<h3>Proses transisi ke pekerjaan penuh waktu</h3>\n<p>Suatu hari, Caldera Forms diakuisisi oleh <a href=\"http://saturdaydrive.com\">Saturday Drive</a>, perusahaan di balik plugin form builder lainnya, <a href=\"http://ninjaforms.com\">Ninja Forms</a>. Josh, Nico, Rosa, dan saya ‘berpindah’ juga. Josh memperkenalkan saya ke <a href=\"http://jameslaws.com\">James Laws</a>, CEO dari Saturday Drive. Saat itu, kami masih menggunakan kontrak lama saya di Upwork, dengan batas waktu kerja 15 jam seminggu. Di Saturday Drive, semuanya berbeda, tim mereka jauh lebih besar dibandingkan Caldera (ada lebih dari 20 orang) sehingga saya sangat bersemangat! Mereka mempunyai tim produk, tim suport, dan tim komunikasi. Tetapi, selain akuisisi tersebut, mereka juga sedang melewati transisi yang lain, yaitu berubah menjadi perusahaan remote.</p>\n<p>Setelah satu bulan bekerja bersama Saturday Drive dengan kontrak lama saya, James tiba-tiba menawari saya posisi penuh waktu untuk mengelola program afiliasi mereka. Saya sangat senang dan bersyukur mendapatkan penawaran tersebut, tetapi juga mengalami dilema. Mengambil tawaran tersebut dan bekerja penuh waktu dengan Saturday Drive berarti melepas semua klien saya dan harus mengambil spesialisasi <i>affiliate marketing</i> (pemasaran afiliasi). Saya juga harus bekerja selama 8 jam sehari. Malam itu, saya tidak bisa tidur, dan saya berdiskusi dengan kedua orangtua saya yang sama bersemangatnya.</p>\n<p>Keesokan harinya, saya menjawab pesan dari James dan menerima tawarannya.</p>\n<p>Sudah lebih dari 4 bulan sejak saya mulai bekerja dengan Saturday Drive (waktu penulisan: bulan Januari 2020). Bekerja penuh waktu dengan satu perusahaan memang sangat berbeda dengan freelancing (bekerja lepas), tetapi saya menikmati hampir setiap momennya.</p>\n<p>Di Saturday Drive, kami menggunakan Basecamp, bukan Slack, dimana kami dapat mengatur pertanyaan rutin untuk anggota yang lain setiap minggunya. Misalnya, setiap Rabu kami akan mendapat pertanyaan: “Bagaimana penampilanmu hari ini?”. Ada juga pertanyaan-pertanyaan seperti: “Apa yang kamu tunggu-tunggu minggu ini?”, “Apa yang berjalan lancar dari kerjamu hari ini?”, dan “Buku apa yang baru kamu baca dan menurutmu bagus akhir-akhir ini?”. Bahkan kami mempunyai klub membaca untuk buku fiksi dan non-fiksi!</p>\n<p>Kami juga menggunakan metode kerja dari Basecamp, yang disebut <a href=\"https://basecamp.com/shapeup\">Shape Up</a>. Kami bekerja dalam siklus, yaitu 6 minggu mengerjakan proyek, lalu 2 minggu mengerjakan hal-hal yang kami ingin kerjakan (disebut <i>cooldown</i>). Sebelum siklus selanjutnya mulai, kami akan mengumpulkan <i>pitch</i> mengenai proyek yang ingin kita lakukan.</p>\n<p>Bagaimana dengan panggilan/konferensi video? Kami mengadakan pertemuan dengan semua anggota tim setiap bulannya, dan <i>ngobrol </i>dengan 4-5 orang setiap 2 minggu. Kalau diperlukan sekali, kami juga mengadakan panggilan video untuk pekerjaan. Saya bekerja dalam zona waktu Indonesia, kecuali untuk mengikuti panggilan-panggilan ini.</p>\n<p>Sejauh ini, saya menikmati bekerja dengan Saturday Drive dan mengenal orang-orang di dalamnya. Walaupun sulit untuk terhubung dengan budaya Amerika (hampir 90% stafnya berada di Amerika), tetapi saya terhubung dan sangat mendukung nilai-nilai yang Saturday Drive pegang. Dan yang terpenting, saya bangga dengan kerja Saturday Drive sebagai perusahaan!</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2020/01/image1-1.png\"><img /></a>Ngobrol virtual dengan tim Saturday Drive.\n<h3>Memberi kembali ke Komunitas WordPress</h3>\n<p>Apakah teman-teman bisa melihat pola di dalam cerita saya?</p>\n<p>Orang-orang di dalam komunitas WordPress biasanya suka berbagi, sangat percaya kepada orang lain (dan potensi orang lain), dan suka menolong, karena WordPress sendiri bersifat open-source (terbuka). WordPress bisa berjalan karena dibantu oleh para relawan, orang-orag dari seluruh dunia yang secara sukarela menulis kode, membantu pemasaran, penerjemahan, suport, dan masih banyak lagi. Meetup dan WordCamp, baik lokal dan regional, diadakan oleh organizer dan relawan.</p>\n<p>Karena selama ini saya telah merasakan kebaikan dari orang-orang WordPress, saya ingin memberi kembali/membantu komunitas WordPress. Beberapa bulan lalu, saya mencoba berkontribusi ke tim Marketing WordPress global dengan mengikuti beberapa kali pertemuan mingguannya di Slack. Tetapi lama kelamaan saya tidak datang lagi, karena terlalu sibuk dengan pekerjaan (dan pertemuannya diadakan pukul 10 malam).</p>\n<p>Sekitar bulan November 2019, Devin Maeztri dari WordPress Indonesia menghubungi saya lewat DM Instagram. Ia mengundang saya untuk ikut PerempuanWP, sebuah komunitas untuk perempuan Indonesia yang bekerja di dunia WordPress (mirip dengan WomeninWP). Hari itu, saya mulai mengikuti <a href=\"https://twitter.com/PerempuanWP\">@PerempuanWP</a> di Twitter dan bergabung dengan Slack WordPress Indonesia. Tidak lama setelahnya, saya berkontribusi di tim poliglot Indonesia juga, menerjemahkan Kode Etik Komunitas WordPress Indonesia (<i>Code of Conduct</i>) dan merevisi Panduan Penerjemahan (<i>Translation Style Guide</i>).</p>\n<p>Saat ini, saya sedang mempersiapkan <a href=\"https://wp-id.org/kulgram-4-onboarding-e-mail/\">kulgram di grup Telegram PerempuanWP</a> dan menjadi <a href=\"https://wp-id.org/wpjkt-meetup-21-onboarding-email-and-woocommerce-theme-for-your-business\">pembicara di Meetup WordPress Jakarta</a>, keduanya tentang <i>email marketing.</i></p>\n<p>Dengan membagikan pengalaman dan cerita saya, salah satunya melakui artikel ini, saya ingin mewakili perempuan Indonesia dan Asia. Saya berharap saya dapat menginspirasi banyak perempuan di Indonesia dan Asia untuk bekerja secara remote.</p>\n<h3>Apa yang harus Anda lakukan jika ingin bekerja secara <i>remote</i></h3>\n<p>Jika teman-teman adalah seorang yang introver (seperti saya!), bekerja remote mungkin terdengar seperti mimpi yang jadi kenyataan. Tanpa harus meninggalkan rumah (bahkan kadang masih memakai baju tidur), Anda dapat bekerja dan menghasilkan uang. Tetapi tidak semua aspek bekerja remote itu menyenangkan.</p>\n<p>Berdasarkan pengalaman saya, berikut hal-hal yang harus Anda persiapkan jika ingin bekerja secara remote:</p>\n<ol>\n<li>Anda harus siap bekerja di depan komputer. Satu hari penuh.<br />\nPaling tidak Anda harus bisa melakukan pencarian lewat Google, karena akan sangat dibutuhkan untuk bekerja, terutama jika Anda ingin memulai sebagai asisten virtual. Jaga mata Anda. Berdiri dan jalan setiap 30 menit.</li>\n<li>Anda harus siap bosan, dan tidak bertemu orang lain (selain keluarga) selama satu hari.<br />\nKadang Anda harus fokus sekali dengan pekerjaan hingga tidak bisa keluar rumah. Tetapi kadang, satu-satunya cara untuk fokus adalah keluar rumah dan kerja di kafe. Sesuaikan dengan kebutuhan, lama-kelamaan Anda akan menemukan kombinasi yang pas.</li>\n<li>Pelajari bahasa Inggris. Atau bahasa internasional lainnya.<br />\nJika Anda ingin bekerja secara internasional. Poin ini adalah keharusan. Anda tidak akan bisa bekerja dengan orang dari negara lain jika Anda tidak dapat berkomunikasi dalam bahasa mereka.</li>\n<li>Lakukan yang terbaik di pekerjaan Anda saat ini.<br />\nSalah satu buku terbaik yang saya baca di tahun 2019 adalah So Good They Can’t Ignore You oleh Cal Newport. “Jangan ikuti passion Anda; melainkan biarkan passion Anda mengikuti Anda dalam perjalanan, yang Steve Martin sebagai, “bagus sekali hingga mereka tidak dapat mengabaikan Anda.”” Jadi, jangan ikuti passion Anda, tetapi jalani pekerjaan yang Anda punya sekarang sebaik mungkin, coba untuk menguasai kemampuan yang dibutuhkan, dan adopsi cara pikir ‘pengrajin’. Jangan menunggu pekerjaan yang ‘sempurna’, percaya bahwa setiap pekerjaan mempunyai pelajaran bagi diri kita, kumpulkan kemampuan sebanyak mungkin, dan pikirkan apa yang dapat Anda lakukan bagi dunia dengan kemampuan-kemampuan tersebut.<br />\nSingkatnya, jangan terlalu terobsesi dengan ingin bekerja secara remote. Kerjakan pekerjaan Anda sebaik mungkin, kesempatan akan datang pada waktunya.</li>\n<li>Jangan mudah puas.<br />\nApapun tingkat kemampuan Anda saat ini, belajar sebanyak-banyaknya. Darimana saja, tentang apa saja. Tetap terbuka. Baca buku, dengarkan podcast, dan pelajari kemampuan baru.</li>\n<li>Ikut komunitas.<br />\nJika Anda bekerja di dunia WordPress, ikut komunitas WordPress! Selain bisa menolong orang lain, kita juga bisa belajar dari banyak orang hebat dan menambah koneksi.</li>\n</ol>\n<p>Saya berharap pengalaman saya dan tips-tips di atas dapat menginspirasi dan menolong teman-teman yang ingin berkarir secara remote.</p>\n<div class=\"rtsocial-container rtsocial-container-align-right rtsocial-horizontal\"><div class=\"rtsocial-twitter-horizontal\"><div class=\"rtsocial-twitter-horizontal-button\"><a title=\"Tweet: How WordPress Enabled Me To Work Remotely &#8211; Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote\" class=\"rtsocial-twitter-button\" href=\"https://twitter.com/share?text=How%20WordPress%20Enabled%20Me%20To%20Work%20Remotely%20%2D%20Bagaimana%20WordPress%20Memungkinkan%20Saya%20Bekerja%20Secara%20Remote&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fstarting-early-in-tech%2F\" rel=\"nofollow\" target=\"_blank\"></a></div></div><div class=\"rtsocial-fb-horizontal fb-light\"><div class=\"rtsocial-fb-horizontal-button\"><a title=\"Like: How WordPress Enabled Me To Work Remotely &#8211; Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote\" class=\"rtsocial-fb-button rtsocial-fb-like-light\" href=\"https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fstarting-early-in-tech%2F\" rel=\"nofollow\" target=\"_blank\"></a></div></div><div class=\"rtsocial-linkedin-horizontal\"><div class=\"rtsocial-linkedin-horizontal-button\"><a class=\"rtsocial-linkedin-button\" href=\"https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fessays%2Fstarting-early-in-tech%2F&title=How+WordPress+Enabled+Me+To+Work+Remotely+%26%238211%3B+Bagaimana+WordPress+Memungkinkan+Saya+Bekerja+Secara+Remote\" rel=\"nofollow\" target=\"_blank\" title=\"Share: How WordPress Enabled Me To Work Remotely &#8211; Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote\"></a></div></div><div class=\"rtsocial-pinterest-horizontal\"><div class=\"rtsocial-pinterest-horizontal-button\"><a class=\"rtsocial-pinterest-button\" href=\"https://pinterest.com/pin/create/button/?url=https://heropress.com/essays/starting-early-in-tech/&media=https://heropress.com/wp-content/uploads/2020/01/011320-min-150x150.jpg&description=How WordPress Enabled Me To Work Remotely - Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote\" rel=\"nofollow\" target=\"_blank\" title=\"Pin: How WordPress Enabled Me To Work Remotely &#8211; Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote\"></a></div></div><a rel=\"nofollow\" class=\"perma-link\" href=\"https://heropress.com/essays/starting-early-in-tech/\" title=\"How WordPress Enabled Me To Work Remotely &#8211; Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote\"></a></div><p>The post <a rel=\"nofollow\" href=\"https://heropress.com/essays/starting-early-in-tech/\">How WordPress Enabled Me To Work Remotely &#8211; Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote</a> appeared first on <a rel=\"nofollow\" href=\"https://heropress.com\">HeroPress</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 15 Jan 2020 01:00:05 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Fike Komala\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:40;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:104:\"WPTavern: Dollie Platform Launches, Provides Tools to Build and Deploy Pre-Configured WordPress Installs\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96477\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:114:\"https://wptavern.com/dollie-platform-launches-provides-tools-to-build-and-deploy-pre-configured-wordpress-installs\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4720:\"<p>Stratus5, a company that specializes in cloud container management and business service automation, launched <a href=\"https://getdollie.com/\">Dollie</a> today.  Dollie is a cloud-based eCommerce solution for WordPress developers looking to provide white-label hosting services to their customers.  The platform allows developers and agencies to sell custom, pre-configured WordPress solutions to their clients.</p>\n\n\n\n<p>Dollie is built on top of the Stratus5 Cloudware system.  It includes tools like Blueprints, which allows developers to save and clone custom WordPress configurations.  These configurations are saved to the cloud.  Developers can then launch new instances and monetize them at the click of a button.</p>\n\n\n\n<p>It also has management tools such as billing automation, customer resource management, analytics, backups, permissions, and more.  The platform serves sites via isolated Docker containers.  It runs on a modern stack that includes NGINX, PHP 7.3, Redis, and PerconaDB.</p>\n\n\n\n<p>&ldquo;In the simplest terms, we let developers launch their own cloud hosting service similar to Wix or Squarespace but using WordPress,&rdquo; said Trent Lapinski, VP of Dollie and Stratus5 Cloudware.</p>\n\n\n\n<p>Developers can try Dollie for free and only start paying once they are ready to accept customers.  Pricing begins at $100 per month for the first 10 customers.</p>\n\n\n\n<p>Customer billing can be done via Dollie&rsquo;s payment gateway or the developer&rsquo;s gateway of choice.  The system is backed by the WooCommerce plugin, so any payment gateway that supports WooCommerce Subscriptions is available.  There are no limits on the business model that developers employ.  They can set up custom pricing.</p>\n\n\n\n<p>Take a quick tour of how Dollie works:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<h2>Filling a Missing Gap in the Market</h2>\n\n\n\n<p>&ldquo;We built Dollie because there&rsquo;s a competitive gap in the market between the hosting companies and the developers who actually build websites, themes, and plugins,&rdquo; Trent Lapinski.  &ldquo;I&rsquo;ve seen agencies and many of my developer friends constantly stuck in the rat race of trying to find that next customer, get that next download, and struggle to build sustainable businesses. This is the struggle I faced with CyberChimps selling one-off WordPress products.  Meanwhile, the hosting companies have turned into multi-million and even billion-dollar corporations on the backs of these same developers.&rdquo;</p>\n\n\n\n<p>Lapinski feels like Dollie will level the playing field for developers.  He wishes these tools had existed when he bootstrapped his WordPress startup.  The goal is to allow developers to compete on their own terms.  </p>\n\n\n\n<p>&ldquo;By empowering developers to build sustainable products and services and generate reoccurring-subscription revenue, much like the hosting companies have accomplished, we can grow WordPress by helping developers and agencies grow their businesses,&rdquo; he said.  &ldquo;The key is helping them acquire subscription customers so they can forecast, budget, and bootstrap their businesses in a way I never could when I ran my own theme shop.&rdquo;</p>\n\n\n\n<p>The platform is built on top of WordPress and WooCommerce.  The custom-built technology on top of this allows developers to set up white-label cloud services with minimal up-front knowledge.  The biggest requirement is that developers need to be comfortable with WordPress and WooCommerce.</p>\n\n\n\n<p>&ldquo;Bringing these enterprise-level tools to WordPress developers and giving them the freedom to choose their own business models has simply never been done before,&rdquo; said Lapinski.  &ldquo;Dollie automates many of the processes developers have had to work around for decades, and makes saving, cloning, deploying, and monetizing WordPress products and services as easy as a few clicks.&rdquo;</p>\n\n\n\n<p>Dollie takes no part in what developers or agencies charge their clients outside of providing the tools.  That relationship exists directly between the developer and the client.  Dollie gets paid when developers convert subscribing customers to cover the cloud hosting costs.</p>\n\n\n\n<p>They also allow larger agencies to select third-party cloud providers.  They can then license and partner with Dollie to manage their cloud infrastructure.  The goal is to allow developers to scale as large as needed and customize to suit their needs.</p>\n\n\n\n<p>&ldquo;We are optimistic these tools and the freedom we are enabling for our partners will be the point of difference in how developers view their own value in what they can deliver to their clients and customers,&rdquo; said Lapinski.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Jan 2020 21:13:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:41;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"WPTavern: Can the Block Directory and Business Interests Coexist?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96444\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://wptavern.com/can-the-block-directory-and-business-interests-coexist\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5388:\"<p>WordPress.org is not an official marketplace for plugins and themes.  Except for some plugins that are strictly SaaS products, all extensions to the platform are publicly available for the low cost of $0.</p>\n\n\n\n<p>Despite not directly selling through WordPress.org, the plugin directory is a huge source of income for many individual developers and companies via product and service upsells.  Plugins are big business.  Besides a bounty of third-party marketplaces and individual shops, commercial interests often flow directly in and out of the official WordPress site.  For many developers, it essentially serves as a marketplace.</p>\n\n\n\n<p>In December, we dove into an <a href=\"https://wptavern.com/version-1-prototype-of-the-wordpress-admin-block-directory-announced\">early proposal of the WordPress block directory</a>.  The new directory should land within the WordPress software itself in version 5.5 and will house a new type of plugin.  The idea behind the <a href=\"https://wordpress.org/plugins/browse/block/\">block directory</a> is that it will allow plugin developers to create and share one-off blocks that users can install on their websites.</p>\n\n\n\n<p>This is the future of WordPress.</p>\n\n\n\n<p>Love it or hate it, there will come a time when end-users are primarily looking to install individual blocks to solve their problems.  This is not to say that other types of plugins won&rsquo;t exist or have their place.  They will continue to be a major part of the platform.  However, blocks will be a big deal once users can install them at the click of a button via the WordPress admin.</p>\n\n\n\n<p>The question is whether blocks can also be big business.</p>\n\n\n\n<p>Tavern reader Matt Gowdy <a href=\"https://wptavern.com/version-1-prototype-of-the-wordpress-admin-block-directory-announced#comment-316657\">believes the guidelines</a> for the block directory could be an issue.  &ldquo;There&rsquo;s a lot to like here,&rdquo; he said.  &ldquo;Though I&rsquo;m still troubled by the directory submission rules that are fairly stringently not allowing for any sort of promotional link or defined up-sell of any kind so as not to &lsquo;disrupt the flow.\'&rdquo;</p>\n\n\n\n<p>Currently, the <a href=\"https://github.com/WordPress/wporg-plugin-guidelines/blob/block-guidelines/blocks.md\">block directory guidelines</a> make it clear that advertising of any kind is disallowed:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Block Plugins are blocks. They must not include advertisements, prompts, or promotional messages.</p></blockquote>\n\n\n\n<p>On the one hand, it makes sense, particularly for something that is not yet built and will eventually serve as a version 1.0. If every block a user installs begins advertising, it could be a recipe for disaster without some type of standard.</p>\n\n\n\n<p>On the other hand, would the idea of not having an upselling route turn WordPress businesses away?  While many developers would be willing to submit blocks, is this sustainable?  Many of the most popular plugins are backed by businesses.  The more popular any particular piece of software becomes, the more likely it is that the software will need funding to cover maintenance, feature updates, and support.</p>\n\n\n\n<p>&ldquo;More often than not these days, people don&rsquo;t have as much free time to invest in coding just for the fun of it,&rdquo; said Gowdy.  &ldquo;I speak mainly of myself, but I have the notion that while WordPress is still grounded pretty firmly in Open Source (not a bad thing), it&rsquo;s been the open markets that have allowed it to grow as much as it has. I don&rsquo;t think it&rsquo;s wrong to allow people the opportunity (within reason) to make something back off their hard work should they choose. Donations are non-viable in my experience as the vast majority of humanity are way cheaper than they would like to admit.&rdquo;</p>\n\n\n\n<p>Currently, the upcoming directory has a limited number of blocks available.  The WordPress Meta and Plugin teams should expect more.  However, it is unclear whether the guideline will slow its growth.</p>\n\n\n\n<p>&ldquo;Without any sort of up-sell channel (rule-defined or element defined in blocks), we aren&rsquo;t going to see the plethora that we are hoping for, nor in some cases the quality that could be brought in by people working professionally on a block plugin,&rdquo; said Gowdy. &ldquo;The time to define these up-sell and link options is right now.&rdquo;</p>\n\n\n\n<p>Gowdy is not alone in his concerns.  Several others expressed similar opinions in the comments on the <a href=\"https://make.wordpress.org/meta/2019/12/06/block-directory-plugin-guidelines\">block directory announcement post</a>.</p>\n\n\n\n<p>&ldquo;Where WordPress started and where it is now are two separate points in time,&rdquo; said Gowdy.  &ldquo;I hope the Open Source community and the marketplaces can find a way to co-exist here in order to really rev up the platform for the future.&rdquo;</p>\n\n\n\n<p class=\"has-text-color has-background has-white-color has-blue-700-background-color is-style-highlight text-white bg-blue-700\">This post is part of a new <a href=\"https://wptavern.com/category/from-the-comments\">From the Comments</a> series where we highlight interesting points of discussion from comments on WP Tavern articles. The hope is to give these comments, which can sometimes get lost, the attention they deserve.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Jan 2020 20:46:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:42;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"WPTavern: Upcoming Tailwind CSS 1.2.0 Includes Grid Support and New Utilities\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96387\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:88:\"https://wptavern.com/upcoming-tailwind-css-1-2-0-includes-grid-support-and-new-utilities\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3499:\"<p>Adam Wathan, creator of the Tailwind CSS, <a href=\"https://github.com/tailwindcss/tailwindcss/releases/tag/v1.2.0-canary.4\">published the early release notes</a> for the upcoming version 1.2.0 update to the framework.  The new version will include the much-anticipated <a href=\"https://github.com/tailwindcss/tailwindcss/pull/1274\">support for CSS grids</a> and several other useful features for app and website designers.  There are no planned breaking changes with the update.</p>\n\n\n\n<p>Tailwind CSS is a utility-first CSS framework that is quickly gaining support from designers and developers.  Some WordPress themes are starting to pop up in the public sphere that use it, but is more often used as part of the in-house toolset at agencies, in which standards are necessary to keep teams on the same page.</p>\n\n\n\n<p>For developers already using the framework, they can look for an update within days.  &ldquo;Right now I don&rsquo;t have any changes to these features planned, so as long as nobody finds any huge issues I&rsquo;ll tag the real v1.2.0 next week once I get some documentation together,&rdquo; said Wathan on <a href=\"https://twitter.com/adamwathan/status/1214982042083090433\">Twitter</a>.</p>\n\n\n\n<p>Now is a good time for new developers to start tinkering with the CSS framework.  With the addition of new CSS grid classes, there is little that is not possible for the majority of use cases.</p>\n\n\n\n<p>I have been building with Tailwind, or a subset of its classes, for about a year now.  Aside from highly-custom scenarios, I have been able to build most projects while writing little CSS code.  For someone who comes primarily from a developer background, it has been a godsend for quickly putting together complex layouts.  CSS grid support was the big item I had been waiting for.  I had already built a custom grid system based on Tailwind&rsquo;s naming scheme.  My implementation is nearly the same as what is shipping in Tailwind CSS 1.2.0.</p>\n\n\n\n<p>Other new features include classes for CSS features such as:</p>\n\n\n\n<ul><li><code>transition</code></li><li><code>transform</code></li><li><code>stroke-width</code></li><li><code>box-sizing</code></li><li><code>clear</code></li></ul>\n\n\n\n<p>Version 1.2.0 adds extra utility classes for rounded corners and shadow sizes.  It also extends its support for setting an element&rsquo;s maximum width.  New utility classes were added for removing a max-width and setting it based on predefined breakpoints.</p>\n\n\n\n<p>The <a href=\"https://rsms.me/inter/\">Inter font</a> now sits at the top of the font stack and will be used if installed on the user&rsquo;s system or if the developer loads it on the site.  Inter is a popular font created specifically for computer screens.  It comes in both fixed and variable options.  The Twenty Twenty theme <a href=\"https://wptavern.com/wordpress-5-3-kirk-released-brings-new-default-theme-editor-improvements-and-ui-tweaks\">released with WordPress 5.3</a> uses the variable version of Inter for several elements within its design.</p>\n\n\n\n<p>For developers who are extending Tailwind CSS, they now have a <a href=\"https://github.com/tailwindcss/tailwindcss/pull/1268\">new plugin API</a> for building custom plugins.  Plugins can also <a href=\"https://github.com/tailwindcss/tailwindcss/pull/1162\">extend the user&rsquo;s configuration file</a>.</p>\n\n\n\n<p>Overall, it looks like it will be a solid update.  I am excited about digging into it and using some of the new utility classes.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 10 Jan 2020 21:11:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:43;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"WPTavern: Gutenberg 7.2 Adds Long-Awaited Multi-Button Block and Gallery Image Size Option\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96362\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:101:\"https://wptavern.com/gutenberg-7-2-adds-long-awaited-multi-button-block-and-gallery-image-size-option\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4723:\"<p>The Gutenberg team <a href=\"https://make.wordpress.org/core/2020/01/09/whats-new-in-gutenberg-8-january/\">released version 7.2</a> of the plugin yesterday after a four-week release hiatus for the holidays.  This update includes at least 180 pull requests to the project&rsquo;s repository by 56 contributors. The largest user-facing features include a new &ldquo;buttons&rdquo; block that allows users to add multiple buttons in a row and the ability to define the size of images in a gallery block.  These were two highly-requested features.</p>\n\n\n\n<p>The update supports changing the font size in the relatively new navigation block.  Users can also add a link for the image in the media &amp; text block.  A few dozen other minor enhancements across multiple components made their way into the update.  Most enhancements continue to clean up the interface and improve usability.</p>\n\n\n\n<p>Many bug fixes are included in version 7.2.  Accessibility improvements include using radio inputs for text alignment, adding an appropriate <code>group</code> role to the block wrapper, adding a label to the social icons block, and more.  Several fixes should improve how pasting content in the editor works, which generally works well already.</p>\n\n\n\n<p>The team continued building upon experimental features, which must be activated via the Gutenberg &gt; Experiments screen in the admin. Outside of a handful of bug fixes and enhancements, the most interesting change is the introduction of a new experimental admin screen.  Gutenberg 7.2 now includes an early beta of a full-site editing page.</p>\n\n\n\n<h2>Adding Buttons in a Row</h2>\n\n\n\n<img />Adding multiple buttons within the Buttons block.\n\n\n\n<p><em>If I had a nickel for every time a user asked how to put two buttons next to each other&hellip;</em>You know how the story goes.</p>\n\n\n\n<p>One of the most-common website layouts today is a large &ldquo;hero&rdquo; section, a heading, some text, and a button, perhaps two.  An end-user could easily build this with a combination of the cover, heading, paragraph, and button blocks if only a single button was needed.  However, that second button was troubling without some custom code work.</p>\n\n\n\n<p>The introduction of the buttons block changes everything.  It is a block that allows end-users to add any number of individual button blocks in a row.  At the moment, the block essentially serves as a wrapper.  The block&rsquo;s only option is the ability to set the alignment of the inner button blocks.</p>\n\n\n\n<h2>Image Size Selector for Galleries</h2>\n\n\n\n<img />Selecting a custom image size for the Gallery block.\n\n\n\n<p>The lack of an option to set the size of gallery images has been one of Gutenberg&rsquo;s largest failures since its inception.  After years of this basic option for the gallery shortcode with the classic editor, the gallery block has always felt incomplete.</p>\n\n\n\n<p>For some users, the lack of basic features that have long existed in the classic editor <a href=\"https://wptavern.com/gutenberg-one-year-later#comment-314188\">is frustrating</a>.  That frustration is understandable, given the fast-paced movement on newer and shinier features.  It is refreshing to see work being done toward addressing long-missing features such as this.</p>\n\n\n\n<p>The gallery block now has a new &ldquo;Images Sizes&rdquo; dropdown select for choosing the size of the images shown.  This option will solve at least a couple of major issues.  By selecting a custom size, the images will utilize less bandwidth for site visitors.  Previously, full-sized images were displayed.  It also allows users to select a consistent size so that galleries with multiple image aspect ratios are better aligned in a grid.  Basically, it can make for prettier galleries.</p>\n\n\n\n<h2>Site Editor Screen Beta</h2>\n\n\n\n<img />Testing the beta Site Editor screen.\n\n\n\n<p>Gutenberg 7.2 introduces a &ldquo;Site Editor&rdquo; screen, which can be enabled by ticking the &ldquo;Enable Full Site Editing&rdquo; checkbox on the Gutenberg &gt; Experiments admin page.  The new screen is an early, bare-bones beta exploration into what will eventually be fully-fledged site editor.</p>\n\n\n\n<p>At this point, the screen does not do much.  End-users can insert blocks and little else.  Content on this screen is not stored for later.  There is not even a save button yet.  Mostly, it serves as another step toward site editing, which could possibly land in core WordPress late in 2020.  However, that is an optimistic schedule, and it is far too early to make a solid guess.  There are a lot of open questions that need answers and technical hurdles to jump.  A 2021 release might be more realistic, depending on the pace of development.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 09 Jan 2020 20:47:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:44;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"WPTavern: BobWP.com Shifts Focus to WooCommerce, Rebrands as ‘Do the Woo’\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96305\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://wptavern.com/bobwp-com-shifts-focus-to-woocommerce-rebrands-as-do-the-woo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4426:\"<img />\n\n\n\n<p>BobWP.com <a href=\"https://bobwp.com/bobwp-is-now-do-the-woo-woocommerce-news-and-community/\">announced yesterday</a> that the site and its podcast would be rebranded to &ldquo;Do the Woo at BobWP .&rdquo; After a decade of more generalized WordPress topics and news, it will now focus specifically on the WooCommerce plugin and its community.  The podcast will also be aired weekly, notching up their previous twice-monthly episodes.</p>\n\n\n\n<p>For Bob Dunn, founder and co-host, this was move was a natural result of where the community he had built was heading.  &ldquo;Over the last 3 years, we have consistently created content around WooCommerce on our site,&rdquo; he said.  &ldquo;I saw that this was what our readers wanted, so built that up and in March of last year, made the decision to focus entirely on WooCommerce.&rdquo;</p>\n\n\n\n<p>Dunn said he has been a fan of WooCommerce since its launch.  &ldquo;It has always been a favorite of mine, and I have used it to sell a lot of stuff. But oddly enough, never physical products.&rdquo;</p>\n\n\n\n<p>Starting in 2020, the podcast will run weekly.  To keep up the brisk pace, the show is bringing on two new co-hosts.  Joining the team is Jonathan Wold, community lead for WooCommerce, and Mendel Kurland, developer advocate a Liquid Web.  Brad Williams, CEO of WebDevStudios, has been a co-host since 2018.</p>\n\n\n\n<p>New episodes of the podcast will air every Thursday.  The show is pre-recorded on Tuesday of the same week, so the content should remain timely.</p>\n\n\n\n<p>Do the Woo will specifically cater to its WooCommerce audience, but it may delve into the larger eCommerce world from time to time.  However, Dunn recommends listening in on the <a href=\"https://wpecommerceshow.com/\">WP eCommerce Show</a> for topics that explore the larger WordPress and eCommerce landscape.</p>\n\n\n\n<p>Dunn does not feel like there will be a shortage of topics to explore every week with WooCommerce-specific content.  &ldquo;At first, yes, it is a bit of a challenge finding topics around it,&rdquo; he said.  &ldquo;But, expanding it to bring in more of what people are doing in the space, no matter how big or small, opens it up more.&rdquo;  He is optimistic about the show&rsquo;s future.  &ldquo;I&rsquo;ll dig as deep as I need to go.  And, with its growth, it may come to the time where there will always be more [content] than I need.&rdquo;</p>\n\n\n\n<p>The podcast&rsquo;s format remains simple.  &ldquo;We basically bring a guest in, learn more about what they are doing and their involvement in the Woo ecosystem,&rdquo; said Dunn.  &ldquo;We wrap it up, typically covering two or three news items. The conversation isn&rsquo;t planned at all.  We just take it where it leads us.&rdquo;</p>\n\n\n\n<p>Dunn originally began the Doo the Woo podcast in 2016 but broadened the scope that same year to WordPress and eCommerce.  &ldquo;I missed it, and at the end of 2017, brought it back as more of an interview-style show, with me and a guest,&rdquo; he said.  &ldquo;For the next few months, I did very few shows and felt I need to change it up to be more conversational.&rdquo;  He brought on Williams as a co-host at that point.  &ldquo;We did a few shows where Brad and I would just chat Woo stuff, and both came to the conclusion it would be fun to bring on a guest, but still keeping it conversational.&rdquo;</p>\n\n\n\n<p>The podcast episodes were sporadic until the middle of 2019, which was the start of the bi-weekly schedule.  Today, with three extra co-hosts, the team can rotate who is hosting a particular episode.</p>\n\n\n\n<p>Dunn said he still catches a few other podcasts but not as many as in the past.  &ldquo;Always been a fan of and still listen to <a href=\"https://mattreport.com/\">Matt Report</a> and <a href=\"https://getoptionspodcast.com/\">Get Options</a>,&rdquo; he said.  &ldquo;I am sure I have listened to just about every WP-centric podcast a few times over the years. Without naming each one, there are several good choices depending on what you are looking for. Podcast listening is a very personal choice and I just recommend people dabble in what is out there and find those that click with you.&rdquo;</p>\n\n\n\n<p>Listen to <a href=\"https://bobwp.com/whats-coming-to-the-do-the-woo-podcast-in-2020/\">episode 33</a> where the team discusses the show&rsquo;s plans for 2020 and beyond:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 08 Jan 2020 21:07:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:45;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"WPTavern: Landing Kit for WordPress Maps Any Post or Page to a Custom Domain\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96301\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"https://wptavern.com/landing-kit-for-wordpress-maps-any-post-or-page-to-a-custom-domain\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7094:\"<img />\n\n\n\n<p>Phil Kurth and Jason Schuller launched a new WordPress product named <a href=\"https://wplandingkit.com/\">Landing Kit</a> today.  The plugin allows end-users to map a domain name to any post, page, or custom post type entry.  It includes other features such as SSL support and URL redirecting.  More features like custom templates and Gutenberg blocks are on the way.</p>\n\n\n\n<p>Kurth is the director and WordPress product developer at <a href=\"https://hookturn.io/\">Hookturn.io</a>, a premium WordPress plugin company, and runs <a href=\"https://www.awesomeacf.com/\">Awesome ACF</a>, a community hub around the Advanced Custom Fields plugin.  Schuller has several ongoing projects.  He runs <a href=\"https://rivyt.com/\">RIVYT</a>, a website for video creators to share their work.  In October, he <a href=\"https://wptavern.com/jason-schuller-launches-dsko-a-discovery-network-for-creators-and-brands\">launched DSKO</a>, which is a discovery network built on WordPress for creators and brands.</p>\n\n\n\n<p><a href=\"https://leeflets.com\">Leeflets</a>, a project Schuller created for building single-page websites, served as the catalyst for the Landing Kit project.  The plugin brings similar functionality to any WordPress install.</p>\n\n\n\n<p>Often, WordPress is overkill for single-page sites.  The platform is ideal for larger sites and applications.  For people who need to manage multiple single-page sites, Landing Kit could be a blessing.  By setting up a single WordPress install with the plugin active, users can map any domain to any post or page.  It also works with custom post types.  This keeps site management limited to a single admin interface and point of maintenance.</p>\n\n\n\n<p>The plugin should not be confused with domain-mapping plugins built for multisite.  While it will work on multisite, the intent is not to map domains to subsites in a network.  Instead, it is meant to specifically map domains to single posts or pages on single-site installations.</p>\n\n\n\n<p>The plugin has two pricing tiers. The lower tier costs $59 per year for support and updates on up to three installations. It will also include access to a single page template in the near future.  The larger pricing tier at $159 per year offers support and updates for unlimited installations and will provide access to all templates as they become available.</p>\n\n\n\n<p>Landing Kit is Schuller&rsquo;s first foray in the WordPress product market space since selling his former WordPress theme business, Press75, in 2014.  His return is already making a splash and seems to be a welcome addition to the ecosystem given the feedback on his <a href=\"https://twitter.com/jasonpatricksc/status/1214574389036900353\">Twitter announcement</a>.</p>\n\n\n\n<p>&ldquo;It was never a goal of mine to jump back in, but sometimes these things just happen naturally,&rdquo; said Schuller.  &ldquo;I&rsquo;ve consistently used WordPress as a platform to iterate on ideas, and with each new build I end up creating unique functionality to solve specific problems. Landing Kit is the result of one of those problems I had the solve while creating Leeflets.&rdquo;</p>\n\n\n\n<p>Kurth was brought in to work on the project because of his experience building WordPress plugins.  He described the first version as not having many technical challenges because they had a working prototype to build from.  &ldquo;The most difficult part was thinking across multiple contexts and maintaining a clear picture of what would be happening across multiple domains at any time,&rdquo; he said.  &ldquo;I expect more difficult challenges as we start to move deeper into feature territory as we&rsquo;ll have bigger decisions to make and new technical hurdles to face, particularly when we start exploring remote block/template libraries.&rdquo;</p>\n\n\n\n<h2>Plugin Features</h2>\n\n\n\n<img />Potential book template for Landing Kit.\n\n\n\n<p>Version 1.0 of the plugin keeps things simple, which is a signature of Schuller&rsquo;s past work.  The plugin has a domain management screen.  It provides a convenient location to edit and configure all mapped domains for the installation.  Domain mapping is also available through the post-editing screen.</p>\n\n\n\n<p>The SSL options allow users to serve individual domains over HTTPS or to do so on a global basis.  The plugin also makes it easy to decide whether a post or page should be available via the main website or if requests to the single view should be 301 redirected to the mapped domain.</p>\n\n\n\n<p>There are some technical requirements to make use of the plugin.  Users must be on a host with the ability to add alias or add-on domains, have a dedicated IP address for their website, and be running WordPress 5.0 or above.  End-users should also be familiar with managing DNS records, specifically A-Records, with their web host.  These requirements are necessary to make sure domains are pointing to the correct location.  These are common features and available through many hosts.  Each host should have specific instructions for working with these features.</p>\n\n\n\n<p>The big value-add will be the plugin&rsquo;s custom templates and its upcoming Gutenberg blocks.  These will allow users to quickly build out single-page sites that look and feel different from the active theme for their WordPress installation.</p>\n\n\n\n<p>&ldquo;In line with the idea of complete niche templates (essentially bundled blocks), it makes sense to break that concept down a level in form of niche specific blocks you could pick and choose to create your own landing pages with a bit more freedom,&rdquo; said Schuller. &ldquo;There&rsquo;s so much potential with Gutenberg to get creative, especially when you&rsquo;re thinking specifically about landing pages and what creators might need to achieve a specific goal.&rdquo;</p>\n\n\n\n<p>Kurth and Schuller plan to release templates aimed at specific product niches.  &ldquo;I&rsquo;m hoping to get the first template out the door within the next few weeks,&rdquo; said Schuller on <a href=\"https://twitter.com/jasonpatricksc/status/1214576733669617664\">Twitter</a>.  The concept could be interesting as templates could essentially serve as &ldquo;mini themes.&rdquo;  If the plugin gains enough traction and a large user base, there is potential for a larger marketplace to form around single-page template designs.</p>\n\n\n\n<p>Take a video tour of the plugin:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<p>Schuller said that they are kicking around some other feature ideas for the future.  Nothing is set in stone yet.  &ldquo;People have also expressed interest in a Leeflets-style front-end experience for managing pages, which would essentially make Landing Kit a SaaS in a box,&rdquo; he said.  &ldquo;I&rsquo;m not sure if that&rsquo;s something we&rsquo;ll explore in the near term, but an option at the very least.&rdquo;</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p class=\"has-background has-gray-100-background-color bg-gray-100\"><strong>Update &ndash; January 8, 2020:</strong>  Additional quotes from Landing Kit creators added.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 08 Jan 2020 03:34:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:46;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"WPTavern: Lessons Learned by Stepping Outside WordPress Comfort Zone\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96264\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://wptavern.com/lessons-learned-by-stepping-outside-wordpress-comfort-zone\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6861:\"<p>It was late summer in 2018. I was an aging developer who wasn&rsquo;t quite sure where I fit into the WordPress world anymore.  I had spent over a decade learning the ins and outs of the platform that launched my career and also served as a hobby for other pet projects I wanted to tackle.</p>\n\n\n\n<p>In part, I was bored.  I needed a new challenge.</p>\n\n\n\n<p>I love WordPress. More than that, I appreciate what WordPress has allowed me to accomplish over the years. However, I was no longer happy with it for my personal blog.  It was suitable for the job, but I often found it had a lot more gadgets and gizmos than I needed. I had also been writing blog posts in Markdown for many years rather than the classic editor.  WordPress was simply no longer a part of my workflow for my blog.  At times, it was a hindrance.</p>\n\n\n\n<p><em>Challenge accepted.</em></p>\n\n\n\n<p>Over a weekend, I built a working custom blog system.  I am hesitant to call it a Content Manage System (CMS) because it lacked crucial features, such as an administrative interface, that are at the heart of any CMS.  Nevertheless, I built a working system from scratch in two days.</p>\n\n\n\n<p>I had no idea I could accomplish such a feat without relying on the useful functions and tools that WordPress had so generously provided for most of my programming career.  I cannot count the number of times I accidentally typed out <code>esc_attr()</code> or <code>esc_html()</code> only to remember those were WordPress functions.  <em>My WordPress muscle memory was strong.</em>  Without knowing it, everything I had learned through building on top of WordPress pushed me to become a more well-rounded PHP developer.  There are few APIs I had not worked with from core WordPress.  I understood much of the source code and knew the reasons for a lot of the legacy gunk.</p>\n\n\n\n<p>My personal project paled in comparison to WordPress&rsquo; power and still does to this day.  However, it moved me outside my comfort zone.  It allowed me to explore old ideas in new ways.</p>\n\n\n\n<p>One example was understanding how rewrite rules and routing worked.  Some of my friends and I recently joked that no one really understands the WordPress Rewrite API.  You just tinker with it until something works and the new code no longer breaks your site.  There are many existing libraries out there, but I wanted to understand how this worked for my own edification.  Therefore, I set out to build an HTTP request, router, and controller class.  The end result was an elegant solution, which borrowed heavily from other PHP frameworks.</p>\n\n\n\n<p>With a simple line of code, as shown below for setting up a &ldquo;book&rdquo; content type, I could handle incoming requests for a book page, map it to the correct resource, and output the template on the front end. I began to wonder why I had shied away from this foundational website concept for so many years as a developer.</p>\n\n\n\n<pre class=\"wp-block-code\"><code>// Create \'example.com/books/book-name\'.\n$this-&gt;router-&gt;get( \'books/{name}\', Controller::class );</code></pre>\n\n\n\n<p>There were many other areas where I began to question the &ldquo;WordPress way&rdquo; of doing things.  During this journey of discovery, I was able to learn things that I could bring back for use in my WordPress projects.  By stepping out into the larger world of website development, I was able to better see the flaws in the platform that helped me fall in love with programming.  However, I was also better able to see the beauty in the system that thousands of developers have kept running for the preceding 15 years.</p>\n\n\n\n<h2>It Is Not All About Code</h2>\n\n\n\n<p>I had the opportunity to study and learn large frameworks like <a href=\"https://laravel.com/\">Laravel</a> and <a href=\"https://symfony.com/\">Symfony</a>.  However, I also studied how other platforms worked from a pure user-experience perspective.</p>\n\n\n\n<p>The one thing I knew for certain is that I wanted to test platforms created for people who wrote in Markdown.  I wasn&rsquo;t looking for huge platforms to compete with WordPress&rsquo; power, such as Joomla or Drupal.  Instead, I was looking at lighter-weight solutions like <a href=\"https://getgrav.org/\">Grav</a>, <a href=\"https://jekyllrb.com/\">Jekyll</a>, and <a href=\"https://gohugo.io/\">Hugo</a>.  I wanted to understand how the user experience fit in with my workflow.</p>\n\n\n\n<p>Of all the solutions I tested, each had its advantages.  Each also had features or methods of doing things that wasn&rsquo;t to my taste.  The good thing about the experience was that I was able to identify how I wanted my blogging platform to work for me.  Reading thoughts from others in those communities also allowed me to hear from users outside of the WordPress community about why they loved their preferred blogging system.</p>\n\n\n\n<p>I soldiered forward.  Using what I learned from those platforms, I built something that I was happy to use.  It wasn&rsquo;t perfect and would likely never be.  Room for growth is not a bad thing.</p>\n\n\n\n<p>During this time, I rekindled my love of blogging with WordPress.  While not always the popular opinion, the block editor felt leaps and bounds better than the classic editor.  It was something I could see myself using regularly.  Aside from my personal blog, I began using it on other projects.  I still write in Markdown every day.  However, I find myself enjoying writing within WordPress&rsquo; editor for the first time in years.</p>\n\n\n\n<h2>Why You Should Try New Platforms</h2>\n\n\n\n<p>From a developer perspective, it is not a good idea to become complacent and rely on a single system.  Instead of calling yourself a &ldquo;WordPress developer,&rdquo; think beyond that terminology.  Instead, you should be a PHP programmer or JavaScript programmer.  Or, better yet, simply call yourself a programmer.  Programmers solve problems.  The tools or languages are what you use to get from Point A to Point B.</p>\n\n\n\n<p>On the job market, being a more well-rounded programmer opens up more opportunities.  While most of us can only hope that WordPress will be the leading platform for the next 10, 20, or 50 years, you should be prepared for any future.</p>\n\n\n\n<p>Another benefit of working with other platforms from time to time is that you learn ideas that you can bring back into the WordPress ecosystem.  For example, it is interesting to see how the <a href=\"https://roots.io/sage/\">Sage starter theme</a> implements Laravel Blade&rsquo;s templating engine.  These ideas can help shape WordPress&rsquo; future.</p>\n\n\n\n<p>Some ideas can be pushed into core WordPress.  Others can improve team workflows within agencies.</p>\n\n\n\n<p>Continuing education benefits the WordPress community as a whole.  Don&rsquo;t limit that education to WordPress-specific ideas.  Learn from the outside and bring it back.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 06 Jan 2020 21:19:23 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:47;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:45:\"BuddyPress: BuddyPress 5.1.2 Security Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=309637\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://buddypress.org/2020/01/buddypress-5-1-2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1190:\"<p><a href=\"https://downloads.wordpress.org/plugin/buddypress.5.1.2.zip\">BuddyPress 5.1.2</a> is now available. This is a security release. All BuddyPress installations are strongly encouraged to upgrade as soon as possible.</p>\n\n\n\n<p>The 5.1.2 release addresses one security issue:</p>\n\n\n\n<ul><li>Certain REST API requests could result in the exposure of private data. Discovered and reported independently by <a href=\"https://profiles.wordpress.org/walbo/\">Petter Walbø Johnsgård</a> and <a href=\"https://profiles.wordpress.org/finebet/\">Jacek Suski</a>.</li></ul>\n\n\n\n<p>The vulnerability was reported privately to the BuddyPress team, in accordance with&nbsp;<a href=\"https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/\">WordPress’s security policies</a>. Our thanks to the reporters for practicing coordinated disclosure.</p>\n\n\n\n<p>For complete details, visit the&nbsp;<a href=\"https://codex.buddypress.org/releases/version-5-1-2/\">5.1.2 changelog</a>.</p>\n\n\n\n<p>Update to BuddyPress 5.1.2 today in your WordPress Dashboard, or by&nbsp;<a href=\"https://wordpress.org/plugins/buddypress/\">downloading from the WordPress.org plugin repository</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 03 Jan 2020 21:36:11 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Boone Gorges\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:48;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"WPTavern: Pods Framework Loses Primary Sponsorship, Seeks Donors To Fund Project\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96194\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"https://wptavern.com/pods-framework-loses-primary-sponsorship-seeks-donors-to-fund-project\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8184:\"<img />\n\n\n\n<p>Scott Kingsley Clark, lead developer of the Pods Framework, <a href=\"https://pods.io/2020/01/02/pods-needs-your-help-in-2020/\">announced the project was seeking new donors</a> on Thursday.  Automattic, the primary sponsor, dropped out after funding the project since 2012.  This has put the team in a position to seek help for maintaining and supporting the project.  Automattic was previously covering around 90% of the costs.</p>\n\n\n\n<p>The <a href=\"https://wordpress.org/plugins/pods/\">Pods Framework</a> is a WordPress plugin that allows end-users or developers to create and extend custom post types, content types, users, media, and comments.  Essentially, it is a complete content management framework for those who need more than the basics that WordPress offers.  It has well over a dozen <a href=\"https://pods.io/plugins/\">add-on plugins</a> for extra functionality and currently has over 80,000 active installations.</p>\n\n\n\n<p>There are <a href=\"https://friends.pods.io/about-the-team/\">six primary contributors</a> to the Pods plugin.  They have also brought on a React developer who is just getting started with UI work on Pods 2.8.  Other than work from the team, the project receives patches and contributions from the larger Pods community.</p>\n\n\n\n<p>With the loss of funding from Automattic, Pods is receiving around $700 each month from donors. &ldquo;Once we found out that Automattic was going to focus their sponsorship funding towards other priorities of theirs, we put together a plan of action to reduce overall costs,&rdquo; said Clark.</p>\n\n\n\n<p>The team&rsquo;s goal is to have at least 200 sponsors.  The average recurring monthly donation is about $17.  Coupled with their current 40 regular donors, they need an additional 160 at the same donation average to cover costs.  This would at least allow the team to be efficient with their time.</p>\n\n\n\n<p>&ldquo;Right now our feature/fix development and support efforts will begin to suffer from lack of funding because we&rsquo;ll be spread too thin,&rdquo; said Clark.  &ldquo;I work a full-time job and can&rsquo;t pick up the extra weight entirely on my own.&rdquo;  Clark&rsquo;s job with Modern Tribe gives him some flexibility to work on the project, but it is minimal and only when time is available.</p>\n\n\n\n<p>People who are willing to sponsor the project monthly can contribute via the <a href=\"https://friends.pods.io/donations/become-a-friend/\">Friends of Pods</a> sponsorship page.  The project also has a <a href=\"https://friends.pods.io/donations/one-time-donation/\">one-time donation option</a> for those wanting to go that route.</p>\n\n\n\n<h2>Automattic Was Crucial to Success</h2>\n\n\n\n<p>In his announcement, Clark said Automattic&rsquo;s decision to pull their sponsorship was because the company wanted to put their funds toward native Gutenberg projects.  Pods is a project that spans beyond Gutenberg.  However, it does have some Gutenberg integration and more features in the works.</p>\n\n\n\n<p>Since 2012, Automattic has been the largest sponsor of Pods.  Their funding allowed the team to support and continue developing the plugin.  &ldquo;We&rsquo;re so appreciative of Automattic&rsquo;s support,&rdquo; said <a href=\"https://twitter.com/podsframework/status/1212792297911443456\">Clark on Twitter</a>.  &ldquo;They&rsquo;ve sponsored Pods for over 7 years, I know their decision was a tough one for them.&rdquo;</p>\n\n\n\n<p>In 2011, <a href=\"https://wptavern.com/pods-what-happened-after-the-kickstarter-campaign\">Pods surpassed its goal</a> in a Kickstarter campaign.  The project raised over $4,000 with a goal of $1,500.  The campaign was intended to fund the development of Pods 2.0.  In hindsight, the dollar amount was far too low to realistically fund such a complex project.</p>\n\n\n\n<p>&ldquo;I naively thought that would be enough to accomplish everything and more we wanted to do for our big Pods 2.0 release,&rdquo; said Clark.  &ldquo;I was really wrong. Adding developers at a late stage in a project can take even more time than you anticipate. I also had to work around those developers&rsquo; schedules and spend time coordinating with them instead of building things myself. It was a huge challenge as I hadn&rsquo;t really led a team on a side project while having a full-time job before.&rdquo;</p>\n\n\n\n<p>Clark had to reach into his pocket and put money towards the funding problem.  Yet, the team hit more roadblocks getting Pods 2.0 released.  &ldquo;That&rsquo;s when I reached out to Automattic, which they offered to help out here and there to sponsor some more development&rdquo;, he said. &ldquo;I was at the right job and had the right developers in place to really make the most of that arrangement. I had tons of time on the clock at work to build projects with Pods and I could build features/fix problems every day. With the added help of the funding, we were covered for many years to come.&rdquo;</p>\n\n\n\n<p>The arrangement was a blessing for the project, propelling it forward for years.  &ldquo;Without Automattic, we surely couldn&rsquo;t have continued on with the huge undertaking that the Pods 2.0 rewrite was,&rdquo; said Clark.  &ldquo;We would have just shelved everything and only added minor fixes/enhancements to Pods going forward.&rdquo;</p>\n\n\n\n<p>Clark described the funding as crucial to maintaining a premium product for free.  &ldquo;Given what I know about many other free products out there, I can see why our support for Pods itself has sometimes been compared to premium support because of the people we could keep involved helping everyone with their project challenges and Pods questions,&rdquo; he said.</p>\n\n\n\n<p>After success with Pods 2.0 and several releases, the Pods team reached back out to Automattic.  They were able to secure more funding with the agreement that they would diversify their funding and bring in more sponsors, which they were able to accomplish.</p>\n\n\n\n<h2>What the Future Holds</h2>\n\n\n\n<p>Clark is hopeful that they can meet their sponsorship goals.  If not, they may have to explore some commercial options.  However, he said Pods and its primary features will remain free of charge.</p>\n\n\n\n<p>&ldquo;Development is not cheap,&rdquo; said Clark.  &ldquo;In fact, we&rsquo;ve thought about diversifying our funding for a while, but ironically our sponsorship agreement with Automattic prohibited us from exploring premium add-ons to help fund more growth.&rdquo;</p>\n\n\n\n<p>While the funding was a blessing, it may have also been a crutch.  &ldquo;If we had suddenly gotten millions of active installs to support, we would have been in big trouble,&rdquo; he said.  &ldquo;You can&rsquo;t scale sponsorships with a growing userbase.&rdquo;</p>\n\n\n\n<p>Clark said he is committed to making sure the next three major feature releases go out for free as part of the main Pods plugin, regardless of the funding situation.  &ldquo;I believe in making it easy to build projects in WordPress and some of those features are just really crucial to normal projects,&rdquo; he said.</p>\n\n\n\n<p>The team is exploring the potential for premium add-ons.  However, if going that route, the add-ons would be with useful features that go beyond the core needs of the plugin.  &ldquo;We have some really awesome features that we&rsquo;ve always wanted to do and this could be the avenue to build them while giving huge value to our Friends of Pods,&rdquo; he said.  &ldquo;This could be an added benefit to them for supporting our project, which they&rsquo;d get as a reward for keeping their Friends of Pods membership active.&rdquo;</p>\n\n\n\n<p>The future is uncertain.  The project is not in danger of disappearing at this point.  However, the reality is that development and support have real-world costs that need to be met.</p>\n\n\n\n<p>&ldquo;It&rsquo;s still too early to know exactly what we can do with the funding we have and what we can expect to get from our 2020 fundraising efforts,&rdquo; said Clark.  &ldquo;We don&rsquo;t know if those ongoing funding struggles will prevent us from spending time to build new add-ons to generate new revenue either. It&rsquo;s all up in the air right now.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 03 Jan 2020 17:59:56 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:49;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"WordPress.org blog: The Month in WordPress: December 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8282\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2020/01/the-month-in-wordpress-december-2019/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8184:\"<p>As 2019 draws to a close and we look ahead to another exciting year let’s take a moment to review what the WordPress community achieved in December.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>WordPress 5.3.1 and 5.3.2 Releases</h2>\n\n\n\n<p>The WordPress 5.3.1 security and maintenance release was announced on December 13. It features 46 fixes and enhancements. This version corrects four security issues in WordPress versions 5.3 and earlier. Shortly afterwards, WordPress 5.3.2 was released, addressing a couple high severity Trac tickets, and includes 5 fixes and enhancements, so you’ll want to upgrade. You can read more about these releases in the announcements for <a href=\"https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/\">5.3.1</a> and <a href=\"https://wordpress.org/news/2019/12/wordpress-5-3-2-maintenance-release/\">5.3.2</a>.</p>\n\n\n\n<h2>Update on the Nine Core Projects for 2019</h2>\n\n\n\n<p>At the end of 2018, <a href=\"https://profiles.wordpress.org/matt/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>matt</a> <a href=\"https://make.wordpress.org/core/2018/12/08/9-priorities-for-2019/\">announced</a> the nine projects that would be the main focus areas for Core development in the next year. Have we made progress? Yes! <a href=\"https://profiles.wordpress.org/chanthaboune/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>chanthaboune</a> <a href=\"https://make.wordpress.org/core/2019/12/06/update-9-projects-for-2019/\">posted a full update</a> on the team’s work. In brief, two of the projects have been completed and shipped in major releases, four are targeted for release in versions 5.4 and 5.5 of WordPress, and the remaining three have seen significant progress but are not yet slated for completion. These will continue to see progress throughout 2020.</p>\n\n\n\n<p>Want to get involved in building WordPress Core? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a> and join the #core channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>WordPress Major Release Calendar</h2>\n\n\n\n<p>The Core team has published <a href=\"https://make.wordpress.org/core/2019/11/21/tentative-release-calendar-2020-2021/\">a tentative release calendar</a> for 2020 and 2021. This is intended to provide the community with more information about what lies ahead.</p>\n\n\n\n<p>The schedule is considered tentative because there are always variables that could affect these plans — not least that the Core team may need more time to finish the work planned for a release.</p>\n\n\n\n<h2>Initial Documentation for Block-Based WordPress Themes</h2>\n\n\n\n<p>The Gutenberg team has started working on <a href=\"https://github.com/WordPress/gutenberg/pull/18890/files\">the initial documentation</a> for what block-based themes might look like, marking a significant change in the way themes are conceptualized. With full-site editing now a realistic goal for WordPress, themes will certainly look different in the future.</p>\n\n\n\n<p>Want to help shape the future of block-based themes in WordPress Core? Following <a href=\"https://make.wordpress.org/core/\">the Core team blog</a> is a good start! You can also join in on the discussion <a href=\"https://make.wordpress.org/themes/2019/12/04/questions-about-the-future-of-themes/\">on this blog post</a>, or help out with the work to <a href=\"https://github.com/WordPress/gutenberg/blob/master/lib/demo-block-templates/index.html\">create a demo space for experimentation with the future of themes</a>. As always, contribution to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a> is open to everyone! Join the #core-editor channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a> to see what other people are saying, and contribute your own thoughts.</p>\n\n\n\n<h2>Gutenberg Updates Abound</h2>\n\n\n\n<p>It’s been a busy month for Gutenberg! Version 7.0, including a new navigation block, <a href=\"https://make.wordpress.org/core/2019/11/27/whats-new-in-gutenberg-27-november/\">was announced</a> on November 27. This was followed by <a href=\"https://make.wordpress.org/core/2019/12/11/whats-new-in-gutenberg-11-december/\">version 7.1</a>, announced on December 11; it includes 161 merged pull requests that offer a fresh UI to new users, an option to switch between edit and navigation modes, captions for the table block, and many other enhancements.</p>\n\n\n\n<p>Want to get involved in building Gutenberg? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a>, contribute to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a>, and join the #core-editor channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>Arrival of the BuddyPress Beta Tester Plugin</h2>\n\n\n\n<p>On December 2, <a href=\"https://buddypress.org/2019/12/bp-beta-tester-1-0-0/\">the BuddyPress Beta Tester plugin</a> was added to the WordPress.org plugins directory. This feature is a great way for the WordPress community to provide early feedback on releases.</p>\n\n\n\n<p>You can <a href=\"https://wordpress.org/plugins/bp-beta-tester/\">download the plugin</a> now. If you find that something is not working as expected during your beta tests, let the BuddyPress team know by submitting a ticket on the <a href=\"https://buddypress.trac.wordpress.org/newticket\">Development Tracker</a> or posting a new topic in the BuddyPress <a href=\"https://buddypress.org/support/\">support forums</a>.​​</p>\n\n\n\n<h2>An Update on the Block Directory in the WordPress Editor&nbsp;</h2>\n\n\n\n<p>The Design team received lots of excellent feedback on the <a href=\"https://make.wordpress.org/design/2019/07/11/block-directory-in-wp-admin-concepts/\">early concepts for the Block Directory</a>. This feedback was incorporated into a Version 1 update to the <a href=\"https://make.wordpress.org/design/tag/block-directory/\">#block-directory</a> project. The Block Directory is to be included in WordPress 5.5, which is slated for August 2020. To learn more about the Block Directory, check out <a href=\"https://make.wordpress.org/design/2019/12/19/block-directory-in-wp-admin-v1/\">this announcement post</a> and help out by sharing your feedback. </p>\n\n\n\n<p>Want to get involved in building the Block Directory? Follow <a href=\"https://make.wordpress.org/design/\">the Design team blog</a>. If you have a block you’d like to include in the directory you can <a href=\"https://make.wordpress.org/meta/2019/12/06/block-directory-plugin-guidelines/\">submit it following the information here</a>. </p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading:</h2>\n\n\n\n<ul><li><a href=\"https://make.wordpress.org/meta/2019/12/06/block-directory-plugin-guidelines/\">Guidelines for the Block Directory</a> have been drafted; the team is actively working on them now.</li><li>The<a href=\"https://make.wordpress.org/community/2020-wordpress-global-community-sponsorship-program/\"> Global Community Sponsorship Program for 2020</a> has been announced.&nbsp;</li><li>The Theme Review Team <a href=\"https://make.wordpress.org/themes/2019/12/09/do-not-contact-reviewers-outside-of-the-wordpress-org-system-about-your-review/\">has published a reminder</a> for developers about the proper way to communicate with reviewers.</li><li>The Community Team is in the process of <a href=\"https://make.wordpress.org/community/2019/12/05/community-team-reps-for-2020/\">selecting new team reps</a>.</li><li><a href=\"https://meetup.com/pro/wordpress\">The WordPress meetup program</a> crossed the 800-group mark this month and includes groups from more than 100 countries.</li><li>The team that helped to create the 2019 State of the Word slide deck <a href=\"https://wordpress.org/news/2019/12/state-of-the-word-the-story-of-the-slides/\">shared how the slides were created using Gutenberg</a>, powered by the Slides plugin.&nbsp;</li></ul>\n\n\n\n<p><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it here</em></a><em>.</em></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 03 Jan 2020 17:05:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Angela Jin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Fri, 21 Feb 2020 20:33:45 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Fri, 21 Feb 2020 20:15:08 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 1\";s:16:\"content-encoding\";s:4:\"gzip\";}}s:5:\"build\";s:14:\"20130911133210\";}','no'),(158,'_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1582360425','no'),(159,'_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1582317225','no'),(160,'_transient_timeout_dash_v2_c05853b002c443ec8e57ff884f56cdde','1582360425','no'),(161,'_transient_dash_v2_c05853b002c443ec8e57ff884f56cdde','<div class=\"rss-widget\"><ul><li><a class=\'rsswidget\' href=\'https://es.wordpress.org/2020/02/19/wordpress-5-4-beta-2/\'>WordPress 5.4 Beta 2</a></li></ul></div><div class=\"rss-widget\"><ul><li><a class=\'rsswidget\' href=\'https://wptavern.com/goodbye-featured-themes-for-now?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=goodbye-featured-themes-for-now\'>WPTavern: Goodbye Featured Themes, For Now</a></li><li><a class=\'rsswidget\' href=\'https://ma.tt/2020/02/livestream-tomorrow/\'>Matt: Livestream Tomorrow</a></li><li><a class=\'rsswidget\' href=\'https://wordpress.org/news/2020/02/pop-up-livestream-on-february-22/\'>WordPress.org blog: Pop-Up Livestream on February 22</a></li></ul></div>','no'),(162,'can_compress_scripts','1','no'),(166,'category_children','a:0:{}','yes'),(170,'_transient_timeout_jetpack_idc_allowed','1582368418','no'),(171,'_transient_jetpack_idc_allowed','1','no'),(172,'_transient_doing_cron','1582364818.3823940753936767578125','yes'),(177,'boldgrid_backup_in_progress_data','a:3:{s:6:\"status\";s:22:\"Backing up database...\";s:6:\"tables\";a:13:{i:0;s:18:\"wpedpy_commentmeta\";i:1;s:15:\"wpedpy_comments\";i:2;s:12:\"wpedpy_links\";i:3;s:14:\"wpedpy_options\";i:4;s:15:\"wpedpy_postmeta\";i:5;s:12:\"wpedpy_posts\";i:6;s:25:\"wpedpy_term_relationships\";i:7;s:20:\"wpedpy_term_taxonomy\";i:8;s:15:\"wpedpy_termmeta\";i:9;s:12:\"wpedpy_terms\";i:10;s:15:\"wpedpy_usermeta\";i:11;s:12:\"wpedpy_users\";i:12;s:19:\"wpedpy_wpforms_lite\";}s:4:\"step\";i:1;}','yes');

-- Dumped table `wpedpy_options` with 156 row(s)
--

--
-- Table structure for table `wpedpy_postmeta`
--

CREATE TABLE `wpedpy_postmeta` (
  `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `post_id` bigint(20) unsigned NOT NULL DEFAULT 0,
  `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `meta_value` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  PRIMARY KEY (`meta_id`),
  KEY `post_id` (`post_id`),
  KEY `meta_key` (`meta_key`(191))
) ENGINE=MyISAM AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

--
-- Dumping data for table `wpedpy_postmeta`
--

INSERT INTO `wpedpy_postmeta` VALUES (1,2,'_wp_page_template','default'),(2,3,'_wp_page_template','default');

-- Dumped table `wpedpy_postmeta` with 2 row(s)
--

--
-- Table structure for table `wpedpy_posts`
--

CREATE TABLE `wpedpy_posts` (
  `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `post_author` bigint(20) unsigned NOT NULL DEFAULT 0,
  `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `post_content` longtext COLLATE utf8mb4_unicode_ci NOT NULL,
  `post_title` text COLLATE utf8mb4_unicode_ci NOT NULL,
  `post_excerpt` text COLLATE utf8mb4_unicode_ci NOT NULL,
  `post_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'publish',
  `comment_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'open',
  `ping_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'open',
  `post_password` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `post_name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `to_ping` text COLLATE utf8mb4_unicode_ci NOT NULL,
  `pinged` text COLLATE utf8mb4_unicode_ci NOT NULL,
  `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `post_content_filtered` longtext COLLATE utf8mb4_unicode_ci NOT NULL,
  `post_parent` bigint(20) unsigned NOT NULL DEFAULT 0,
  `guid` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `menu_order` int(11) NOT NULL DEFAULT 0,
  `post_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'post',
  `post_mime_type` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `comment_count` bigint(20) NOT NULL DEFAULT 0,
  PRIMARY KEY (`ID`),
  KEY `post_name` (`post_name`(191)),
  KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`),
  KEY `post_parent` (`post_parent`),
  KEY `post_author` (`post_author`)
) ENGINE=MyISAM AUTO_INCREMENT=5 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

--
-- Dumping data for table `wpedpy_posts`
--

INSERT INTO `wpedpy_posts` VALUES (1,1,'2020-02-21 20:31:47','2020-02-21 20:31:47','<!-- wp:paragraph -->\n<p>Welcome to WordPress. This is your first post. Edit or delete it, then start writing!</p>\n<!-- /wp:paragraph -->','Hello world!','','publish','open','open','','hello-world','','','2020-02-21 20:31:47','2020-02-21 20:31:47','',0,'https://acquainvestments.co/?p=1',0,'post','',1),(2,1,'2020-02-21 20:31:47','2020-02-21 20:31:47','<!-- wp:paragraph -->\n<p>This is an example page. It\'s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:</p>\n<!-- /wp:paragraph -->\n\n<!-- wp:quote -->\n<blockquote class=\"wp-block-quote\"><p>Hi there! I\'m a bike messenger by day, aspiring actor by night, and this is my website. I live in Los Angeles, have a great dog named Jack, and I like pi&#241;a coladas. (And gettin\' caught in the rain.)</p></blockquote>\n<!-- /wp:quote -->\n\n<!-- wp:paragraph -->\n<p>...or something like this:</p>\n<!-- /wp:paragraph -->\n\n<!-- wp:quote -->\n<blockquote class=\"wp-block-quote\"><p>The XYZ Doohickey Company was founded in 1971, and has been providing quality doohickeys to the public ever since. Located in Gotham City, XYZ employs over 2,000 people and does all kinds of awesome things for the Gotham community.</p></blockquote>\n<!-- /wp:quote -->\n\n<!-- wp:paragraph -->\n<p>As a new WordPress user, you should go to <a href=\"https://acquainvestments.co/wp-admin/\">your dashboard</a> to delete this page and create new pages for your content. Have fun!</p>\n<!-- /wp:paragraph -->','Sample Page','','publish','closed','open','','sample-page','','','2020-02-21 20:31:47','2020-02-21 20:31:47','',0,'https://acquainvestments.co/?page_id=2',0,'page','',0),(3,1,'2020-02-21 20:31:47','2020-02-21 20:31:47','<!-- wp:heading --><h2>Who we are</h2><!-- /wp:heading --><!-- wp:paragraph --><p>Our website address is: https://acquainvestments.co.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>What personal data we collect and why we collect it</h2><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>Comments</h3><!-- /wp:heading --><!-- wp:paragraph --><p>When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor&#8217;s IP address and browser user agent string to help spam detection.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.</p><!-- /wp:paragraph --><!-- wp:heading {\"level\":3} --><h3>Media</h3><!-- /wp:heading --><!-- wp:paragraph --><p>If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.</p><!-- /wp:paragraph --><!-- wp:heading {\"level\":3} --><h3>Contact forms</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>Cookies</h3><!-- /wp:heading --><!-- wp:paragraph --><p>If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select &quot;Remember Me&quot;, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.</p><!-- /wp:paragraph --><!-- wp:heading {\"level\":3} --><h3>Embedded content from other websites</h3><!-- /wp:heading --><!-- wp:paragraph --><p>Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.</p><!-- /wp:paragraph --><!-- wp:heading {\"level\":3} --><h3>Analytics</h3><!-- /wp:heading --><!-- wp:heading --><h2>Who we share your data with</h2><!-- /wp:heading --><!-- wp:heading --><h2>How long we retain your data</h2><!-- /wp:heading --><!-- wp:paragraph --><p>If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>What rights you have over your data</h2><!-- /wp:heading --><!-- wp:paragraph --><p>If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>Where we send your data</h2><!-- /wp:heading --><!-- wp:paragraph --><p>Visitor comments may be checked through an automated spam detection service.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>Your contact information</h2><!-- /wp:heading --><!-- wp:heading --><h2>Additional information</h2><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>How we protect your data</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>What data breach procedures we have in place</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>What third parties we receive data from</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>What automated decision making and/or profiling we do with user data</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>Industry regulatory disclosure requirements</h3><!-- /wp:heading -->','Privacy Policy','','draft','closed','open','','privacy-policy','','','2020-02-21 20:31:47','2020-02-21 20:31:47','',0,'https://acquainvestments.co/?page_id=3',0,'page','',0),(4,1,'2020-02-21 20:33:37','0000-00-00 00:00:00','','Borrador automático','','auto-draft','open','open','','','','','2020-02-21 20:33:37','0000-00-00 00:00:00','',0,'https://acquainvestments.co/?p=4',0,'post','',0);

-- Dumped table `wpedpy_posts` with 4 row(s)
--

--
-- Table structure for table `wpedpy_term_relationships`
--

CREATE TABLE `wpedpy_term_relationships` (
  `object_id` bigint(20) unsigned NOT NULL DEFAULT 0,
  `term_taxonomy_id` bigint(20) unsigned NOT NULL DEFAULT 0,
  `term_order` int(11) NOT NULL DEFAULT 0,
  PRIMARY KEY (`object_id`,`term_taxonomy_id`),
  KEY `term_taxonomy_id` (`term_taxonomy_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

--
-- Dumping data for table `wpedpy_term_relationships`
--

INSERT INTO `wpedpy_term_relationships` VALUES (1,1,0);

-- Dumped table `wpedpy_term_relationships` with 1 row(s)
--

--
-- Table structure for table `wpedpy_term_taxonomy`
--

CREATE TABLE `wpedpy_term_taxonomy` (
  `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `term_id` bigint(20) unsigned NOT NULL DEFAULT 0,
  `taxonomy` varchar(32) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `description` longtext COLLATE utf8mb4_unicode_ci NOT NULL,
  `parent` bigint(20) unsigned NOT NULL DEFAULT 0,
  `count` bigint(20) NOT NULL DEFAULT 0,
  PRIMARY KEY (`term_taxonomy_id`),
  UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`),
  KEY `taxonomy` (`taxonomy`)
) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

--
-- Dumping data for table `wpedpy_term_taxonomy`
--

INSERT INTO `wpedpy_term_taxonomy` VALUES (1,1,'category','',0,1);

-- Dumped table `wpedpy_term_taxonomy` with 1 row(s)
--

--
-- Table structure for table `wpedpy_termmeta`
--

CREATE TABLE `wpedpy_termmeta` (
  `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `term_id` bigint(20) unsigned NOT NULL DEFAULT 0,
  `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `meta_value` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  PRIMARY KEY (`meta_id`),
  KEY `term_id` (`term_id`),
  KEY `meta_key` (`meta_key`(191))
) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

--
-- Dumping data for table `wpedpy_termmeta`
--


-- Dumped table `wpedpy_termmeta` with 0 row(s)
--

--
-- Table structure for table `wpedpy_terms`
--

CREATE TABLE `wpedpy_terms` (
  `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `slug` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `term_group` bigint(10) NOT NULL DEFAULT 0,
  PRIMARY KEY (`term_id`),
  KEY `slug` (`slug`(191)),
  KEY `name` (`name`(191))
) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

--
-- Dumping data for table `wpedpy_terms`
--

INSERT INTO `wpedpy_terms` VALUES (1,'Uncategorized','uncategorized',0);

-- Dumped table `wpedpy_terms` with 1 row(s)
--

--
-- Table structure for table `wpedpy_usermeta`
--

CREATE TABLE `wpedpy_usermeta` (
  `umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `user_id` bigint(20) unsigned NOT NULL DEFAULT 0,
  `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `meta_value` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  PRIMARY KEY (`umeta_id`),
  KEY `user_id` (`user_id`),
  KEY `meta_key` (`meta_key`(191))
) ENGINE=MyISAM AUTO_INCREMENT=21 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

--
-- Dumping data for table `wpedpy_usermeta`
--

INSERT INTO `wpedpy_usermeta` VALUES (1,1,'nickname','adminwp'),(2,1,'first_name',''),(3,1,'last_name',''),(4,1,'description',''),(5,1,'rich_editing','true'),(6,1,'syntax_highlighting','true'),(7,1,'comment_shortcuts','false'),(8,1,'admin_color','fresh'),(9,1,'use_ssl','0'),(10,1,'show_admin_bar_front','true'),(11,1,'locale',''),(12,1,'wpedpy_capabilities','a:1:{s:13:\"administrator\";b:1;}'),(13,1,'wpedpy_user_level','10'),(14,1,'dismissed_wp_pointers',''),(15,1,'show_welcome_panel','1'),(17,1,'bglibDashboardOrder','1'),(18,1,'jetpack_tracks_anon_id','jetpack:hWRoL3j7fzST5rD/Thjdrk5k'),(19,1,'wpedpy_dashboard_quick_press_last_post_id','4'),(20,1,'community-events-location','a:1:{s:2:\"ip\";s:13:\"186.155.131.0\";}');

-- Dumped table `wpedpy_usermeta` with 19 row(s)
--

--
-- Table structure for table `wpedpy_users`
--

CREATE TABLE `wpedpy_users` (
  `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `user_login` varchar(60) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `user_pass` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `user_nicename` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `user_email` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `user_url` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `user_activation_key` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `user_status` int(11) NOT NULL DEFAULT 0,
  `display_name` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  PRIMARY KEY (`ID`),
  KEY `user_login_key` (`user_login`),
  KEY `user_nicename` (`user_nicename`),
  KEY `user_email` (`user_email`)
) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

--
-- Dumping data for table `wpedpy_users`
--

INSERT INTO `wpedpy_users` VALUES (1,'adminwp','$P$BHGkRuJc4suCXAvdgBO7nrvK7CQ6zV0','adminwp','hernan.castro@consucasa.co','','2020-02-21 20:31:47','',0,'adminwp');

-- Dumped table `wpedpy_users` with 1 row(s)
--

--
-- Table structure for table `wpedpy_wpforms_lite`
--

CREATE TABLE `wpedpy_wpforms_lite` (
  `rid` int(10) NOT NULL AUTO_INCREMENT,
  `start` bigint(20) NOT NULL,
  `end` bigint(20) NOT NULL,
  `status` tinyint(2) NOT NULL DEFAULT 1,
  `date` int(10) NOT NULL,
  PRIMARY KEY (`rid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `wpedpy_wpforms_lite`
--


-- Dumped table `wpedpy_wpforms_lite` with 0 row(s)
--


