Drupal 8 base theme built to use Spectre CSS.
Spectre.css is a Lightweight, Responsive and Modern CSS Framework.Features
1. CND and local subtheme option
2. Minimalistic approach with just a few templates overrides and preprocess
3. Implement the most needed feature from Spectre.css as form elements, menu
pages, status messages, etc..
This theme where primary build in personal need for some minimalist blog alike template.
Any additional features would be developed if the need from community arises.
For the past several years, I’ve used the Post Template plugin developed by Vincent Prat to create and manage post templates. For example, some of the information in the WordPress Weekly and In Case You Missed It posts never changes and instead of manually entering it each time, it’s nice to use a template where only a few changes are necessary.
The other day, I was wondering if I could use the reusable block feature in Gutenberg to replace the plugin. Justin Tadlock reached out and provided me a reusable block template JSON file that I imported into Gutenberg. By the way, if you successfully import a block into WordPress, the block won’t appear until you manually refresh the page.
The reusable block template approach works fairly well. However, I noticed that I was unable to add a block inside the reusable block. When I tried, a red line was displayed and any blocks that were inserted were removed.Red Means No
I understand that reusable blocks are meant to be restricted templates where changes are distributed across a site to wherever the block is displayed. But it’s still a bummer that I can’t add a block inside the template for a singular purpose if a need arises.
One other thing I noticed is that reusable blocks are custom post types. While there is a link to manage them within the reusable block selector, there isn’t a dedicated item within the admin menu. Unless you know the location of the management link, adding and managing them can be a bit more time-consuming.
If you want a quick shortcut to the reusable block management screen, add this to the URL after your domain name. wp-admin/edit.php?post_type=wp_block
I think I’ll experiment with reusable blocks a bit more but as long as they’re not changing often, I believe they’ll make a nice replacement for the Post Templates plugin. What use cases have you encountered where reusable blocks were the solution?
Branch, a Docker-based continuous integration service for WordPress, has been selected for TinySeed’s startup accelerator. The company was founded by Peter Suhm who is also the creator of WP Pusher, a plugin that lets developers install and update WordPress themes and plugins directly from GitHub, Bitbucket, and GitLab.
TinySeed, founded by Rob Walling and Einar Vollset, is a remote accelerator that focuses on providing enough funding for early-stage SaaS founders to live for a year and focus full-time on their startups. It advertises itself as “the first startup accelerator designed for bootstrappers.” TinySeed is unique in that it does not have a bias against single founders. The website states that the majority of successful $1m-$30m SaaS companies that TinySeed is connected with were started by founders working alone.
Branch fits the bill as a SaaS company with a single founder and no employees. As part of the investment terms, TinySeed invests $120k for the first founder (plus $20k per additional founder) in exchange for 8-15% equity. If founders do not need the money for living expenses they are free to spend it on growing the business. Both Branch and WP Pusher are included in Suhm’s participation in TinySeed.
“WP Pusher was doing just enough to pay my bills living in a fairly cheap city (Glasgow), but not enough to pay a full time developer salary,” Suhm said. “However, I didn’t spend much time on WP Pusher in the past few years and was working part time for other companies – mainly Timekit as a backend developer.”
Suhm said the TinySeed investment will allow him to work full time on Branch and WP Pusher for at least a year or two without having to worry about making a salary.
“I may also decide to make a hire during the program, but I want the product to be a little bit more mature,” he said. “In terms of the roadmap, I’ll be able to focus more on building the best tool and less about making a lot of money in the beginning.”
Branch and WP Pusher are fairly unique products in the WordPress space. Suhm said he sees most of his competition coming from continuous integration services that are not tailored to WordPress.
“However, my biggest competitor at the moment is probably manual labor – WordPress developers testing and deploying everything manually,” Suhm said.
TinySeed received approximately 900 applications from which they will select 10-15 companies for participation in 2019. Co-founder Rob Walling has knowledge of the WordPress ecosystem, as he previously invested in WP Engine’s 2011 round of funding.
“Peter has a distinct advantage with Branch in that he’s building on the audience, customer base, and domain knowledge he’s developed with WP Pusher,” TinySeed co-founder Rob Walling said. “His methodical approach to shipping code and content every week has been a good signal for us that he’s pushing the product forward, as well as a key factor in building Branch’s traction in the space.”
Automattic announced today that a team inside the company will be adopting Alex Mills‘ plugins and continuing their development and support. Mills, also known around the web as @Viper007Bond, was a WordPress core contributor and prolific plugin developer who passed away in February 2019 after a battle with Leukemia.
At one time last year, Mills was the primary author for and contributor to more than 40 plugins hosted on WordPress.org. The current collection seems to have been pared back to 17 of his most popular plugins. According to stats from WP Tally, these 17 plugins have a cumulative download count of 138,665,603 and a cumulative rating of 4.55 out of 5 stars.
“Since all of my plugins are open-source, they are free to be forked by reputable authors in the WordPress community. It would mean a lot to have my legacy go on,” Mills said in his farewell post earlier this year. The plugins are all free without any pro versions or monetization efforts attached to them.
“I’d never monetize any of my plugins,” Mills told the Tavern after his popular Regenerate Thumbnails plugin passed 5 million downloads in 2017. “I write them for fun not profit. It would be a conflict of interest anyway due to my employment at Automattic.”
Regenerate Thumbnails is active on more than a million WordPress sites and passed the 10 million downloads milestone in January 2019. It has already been downloaded more than 7,000 times today and has regularly received 3K-12k downloads per day throughout 2019.
The enduring popularity of Regenerate Thumbnails is a testament to Mills’ commitment to writing future-proof plugins. What started as a small plugin to fix a client’s problem in 2008 quickly became an indispensable utility for millions of WordPress users transitioning between themes with different image sizes. For those users who could never write their own script to generate new thumbnail sizes, Mills’ plugin was a little piece of time-saving magic that exemplifies the significant contributions plugin developers can make when they write and share code that solves a common problem.
Automattic plans to fork each of Mills’ GitHub repositories and will add them to the Automattic Github account. The team behind this effort is also adding the following paragraph to each plugin’s readme file:
In February 2019 Alex Mills, the author of this plugin, passed away. He leaves behind a number of plugins which will be maintained by Automattic and members of the WordPress community. If this plugin is useful to you please consider donating to the Oregon Health and Science University.
Automattic will also be answering support queries on the forums and the team is open to receiving help from other members of the WordPress community in maintaining and supporting Mills’ plugins.
“In times gone by authors left works of music, novels, poetry, and letters on their passing,” Donncha Ó Caoimh said on the Automattic Engineering blog. “They were static works of art frozen in time. Alex leaves behind his code that will continue to evolve and operate in a living world used by thousands (millions?) of people every day as they go about their online lives.”
In this episode, John James Jacoby and I discuss Joost de Valk’s decision to step down as WordPress’ Marketing Lead. I shared my recent encounter with food poisoning and some of the lifestyle changes I’m making to improve my health. We also talk about a new experimental plugin by Automattic that aims to provide full site editing and FreeCodeCamp’s decision to migrate away from Medium to Ghost.Stories Discussed:
Next Episode: Wednesday, June 12th 3:00 P.M. Eastern
Subscribe to WordPress Weekly via Itunes
Subscribe to WordPress Weekly via RSS
Subscribe to WordPress Weekly via Stitcher Radio
Subscribe to WordPress Weekly via Google Play
Listen To Episode #355:
Google’s rich results testing tool has been updated to include a selector for desktop or mobile so website owners can check their results on both platforms. This tool shows if pages are properly structured for display in Google’s carousels, images, breadcrumbs, events, books, and other types of rich snippets. A glossary is available with images showing what each type of result looks like with the proper structured data in place.
Last week Google announced that it will begin enabling mobile-first indexing (crawling sites with a mobile user-agent) by default for new domains on July 1, 2019. Site owners can select “Googlebot Smartphone” as the user-agent on the rich results testing tool to see if their sites are prepared for mobile-first indexing. The tool is still in beta, so not all rich results and error types are supported yet.
If your page supports rich results, you will see a confirmation and can click through to view the HTML. Certain rich result types will display a preview of how the result might appear in Google Search. If multiple result layouts are available, the tool will also let you drill down into the different layouts for both desktop and mobile.
If you get a result that says “Page not eligible for rich results known by this test” when you know that you have the structured data in place, it could be because the beta version of this tool only supports a subset of rich result types. These currently include job postings, recipes, courses, TV and movie, events, and Q&A pages.
You can also test your page using this tool by putting in a code snippet, in case your content is not publicly accessible or is restricted behind authorization.
Depending on your specific requirements, there are many different WordPress plugins that properly structure data to improve how your content appears in rich results around the web, such as Schema, All In One Schema Rich Snippets, Schema App Structured Data, Rank Math, and Yoast SEO, to name a handful of popular options.
Joost de Valk has announced that he’s stepped down from the WordPress Marketing and Communications Lead role. The position was created and awarded to de Valk earlier this year. Not only was it a new position, but it also expanded the leadership roles in the WordPress project.
Despite making progress, de Valk didn’t feel as though he was fulfilling the leadership aspect of his role. “My experience over the last few months made me feel that while I was doing things and getting things done, I certainly wasn’t leadership. I don’t want to pretend I have a say in things I don’t have a say in,” he said.
Not having a clear definition of what marketing means and having people within the project on the same page contributed to his decision.
“There’s a stark difference between where I thought I would be in the organization in this role, and where I am actually finding myself now,” de Valk said.
“Even things that every outsider would consider marketing (release posts, about pages) are created without even so much as talking to me or others in the marketing team. Because I felt left out of all these decisions, I feel I can’t be a marketing lead.”
He also cited a lack of clarity surrounding his position, “I’ve been asked dozens of times on Twitter, Facebook and at WordCamps why I now work for Automattic, which of course I don’t but that is the perception for a lot of people,” he said. “On other occasions, I seem to be the token non-Automattician, which I’m also uncomfortable with.”
Due to taking a toll from failing to fulfill the position, de Valk plans to take an extended vacation during the Summer and when he returns, focus 100% of his efforts on Yoast and his Chief Product Officer role.
Matt Mullenweg commented on de Valk’s article thanking him for being willing to try new things and for his passion, impatience, and drive to improve WordPress.
Tantek Çelik, Web Standards Lead at Mozilla and co-founder of IndieWebCamp, delivered an inspirational talk titled “Take Back Your Web” at the most recent beyond tellerrand conference in Düsseldorf, Germany. He opened the presentation with a litany of Facebook’s wrongdoings, taking the world’s largest social network to task for its role in increasing polarization, amplifying rage, and spreading conspiracy theories.
Çelik challenged the audience to “stop scrolling Facebook,” because its algorithms are designed to manipulate users’ emotions and behaviors. He noted that it is the only social network with a Wikipedia page dedicated to its criticism. This massive document has a dizzying number of references, which Wikipedia says “may be too long to read and navigate comfortably.” As an alternative to scrolling Facebook, Celik encouraged attendees to spend time doing nothing, an activity that can be uncomfortable yet productive.
The “Take Back Your Web” presentation is a call to action to join the independent web by owning your own domain, content, social connections, and reading experience. Celik recommends a number of IndieWeb services and tools to empower users to take control of their experiences on the web.
With a free site hosted on GitHub, he said the costs of owning your own domain are less than owning a phone or having internet service. Suggestions like this are targeted at developers who share Twitter names instead of domains and post articles on Medium. Setting up a site on GitHub is not a simple task for most. That’s why networks like WordPress.com, along with hosts that provide instant WordPress sites, are so important for enabling average internet users to create their own websites.
Celik referenced Matthias Ott’s recent article “Into the Personal-Website-Verse,” highlighting the section about the value of learning new technologies by implementing them on your own website: “A personal website is also a powerful playground to tinker with new technologies and discover your powers.” It’s one of the few places developers can expand their skills and make mistakes without the pressure to have everything working. Ott enumerates the many benefits of people having their own enduring home on the web and encourages developers to use their powers to make this a reality:
As idealistic as this vision of the Web might seem these days, it isn’t that far out of reach. Much of what’s needed, especially the publishing part, is already there. It’s also not as if our sites weren’t already connected in one way or another. Yet much of the discussions and establishment of connections, of that social glue that holds our community together – besides community events in real life, of course –, mostly happens on social media platforms at the moment. But: this is a choice. If we would make the conscious decision to find better ways to connect our personal sites and to enable more social interaction again, and if we would then persistently work on this idea, then we could, bit by bit, influence the development of Web technologies into this direction. What we would end up with is not only a bunch of personal websites but a whole interconnected personal-website-verse.
Check out Çelik’s slides for the presentation and the recording below for a little bit of inspiration to re-evaluate your relationship with social networks, create your own site, or revive one that has been neglected.
Jetpack 7.4 is now available and includes a new Business Hours block. This block contains a toggle that users can set to show whether they’re open or closed.
There’s also a way to add additional times so restaurants, for example, can display when they’re open for breakfast, lunch, and dinner. However, I couldn’t figure out a way to add text to label what the hours mean. Also, depending on the theme, the alignment displays incorrectly. You can see the block in action below.
- 9:00 AM – 1:00 PM
5:00 PM – 10:00 PM
- 9:00 AM – 5:00 PM
- 9:00 AM – 5:00 PM
- 9:00 AM – 5:00 PM
- 9:00 AM – 5:00 PM
The Slideshow, Carousel, and Tiled Galleries blocks have all received enhancements to improve their look and performance on mobile devices. The Carousel block also contains better theme compatibility.
WhatsApp is now included in the Jetpack Sharing module. Users can enable it by browsing to Jetpack > Settings > Sharing > Configure sharing buttons. The button supports sharing content through the stand-alone app and the web interface.
Jetpack 7.4 also makes a number of enhancements to the Recurring Payments block such as improving the display of the renewal frequency in the button list and improving the look of the payment modal on mobile devices. This version also requires users to be on the Premium or Professional plan on WordPress.com in order to access the button.
You can see a full list of changes in 7.4 by viewing the changelog.
This month saw the 16th anniversary since the launch of the first release of WordPress. A significant milestone to be sure and one that speaks to the strength and stability of the project as a whole. In this anniversary month, we saw a new major release of WordPress, some exciting new development work, and a significant global event.Release of WordPress 5.2
WordPress 5.2 “Jaco” was released on May 7 shipping some useful site management tools, such as the Site Health Check and PHP Error Protection, as well as a number of accessibility, privacy, and developer updates. You can read the field guide for this release for more detailed information about what was included and how it all works.
327 individual volunteers contributed to the release. If you would like to be a part of that number for future releases, follow the Core team blog and join the #core channel in the Making WordPress Slack group.A Successful WordPress Translation Day 4
WordPress Translation Day is a 24-hour event organised by the Polyglots team where community members from all over the world come together to translate WordPress into their local languages. For the fourth edition held on 11 May, 183 brand new contributors joined the Polyglots team from 77 communities across 35 countries in Africa, Asia, Europe, North America, South America, and Oceania.
While the WP Translation Day is a great time for focussed contributions to localizing WordPress, but these contributions can happen at any time of the year, so if you would like to help make WordPress available in your local language, follow the Polyglots team blog and join the #polyglots channel in the Making WordPress Slack group.Updated Plugin Guidelines Proposal
The Plugins team has proposed some updates to the guidelines for developers on the Plugin Directory. The majority of the proposed changes are intended to address significant issues faced by developers who do not speak English as a first language, making the Plugin DIrectory a more accessible and beneficial place for everyone.
The proposal will be open for comments until late June, so the community is encouraged to get involved with commenting on them and the direction they will take the Plugin Directory. If you would like to be involved in this discussion, comment on the proposal and join the #plugin review team in the Making WordPress Slack group.Continued Gutenberg Development
Since the block editor was first released as part of WordPress Core in v5.0, development has continued in leaps and bounds with a new release every two weeks. The latest update includes some great incremental improvements that will be merged into the 5.2.2 release of WordPress along with the other recent enhancements.
In addition to the editor enhancements, work has been ongoing in the Gutenberg project to bring the block editing experience to the rest of the WordPress dashboard. This second phase of the project has been going well and the latest update shows how much work has been done so far.
In addition to that, the Block Library project that aims to bring a searchable library of available blocks right into the editor is deep in the planning phase with a recent update showing what direction the team is taking things.
If you would like to get involved in planning and development of Gutenberg and the block editor, follow the Core and Design team blogs and join the #core, #design, and #core-editor channels in the Making WordPress Slack group.Further Reading:
- The 5.2.2 release of WordPress is currently in development with a planned release date of 13 June.
- Version 2.1.1 of the WordPress Coding Standards has been released containing seven small, but relevant fixes.
- The Theme Review Team have updated the details of how the Trusted Authors Program works.
- WordCamp-specific blocks have been launched for WordCamp sites with organizers needing to sign up in order to test them out.
- Continuing the growing trend of other platforms adopting the Gutenberg editor, it has now been ported to a plugin for OctoberCMS.
- Version 3.0 of the popular WordPress development environment, Varying Vagrant Vagrants (VVV), was released this month.
- The Community Team published some info clarifying what organizers get (and don’t get) from being involved with their local communities.
Have a story that we should include in the next “Month in WordPress” post? Please submit it here.
In a post titled “Using Motion to Express Change,” Gutenberg designer and engineer Matías Ventura takes a deep dive into how animation can be applied to interfaces to replicate realistic motion. These animations can sometimes more clearly communicate changes, particularly in relationship to the action of moving or reordering items on a page.
“Even though the instant transformation of the interface is accurate it may not be the clearest expression of the change that just occurred,” Ventura said. “The relationship between intention and effect might become harder to grasp. Motion can be a great aid in communicating relationships and clarifying the changes experienced in a more intuitive way.”
This creates an interesting choice for an interface designer. Although instantaneous changes are possible to implement, they may require more time for the user’s brain to process. In the case of an editor, any added cognitive processing can pull a user out of the flow of writing. Ventura sets a good practical rule of thumb for determining if an animation adds value to an interaction:
One could say that an animation is worth being present if the clarity of change it provides is greater than the time it would take to adjust cognitively to the new state in its absence.
Ventura illustrates this concept with two video demos in his post – one showing how block reordering currently looks in WordPress’ editor and a second with an example of how it could be improved with subtle, tasteful animations. It’s an early prototype but very convincing:
When Gutenberg was still in the selling phase before being merged into core, some said that moving forward was simply a matter of retraining your muscle memory to work with the new editor. However, at that time there were still a number of markedly flawed interactions that didn’t feel natural and were even jarring for the user. The legacy editor didn’t have blocks to reorder or many of the other interactions introduced by the new block paradigm, so there wasn’t much prior context for comparison.
User reviews have complained about the cognitive load that Gutenberg adds and have continued to identify problematic interactions with the core blocks. Unfortunately, in many heated exchanges that took place in comments and discussions prior to WordPress 5.0’s release, these concerns were often brushed aside as coming from people who were resistant to change.
Many of the reviewers may not have had the right words to communicate what it was they were experiencing, but the cognitive load may be one of the strongest reasons why the Classic Editor plugin has more than 5 million active installs.
Matías Ventura’s proposal to add motion to express change in the editor has the potential to solve some of these unintuitive interactions. The Gutenberg repository now has an issue dedicated to exploring and discussing the use of motion to add clarity to the action of reordering blocks.
Ventura’s post is an encouraging read that demonstrates the thought and craftsmanship that go into architecting an interface that is required to meet the needs of millions of users. If you have been impatient with Gutenberg’s progress, as I have been, it’s important to recognize that these kinds of refinements to interactions take time to percolate. Replicating realistic motion comes from contemplating how we interact with the known world and understanding how that informs users’ digital expectations.
Ugyen Dorji is from Bhutan, the landlocked country situated between two giant neighbors, India to the south and China to the north. Ugyen works for ServMask Inc and is responsible for the robust Quality Assurance process for All-in-One WP Migration plugin. He believes in the Buddhist teaching that “the most valuable service is one rendered to our fellow humans” and his work ethic shows with managing WordPress translation projects for his Plugin ’All-in-One WP Migration.’ Ugyen also keeps multi-language support for WordPress; furthermore the plugin is now translated into 42 languages with more on the way.How Ugyen started his career with WordPress
Life is a struggle – it is a mixture of success and failure which can come in any venture and that too late and sometimes most unexpectedly people lose heart after a failure; but a person who takes failure in his/her stride and continues his effort for success in long run in the word of EL Kerten means “The secret of success is knowing whom to blame for your failure.”
Back in 2016, he had been looking for new working place after his former cloud company got shattered with some financial crisis, he has looked for a new job. For which he has tried his best and one fine day he makes it to an interview – where he has been triggered with WordPress questionnaires. On that moment he has no proper answer for interviewers saying big number to interviewers, though he has basic knowledge about WordPress. After that day, just sat in his room with silence and made up his mind to learn and get skilled himself with WordPress wisdom, watching cities from his window receiving cool air, and said himself
“I will make my career with WordPress and it will be my bread and butter”.
After a few months, he received a call from ServMask Inc, who developed a great plugin called “All-in-One WP Migration” which made his dream come true like an angle ServMask Inc blessed his dream to make his living with WordPress. Ugyen is now an active contributor to the WordPress Community.Ugyen’s First WordCamp Experience
WordCamp is a genuine spotlight for plugin and theme developers to reach WordPress users and website developers. It’s a glorious atmosphere where many incredible talks about WordPress take place. The “tribe” meetings are a phenomenal moment for aspiring computer engineers, content writers and developers to showcase their talent and meet each other.
WordCamp Bangkok 2018 was an essential day for Ugyen and ServMask because their sponsorship of the event delivered them the opportunity to connect with our active WordPress users and showcase their appreciation on better quality of WordPress plugin.Contributor Day
The first day of WordCamp is Contributor Day. Ugyen associated with a community team and got to share a conversation with WordPress folks from all over the world. Community communication is the ground root of WordCamp and WordPress meetups, giving him all the chance to share and manifest what WordPress does and how it is used. He also addressed encouraging more speakers and WordPress members to nurture their experience and whereby he could support new organizers to continue and contribute to building the WordPress community in places where it is not yet booming.Conference Day
Conference Day is the main event of WordCamp and is held on the second day. Ugyen was taking care of a Photo Booth for people to snap their memories. I think this was a great idea to capture the memories of WordCamp for attendees, speakers, and organizers.
The foremost intention of the conference day is the presentations that take place throughout the day. Ugyen had a great moment to attend various talks which were very beneficial for developers, entrepreneurs, firms, and young startups firms. What holds in Ugyen’s mind is a plan that exhibits leveraging website content has been shown to lead to 100% growth in business extension.How Ugyen became WordPress Meetup Thimphu Co-Organizer
Following October 2016, Ugyen came over about WordPress Meetup Bangkok and WordCamp Bangkok 2018. From that onwards, the importance of WordPress Meetup catches on his mind to introduce WordPress to his home country and cities. The foremost incidence that clicks on his mind was on WordPress Translation Day 3 on September 30, 2017, during WordPress Meetup Bangkok where he has seen his locale Dzongkha was in lowest percentage comparing to another locale status on WordPress Core Translation. Later in WordCamp Bangkok 2018 Contributors day when he met with WordPress Folks and WordPress Community, Meetup Organizer from many countries.
WordPress Meetup Thimphu is an easygoing, volunteer-organized, non-profit meetup covering everything related to WordPress and keeping our Bhutanese Gross National Happiness four pillars in mind with aims to preserve and promote our unique culture and national language. WordPress Meetup implies for individuals and all people who love WordPress and want to contribute and share their knowledge and have experience in meeting new faces and for networking. Ugyen’s Specific focus on encouraging local and international language WordPress bloggers and help startup companies to grow their assets with WordPress and share what he has learned from WordPress with his Bhutanese WordPress community.
Ugyen’s First WordPress Meetup Thimphu was a huge success within his community coinciding with WordPress Main event WordPress Translation Day 4. Ugyen would take a more vital role in preserving his national language by making use of WordPress actively by our Dzongkha bloggers, online Dzongkha news, government websites so that Bhutanese WordPress core contributors could hand over to our next generation very proudly.
What we have achieved :
- Done WordPress Core Translation for our locale Dzongkha.
- New Translation Contributor for our WordPress Core Translation for Dzongkha.
- Participated in Global WordPress Translation Day 4 Livestream.
- Invited WordPress Experts from other countries to http://wpbhutan.slack.com.
- Invited WordPress Meetup Thimphu members to http://wpbhutan.slack.com to discuss more on WordPress related topics and for helpline on WordPress for Bhutanese WordPress users and wordpress.org login for new users.
- Speaker of the event Tenzin Namgyel Senior ICT officer from DDC WordPress Local Manager and General Translation Editor for our locale Dzongkha.
- Good meal and tea with great place to host at Ariya Hotel
- Introduction of a member for networking.
- Became a part of Global WordPress Translation Day 4 team.
- Event Sponsored by ServMask Inc and Helped by Dzongkha Development Commission with Language Experts.
“The best preparation for tomorrow is to do today’s work superbly well” so that we can put all our effort, then we’ll see a very good result and success will surely be yours. No men can hope to have a very successful life but there will be one or two in exception in this earthly world in thousand cases of this matter which results strong determination can help to attain success. Therefore with Ugyen’s determination here are some of his road plans for WordPress.
For WordPress Meetup: Ugyen’s next plan is to visit the language universities and teach them to blog in Dzongkha using WordPress. He said, “ We have plans to gather a group of active Bhutanese WordPress Bloggers and host panel talks to extend the beauty of Bhutan and unique culture of Bhutan to outside nations. And also one of the WordPress Main Events: Introduction to Open Source is in a process to be host soon. His Majesty the fourth King of Bhutan once said, “the future of our nation lies in the hands of our children.” Therefore Ugyen works to focus more on youth to enhance their WordPress Skills.
For WordCamp: WordCamp Thimphu is my goal – to reach and invite more WordPress Experts as speakers of the main event and support Bhutanese to grow their career with WordPress. WordCamp Asia is in the process to kick start in 2020 and become one of the WordCamp Co-organizer among 41 WordCamp Asia Co-Organizers.
To WordPress lovers – “If you want to be successful the ball is in your court, you think to throw a ball outside or smash the ball or play the game nicely and win the game’’ཚིག་གསར་དཔེ་སྐྲུན་ལས་ཁང་ལུ་རྒྱབ་སྐྱོར་གྱི་དོན་ལུ་ ཨོ་རྒྱན་གྱི་ལམ་ཡིག
ཨོ་རྒྱན་རྡོ་རྗེ་གི་སྐྱེ་སའི་ཕ་ཡུལ་ནི་འབྲུག་རྒྱལ་ཁབབ་ཨིན། འབྲུག་རྒྱལ་ཁབ་འདི་ཁྱིམ་ཚང་རྒྱལ་ཁབ་ རྒྱ་དང་བོད་ཀྱི་བར་ན་ ཕྱི་ཡི་ལྕགས་རི་མཚུངས་པའི་ གང་རི་ཚུ་གི་བསྐོར་ཏེ་ ཡོདཔ་ཨིན། ཨོ་རྒྱན་གྱི་ ལཱ་འབད་ས་འདི་ ServMask Inc ནང་འབད་དོ་ཨིནམ་ད་ ཁོ་གི་ལཱ་འགན་ངོ་མ་འདི་ WordPress གི་ས་གནས་གཞན་ཁར་སྤོ་འགྱོ་ནིའི་ལས་རིམ་ཚུ་ པུས་ཚད་སྒྲིང་སྒྲིང་བཟོ་ནི་ལུ་ ཡིད་ཆེས་བསྐྱེད་བཅུག་ནི་འདི་ཨིན།
ཁོ་ནང་པ་སངས་རྒྱས་ཀྱི་ཆོས་ལུགས་ལུ་ཡང་ སྙིང་ཐག་པའི་གཏིང་ལས་ ཡིད་ཆེས་ཡོད་མི་ཅིག་ཨིན་པའི་ཆ་གནས་ལས་ ཁོ་གིས་ལཱ་འབད་ཐངས་ཡང་ ཚིག་གསར་དཔེ་སྐྲུན་ལས་ཁང་གི་ སྐད་སྒྱུར་ལས་འཆར་གྱི་ འཛིན་སྐྱོང་འཐབ་ནི་འདི་ཨིན་མས། འདི་མ་ཚད་ ཁོ་གི་ WordPress གི་དོན་ལུ་ སྐད་ཡིག་སྣ་མང་གི་ རྒྱབ་སྐྱོར་ཚུ་འབད་དོ་ཡོདཔ་མ་ཚད་ ད་ཚུན་གྱི་རིང་ All-in-One WP Migration plugin འདི་སྐད་ཡིག་མ་འདྲཝ་༤༢་༢དེ་ཅིག་ནང་ སྐད་སྒྱུར་འབད་དེ་ཡོདཔ་ཨིན།ཨོ་རྒྱན་གྱི་ཚིག་གསར་དཔར་སྐྲུན་ལས་ཁང་དང་མཉམ་གཡོག་གི་མདུན་ལས་ག་དེ་སྦེ་འགོ་བཙུགས་ཡི་ག་གི་སྐོར།
ང་བཅས་རའི་མི་ཚེ་གི་ལམ་འདི་ གདོང་ལེན་དྲག་པོ་ཅིག་ཨིན། མི་ཚེ་འདི་ནང་ལཱ་དང་བྱ་བ་ག་ཅི་ར་འབད་རུང་ མཐར་འཁྱོལ་ནི་དང་འཐུས་ཤོར་ནི་འདི་ རང་བཞིན་ཅིག་ཨིན། ཨིན་རུང་མི་མང་ཤོས་ཅིག་གི་ར་ ལཱ་འདི་རང་གི་མནོ་བཞིན་བསམ་བཞིན་འགྱོ་མ་བཏུབ་པའི་བསྒང་ལས་ བློ་ཕམ་སི་སི་སྦེ་ ཚར་ཅིག་གུ་མནོ་བསམ་ག་ནི་ཡང་མ་གཏང་པར་ གདོང་ལེན་ཅན་གྱི་མི་ཚེ་འདི་ལུ་ གདོང་ལེན་འབད་མ་ཚུགས་པར་ རྒྱབ་ཤུད་རྐྱབ་སྡོདཔ་མས། རང་གི་མི་ཚེ་ནང་ཚགས་ཁ་མ་ཚུད་པའི་འཐུས་ཤོར་འབྱུང་རུང་ འདི་ལས་ཡོན་ཏན་ལེན་སྟེ་ མི་ཚེ་འདི་ནང་མཐར་འཁྱོལ་ནི་ལུ་གཙོ་བོ་བཏོན་ནི་བཀོ་མ་བཞག་པར་ འཕྲོ་མཐུད་དེ་ར་བརྩོན་འགྲུས་བསྐྱེད་དེ་ལཱ་འབད་མི་ མི་འདི་གིས་ མི་ཚེ་ནང་འབྲས་བུ་ལེགས་ཤོམ་འབག་ནི་ཡོདཔ་ཨིན། མཁས་དབང་ཨིལ་ཀར་ཊྲན་གྱི་ཡང་ མི་ཚེ་ནང་མཐར་མཁྱོལ་ནི་དོན་ལུ་གསང་བ་ངོ་མ་འདི་ར་ འཐུས་ཤོར་བའི་གནད་དོན་འདི་ལུ་རྫུན་ཁ་བཀལ་ཤེས་ནི་འདི་ཨིན་ ཟེར་གསུངས་ནུག དེ་བཟུམ་སྦེ་ར་ ཨོ་རྒྱན་ཡང་ཧེ་མ་ དབྱིན་ལོ་༢༠༡༦་ལུ་ཁོ་རའི་ལཱ་འབད་སའི་ ཀལཝཏ་ཚོང་སྡེ་འདི་དངུལ་འབྲེལ་གྱི་དཀའ་ངལ་ཅིག་འཐོན་སྟེ་ སྒོ་བསྡམ་པའི་ཤུལ་ལུ་ ཁོ་ཡང་ལཱ་གཡོག་གསརཔ་ཅིག་ནང་འཛུལ་ཞུགས་འབད་ནིའི་དོན་ལུ་ གཡོག་གི་ས་གོ་ཅིག་འཚོལ་སྟེ་ར་སྡོད་པའི་ཤུལ་ལུ་ ཉིནམ་ཅིག་འབདཝ་ད་ ཚིག་གསར་དཔེར་སྐྲུན་ལས་ཁང་དང་མཉམ་ གཡོག་གི་དོན་ལུ་དྲི་བ་དྲི་ལན་འབད་ནིའི་གོ་སྐབས་ཅིག་ཐོབ་ནུག རེ་འདོད་ཅན་གྱི་ཉིནམ་འདི་ལས་འགོ་བཟུང་ ཁོགི་སེམས་ཁར་ ཁོ་རའི་མི་ཚེ་འཚོ་ཐབས་ཀྱི་དོན་ལུ་ ཡུན་དུ་གནས་པའི་འོང་འབབ་ཀྱི་གཞི་གཙོ་བོ་འདི་ ཚིག་གསར་དཔར་སྐྲུན་ལས་ཁང་ར་ཨིན་ཟེར་མནོ་ནུག ཟླཝ་དག་པ་ཅིག་གི་ཤུལ་ལས་ འཛམ་གླིང་ནང་གཞན་དང་མ་འདྲ་བའི་ལས་འགུལ་ ‘ག་ར་མཉམ་གཅིག་འཛོམས་ཚུགས་པའི་ ཚིག་གསར་དཔར་སྐྲུན་ལས་ཁང་གི་ ས་གནས་སྤོ་བ་’ ཟེར་མི་གསར་བཟོ་ཚོང་སྡེ་ནང་ལས་ ServMask གིས་འགྲུལ་འཕྲིན་ལྷོད་དེ་ ཁོ་བཙག་འཐུ་བསྒྲུབ་པའི་གནས་ཚུལ་གོཝ་ད་ ཁོ་གིས་ཁོ་རའི་རེ་བ་བསྐྱེད་མི་ རེ་འདོད་འདི་དངོས་སུ་སྦེ་འགྲུབ་པའི་དགའ་བ་ཚད་མེདཔ་སྦེ་འབྱུང་ནུག འདི་འབདཝ་ལས་བརྟེན་ ད་རིས་ཨོ་རྒྱན་ཡང་ ཚིག་གསར་དཔེར་སྐྲུན་ལས་ཁང་གི་དོན་ལུ་ འཇོན་ཐངས་ཅན་གྱི་ལས་གཡོགཔ་ཅིག་ཨིན་མས།ལྟ་བ་མཐུན་པའི་གནས་ཚུལ་སྡེ་ཚན་ནང་ཨོ་རྒྱན་གྱི་ཉམས་མྱོང་འགོ་དང་པ།
ལྟ་བ་མཐུན་པའི་གནས་ཚུལ་སྡེ་ཚན་འདི་ plugin དང་བརྗོད་དོན་གསར་བཟོ་མཛད་མི་ཚུ་ WordPress ལག་ལེན་འཐབ་མི་དང་་ཡོངས་འབྲེལ་ཁ་རྒྱང་གསར་བཟོ་འབད་མི་ཚུ་གི་ གནས་ཚད་ནང་ལྷོད་ཚུགས་ནི་དོན་ལུ་ཡིད་ཆེས་བཏུབ་པའི་ ཐད་དམིགས་བཟུམ་ཅིག་ཨིན་མས། WordPress གི་སྐོར་ལས་གནས་ཚུལ་དང་གསུང་བཤད་གནམ་མེད་ས་མེད་ལེགས་ཤོམ་ གོ་ཡོདཔ་ལས་ ཚོང་སྡེ་འདི་མིང་གཏམ་ཅན་ཅིག་ཨིན་པའི་ ཚོར་སྣང་དང་དགའ་བ་འབྱུང་ཡི། འདི་མ་ཚད་ ཁོང་མི་རིགས་ལེ་ཤ་གཅིག་ཁར་ཚོགས་སྟེ་ ཞལ་འཛོམས་གནང་ནིའི་སྲོལ་ཡོད་མི་འདི་ ལྷག་པར་དུ་ ཁོང་གློག་རིག་འགོ་དཔོན། བརྗོད་དོན་རྩོམ་སྒྲིག་པ་དང་གསར་བཟོ་པ་ཚུ་གི་དོན་ལུ་ ཁོང་རའི་རིག་རྩལ་དང་ལྕོགས་གྲུབ་དཔེ་སྟོན་འབད་ནིའི་དོན་ལུ་ རེ་འདོད་ཅན་གྱི་དུས་ཚོད་ལེགས་ཤོམ་ཅིག་འབད་མཇལ་ཡི།
འཛམ་གླིང་ལྟ་བ་མཐུན་པའི་སྡེ་ཚན་ བེང་ཀོག ༢༠༡༨་འདི་ ཨོ་རྒྱན་དང་ ServMask གི་དོན་ལུ་ ཉིནམ་ཁག་ཆེ་ཏོག་ཏོ་ཅིག་ཨིན། འདི་ཡང་ཉིནམ་འདི་ཁར་ དུས་སྟོན་འདི་གི་དངུལ་གྱི་རྒྱབ་སྐྱོར་པ་གིས་ ཁོང་ཚུ་ལུ་སྤུ་འགྱིར་དྲག་ཡོད་པའི་ WordPress སྤྱོད་མི་ཚུ་དང་འབྲེལ་བ་འཐབ་སྟེ་ WordPress Plugin གི་སྤུས་ཚོད་ཧེང་སྐལ་ཡར་དྲག་འགྱོ་ནིའི་དོན་ལུ་ ཁོང་རའི་ངལ་རངས་གསལ་སྟོན་འབད་ནིའི་གོ་སྐབས་གནང་ཡོདཔ་ལས་བརྟེན་ཏེ་ཨིན་མས།རྒྱབ་སྐྱོར་པའི་ཉིནམ།
WordCamp གི་ཉིནམ་དང་པ་འདི་ རྒྱབ་སྐྱོར་པའི་ཉིནམ་སྦེ་བརྩིཝ་ཨིན། ཉིནམ་འདི་ཁར་ཨོ་རྒྱན་གྱི་ མི་སྡེའི་སྡེ་ཚན་ཚུ་དང་འབྲེལ་བ་འཐབ་སྟེ་ ཕྱོགས་བཞི་མཚམས་བརྒྱད་ལས་འོང་མི་ WordPress གི་སྡེ་ཚན་ཚུ་དང་མཉམ་ ཁོ་རའི་བསམ་འཆར་བརྗེ་སོར་འབད་ནིའི་གོ་སྐབས་བཟང་པོ་ཡང་ཐོབ་ནུག མི་སྡེ་བརྡ་སྤྲོད་ཀྱི་ WordCamp དང WordPress གི་ཞལ་འཛོམས་འདི་ ཨོ་རྒྱན་གྱི་དོན་ལུ་ WordPress གི་ལཱ་ག་དེ་སྦེ་འབདཝ་ཨིན་ན་དང་ འདི་ག་དེ་སྦེ་ལག་ལེན་འཐབ་ནི་ཨིན་ན་ཚུའི་སྐོར་ གཞན་ལུ་བཤད་ནི་གོ་སྐབས་ཁྲིལ་བུ་སྤྲོད་མི་ ལམ་སྟོན་ཅིག་མས། དེ་གིས་སྦེ་ ཁོ་གི་ད་ལས་ཕར་གསལ་བཤད་པ་ག་དེ་མང་མང་དང་ WordPress གི་འཐུས་མི་ཚུ་ ཁོང་རའི་ཉམས་མྱོང་དང་ལྕོགས་གྲུབ་ཡར་དྲག་བཏང་ནིའི་སེམས་ཤུགས་ག་དེ་དྲག་དྲག་བསྐྱེད་བཅག་ནི་ཟེར་ སླབ་ཡོདཔ་མ་ཚད་ ཁོ་གི་འགོ་འདྲེན་པ་གསརཔ་ཚུ་ལུ་ཡང་ WordPress མི་སྡེ་འདི་དར་ཁྱབ་མ་འགྱོ་བའི་ས་གོ་ནང་ལས་ཕར་ ངོ་སྤྲོད་འབད་དེ་ ལག་ལེན་འཐབ་བཅུག་ནིའི་དོན་ལུ་ འཕྲོ་མཐུད་དེ་ར་ རྒྱབ་སྐྱོར་དང་གྲོགས་རམ་འབད་ནི་ཨིན་མས།གྲོས་ཚོགས་ཀྱིས་ཉིནམ།
གྲོས་ཚོགས་ཀྱི་ཉིནམ་འདི་ WordCamp གི་ལས་རིམ་གཙོ་བོ་ཅིག་ཨིན། དེཡང་ཉིནམ་གཉིས་པའམ་འདི་ནང་ འགོ་འདྲེན་འཐབ་ཨིན། འདི་གི་སྐབས་ ཨོ་རྒྱན་གྱིས་ མི་ཚུ་གི་ དྲན་ཐེ་བཞག་ནིའི་དོན་ལས་ པར་བཏབ་ནི་གིས་ ལཱ་འགན་འདི་འབགཔ་ཨིན། ངེའི་སེམས་ཁར་ལས་འབད་བ་ཅིན་ འདི་བཟུམ་མའི་ གནས་སྐབས་འདི་ WordCamp གི་ལས་རོགསཔ་ གསལ་བཤདཔ་དང་ འགོ་འདྲེན་པ་ཚུ་གིས་ དྲན་ཐོ་བཞག་ནི་དོན་ལུ་ གནམ་མེད་ས་མེད་ལེགས་ཤོམ་ཅིག་ ཨིན་པས་ཟེར་མནོཝ་མས། མི་རིགས་ལུ་ཕན་ཐོགས་པའི་ཞབས་ཏོག་འདི་ཁྱད་དུ་འཕགསཔ་ཨིན། ང་བཅས་འགྲོ་བ་མི་ལུ་ ཕན་ཐོགས་པའི་ལཱ་འབད་མི་འདི་ ཞབས་ཏོག་ཚུ་གི་གྲས་ལས་ དྲག་ཤོས་ཅིག་ཨིན།
ཨྱོན་འདི་ WordPress Meetup ཐིམ་ཕུག་གི་འགོ་འདྲེན་པ་ག་དེ་སྦེ་འབད་ཡོདཔ་ཨིན་ན།
འདི་ཡང་ ཨྱོན་ཁོ་རང་ སྤྱི་ལོ་༢༠༡༦ སྤྱི་ཟླ་༡༠པའི་ ནང་ WordPress Meetup Bangkok དང་ WordCamp Bangkok ༢༠༡༨ ཀྱི་ནང་ལས་ WordPressགི་སྐོར་ལས་ཧ་གོ་བའི་ཤུལ་ འབྲུག་རྒྱལ་ཁབ་ནང་ལུ་ཡང་ གཞི་བཙུགས་འབད་དགོཔ་ཁག་ཆེ་བའི་སྐོར་ལས་ ཤེས་ཡོདཔ་ཨིན་མས།
འདི་ཡང་ སྤྱི་ལོ་༢༠༡༧ སྤྱི་ཟླ་༩པའི་ སྤྱི་ཚེས་༣ རྒྱལ་སྤྱི་ WordPress སྐད་བསྒྱུར་གྱི་ཉིནམ་གྱི་སྐབས་ལུ་ WordPress Meetup Bangkok ལུ་ རྫོང་ཁ་འདི་ WordPress Core Translation ནང་ རྫོང་ཁ་འདི་ གཞན་མི་སྐད་ཡིག་དང་ཕྱདཔ་དང་ དམའ་ཤོས་ཅིག་སྦེ་ཡོདཔ་མཐོང་ཡོདཔ་ཨིན་མས།
དེའི་ཤུལ་ལས་ WordCamp Bangkok ༢༠༡༨ རྒྱབ་སྐྱོར་པའི་ཉིནམ་གྱི་སྐབས་ལུ་ WordPress གི་མཉམ་རོགས་དང་ WordPress གི་མི་སྡེ་ དེ་ལས་ རྒྱལ་ཁབ་གཞན་ཁའི་ Meetup འགོ་འདྲེན་པ་ཚུ་དང་ཕྱད་ཡོདཔ་ཨིན་མས།
WordPress Meetup ཐིམ་ཕུག་འདི་ ཁེབ་ས་མེད་པར་ ཁས་བླངས་ཀྱི་ཐོག་ལས་ རྒྱལ་ཡོངས་དགའ་སྐྱིད་དཔལ་འཛོམས་ཀྱི་ཀ་ཆེན་སེམས་ཁར་བཞག་སྟེ་ ལམ་སྲོལ་དང་ རྒྱལ་ཡོངས་སྐད་ཡིག་ མི་ཉམས་རྒྱུན་སྐྱོང་འབད་ནི་ལུ་དམིགས་གཏད་བསྐྱེདཔ་ཨིན།
WordPress Meetup འདི་ མི་ངོམ་རང་རྐྱང་དང་ WordPress ལུ་དགའ་མི་ དེ་ལས་ རང་སོའི་ཡོན་ཏན་ བརྗེ་སོར་འབད་ནི་དང་ མི་གསརཔ་འཕྱེད་དེ་ མཐུན་ལམ་བཟོ་ནི་ལུ་ཕན་ཐོག་ཡོདཔ་ཨིན།
ཨྱོན་གྱིས་ ནང་འཁོད་དང་ རྒྱལ་སྤྱིའི་སྐད་ཡིག་གི་ཐོག་ལུ་ WordPress ནང་བྲི་མི་ཚུ་ལུ་གཙོ་བོ་སྟོན་ཏེ་ ལས་སྡེ་ཚུ་ ཡང་རྒྱས་གཏང་ནི་རྒྱབ་སྐྱོར་འབདཝ་མ་ཚད་ WordPress ནང་ལས་ག་ཅིག་རང་ལྷབ་ཅི་ག་ འབྲུག་པའི་མི་སྡེ་ཚུ་ལུ་ བརྗེ་སོར་འབདཝ་ཨིན།
WordPress གི་དུས་སྟོན་གྱི་ལས་རིམ་ WordPress སྐད་བསྒྱུར་གྱི་ཉིནམ་༤པ་དང་འབྲེལ་ ཨྱོན་གྱི་ WordPress Meetup Thimphu ཐེངས་དང་པའམ་འདི་ མཐར་འཁྱོལ་ཅན་སོང་ཡོདཔ་ཨིན།
ཨྱོན་གྱི་རྒྱལ་ཡོངས་སྐད་ཡིག་གོང་འཕེལ་གཏང་ཐབས་ལུ་ WordPress འདི་ རྫོང་ཁ་ནང་བྲི་མི་དང་ ཡོངས་འབྲེལ་གྱི་ཐོག་ལས་ རྫོང་ཁའི་གནས་ཚུལ་ དེ་ལས་ གཞུང་གི་ཡོངས་འབྲེལ་ཚུ་ནང་ ལག་ལེན་འཐབ་སྟེ་ འབྲུག་པའི་ WordPress འདི་ མ་འོང་བུ་བརྒྱུད་ཚུ་ལུ་སྤྲོད་ནིའི་ འགན་ཁུར་གཙོ་བོ་ཅིག་འབག་སྟེ་ཡོདཔ་ཨིན།
༡ རྫོང་ཁའི་ WordPress Core སྐད་བསྒྱུར་འབད་ཚར་ཏེ་ཡོདཔ།
༢ WordPress Core སྐད་བསྒྱུར་གྱི་དོན་ལུ་ སྐ་བསྒྱུར་གསརཔ་གི་ཕན་འདེབས་འབད་ནི།
༣ Global WordPress སྐད་བསྒྱུར་ཉིནམ་༤པའི་ དངོས་མཐོང་ ༼ https://wptranslationday.org/༽ ནང་བཅའ་མར་ གཏོགས་ཡོདཔ།
༤ ཕྱི་རྒྱལ་ཁབ་ངགཞན་མིའི་ wordpress མཁས་མཆོག་ཚུ་ http://wpbhutan.slack.com. ནང་གདན་འདྲེན་ཞུ་ཡོདཔ།
༥ WordPress Meetup ཐིམ་ཕུག་གི་འཐུས་མི་ཚུ་ WordPress དང་འབྲེལ་བའི་དོན་ཚན་ཐོག་ལུ་གྲོས་བསྡུར་འབད་ནིའི་དང་ འབྲུག་པའི་ WordPress ལག་ལེན་འཐབ་མི་ཚུ་དང་ wordpress.org ནང་འཐུས་མི་གསརཔ་ཚུ་ འཛུལ་ཞུགས་འབད་ནིའི་ནང་ རྒྱབ་སྐྱོར་འབད་ནིའི་དོན་ལུ་ http://wpbhutan.slack.com ནང་ གདན་འདྲེན་ཞུ་ཡོདཔ།
༦ དེ་ནང་སྐུ་མགྲོན་སྦེ་ རྫོང་ཁག་གོང་འཕེལ་ལྷན་ཚོགས་ཀྱི་བརྡ་དོན་དང་འཕྲུལ་རིག་འགོ་དཔོན་གོངམ་ བསྟན་འཛིན་རྣམ་རྒྱལ་འབྱོན་ཡདོཔ་ཨིན།
༧ ལས་རིམ་འགོ་འདྲེན་འཐབ་སའི་ས་ཁོངས་འདི་ བཟེས་སྒོ་ཡང་ལེགས་ལོམ་འཐོབ་ས་ Ariya Hotel ནང་ཨིན།
༨ མཐུན་ལམ་བཟོ་ནིའི་དོན་ལུ་ འཐུས་མི་ངོ་སྤྲོད་འབད་ནི།
༩ Global WordPress སྐད་བསྒྱུར་ཉིནམ་༤པའི་ སྡེ་ཚན་གྱི་གྲངས་སུ་འཛུལ་ནི།
༡༠ ལས་རིམ་འདི་ ServMask Inc གི་གྲོགས་རམ་དང་ རྫོང་ཁག་གོང་འཕེལ་ལྷན་ཚོགས་ཀྱི་ སྐད་ཡིག་མཁས་མཆོག་ཚུ་གིས་རྒྱབ་སྐྱོར་འབད་ཡོདཔ།
ལཱ་དང་བྱ་བ་ག་ཅི་རང་འབད་རུང་ གྲུབ་འབྲས་ལེགས་ཤོམ་འོང་དགོ་པ་ཅིན་ ད་ལྟོ་ལས་རང་ རྩ་འགེངས་ཏེ་ ལེགས་ཤོམ་སྦེ་འབད་དགོཔ་ཨིན།
ལཱ་ག་ཅིག་རང་འབད་རུང་ སྐལ་བ་ཅན་གྱི་མ་གཏོགས་རེ་བ་ཅན་གྱི་མི་འཐོབ་ཟེར་དོ་བཟུམ་ སྐལ་བ་ཡོད་པའི་ཁར་ ལཱ་ཚུ་ བརྩོན་འགྲུས་བསྐྱེད་དེ་འབད་བ་ཅིན་ ལཱ་ག་ཅི་རང་འབད་རུང་མཐར་མ་ཕྱིན་པའི་དཔེ་མི་སྲིད། དེ་འབདཝ་ལས་ ཨྱོན་གྱི་ བརྩོན་འགྲུས་དང་བསྟུན་ཁོང་གི་མ་འོངས་པའི་ Word Press གི་འཆར་གཞི་ཚུ་འོག་ལུ་འཁོད་དེ་ཡོདཔ་ཨིན།
དེ་ཡང་ ཨྱོན་གྱི་ སྐད་ཡིག་གི་མཐོ་རིམ་སློབ་གྲྭ་དང་གཙུག་སྡེ་ཚུ་ནང་འགྱོ་སྟེ་ WordPress ལག་ལེན་འཐབ་ཐོག་ལས་ རྫོང་ཁའི ནང་བྲི་ཐངས་ཀྱི་སྐོར་ལས་སྟོན་བྱིན་ནི་ཨིན།
དེ་མ་ཚད་ འབྲུག་པའི་ WordPressལག་ལེན་འཐབ་མི་ཚུ་འཛོམས་ཏེ་ འབུག་པའི་ལམ་སྲོལ་དང་ མཛེས་ཆའི་སྐོར་ལས་ གཞན་མི་རྒྱལ་ཁབ་ནང་ གསལ་སྟོན་འབད་ནིའི་དོན་ལུ་ གྲོས་བསྡུར་གོ་འདྲེན་འཐབ་ནི་དང་ WordPress གི་ལས་རིམ་གཙོ་ཅན་ཅིག་ཨིན་མི་ Introduction to Open Source ཟེར་མི་འདི་ འགོ་འདྲེན་འཐབ་ནིའི་ལཱ་འབད་བའི་བསྒང་རང་ཡོདཔ་ཨིན།
དེ་ལས་ འབྲུག་མི་ཚུ་ WordPress ལག་ལེན་འཐབ་ནིའི་ནང་རྒྱབ་སྐྱར་འབད་དེ་ ཡར་རྒྱས་གཏང་ཞིནམ་ལས་ མི་ཚེ་སྐྱོང་ཚུགས་ནིའི་དོན་ལུ་ WordPress གི་མཁས་མཆོག་ཚུ་གདན་འདྲེན་ཞུ་སྟེ་ Wordcamp གི་དོན་ལུ་ Wordcamp ཐིམ་ཕུག་འགོ་འདྲེན་འཐབ་ནི་ཨིན།
WordCamp Asia འདི་ཡང་ སྤྱི་ལོ་༢༠༢༠ལུ་འགོ་འདྲེན་འཐབ་ནི་ཨིནམ་ལས་ WordCamp Asia ནང་ལས་ འགོ་འདྲེན་པ་༤༡ཡོད་པའི་གྲལ་ཁར་ཚུད་དེ་ཡོདཔ་ཨིན།
མཇུག་རང་ ཁྱོད་ར་ཚུ་ WordPress ལུ་དགའ་མི་ཅིག་ཨིན་པ་ཅིན་ ད་ལྟོ་ རང་ལུ་ རང་དབང་ཡོདཔ་་ལས་ རང་སོའི་མི་ཚེ་མཐར་འཁྱོལ་ཅན་བཟོ་ནིའི་གོ་སྐབས་ཡོདཔ་ཨིན།
WordProof Timestamp is a new free plugin that bridges the WordPress and blockchain communities in an approachable, user-friendly way. It gives users the ability to timestamp their posts and pages to demonstrate transparency and claim ownership of content.
WordProof works with any EOSIO blockchain to create the timestamp and provides a custom certificate link with a frontend pop-up to display it.
The plugin adds a “View the blockchain certificate” link under each post or page, which pops up the URL, title, content, timestamp information, and will soon also display revisions. Users will be able to browse through different timestamps to view the changes.
WordProof Timestamp was first created by Van Ons, a WordPress agency based in Amsterdam. This is the same company that recently open sourced Laraberg, a package that allows developers building applications with Laravel to integrate the Gutenberg editor. Development has now been passed on to a dedicated WordProof team that is funded by Tenos.
“I have been working and investing with blockchain as a hobby since 2013,” Van Ons founder Sebastiaan van der Lans said. “After we built the WP GDPR Compliance plugin and started working Laraberg, I am trying to work more and more on open source projects. From my point of view, WordPress + blockchain could not only democratize publishing but also doing business as a whole.”
Van der Lans said he expects that any type of publishing website or any site with “Terms & Conditions” pages can benefit from timestamping. It’s especially useful in mediating claims of plagiarism and content theft. WordProof has no transaction costs and is almost instant (0.5s). Van der Lans said it was important for this solution to have no transaction fees, since it is fundamental to proving the author’s identity and the integrity of the content.
Right now the plugin offers the ability to timestamp an entire article, including the title and content. Block level time-stamping is not on the roadmap, but the team is open to adding it in the future. They are currently looking into time-stamping media files and legal documents.
After launching the plugin in beta, a team of 60 testers, from both the WordPress and EOS.IO blockchain communities, gave feedback that led to the creation of a WordProof Wizard to make it easier for users to set up the required accounts.
“Our testers’ main concern: it was too difficult to create an account on the blockchain and download and set-up a blockchain wallet afterwards,” Van Ons head of product Jelle van der Schoot said. “Therefore, we invested a lot of time into improving the UI/UX of the entire process (downloading the plugin, creating a blockchain account, downloading and setting up a wallet, timestamping).”
The wizard supports both Telos and EOS and guides users through the process of setting up an account directly inside the WordPress dashboard. The process takes approximately five minutes.
“We believe the WordProof Wizard can have a massive impact on the onboarding of new users to the blockchain in general, but more specifically to the Telos and EOS blockchains,” van der Schoot said.
Timestamping posts is by no means a new idea. There are already several free WordPress plugins that have similar functionality and work with various blockchain technology, such as WP Blockchain, STAMPD.IO, Po.et, and Mingrana WP to Blockchain. WordProof is different from many of them in that it doesn’t use a centralized middle layer.
The team behind the plugin is working on more tools that bring blockchain features to WordPress and will soon be adding cryptographically secured decentralized WordPress hosting to the WordProof lineup. van der Lans will also be speaking about more of the benefits of timestamping content with the blockchain at WordCamp Europe in his presentation titled “From WordPress to blockchain: the future is 100% open source.”
After four years of publishing on Medium, FreeCodeCamp is migrating all of its articles to its own open source publishing platform, a modified version of Ghost. The platform allows approved authors to cross-post their blog articles on the new FreeCodeCamp News site for free, without any ads.
“Medium was a great place to publish because it helped a lot of people discover your articles. But the community has outgrown Medium,” FreeCodeCamp founder Quincy Larson said.
“Medium has shifted to a paywall model where they mainly recommend paywalled articles, then encourage visitors to pay to get around their paywall.
“At the same time, not much of the traffic to Medium articles comes from Medium itself. Most of it comes from Google and social media.”
In the detailed public announcement on the FreeCodeCamp forums, Larson said he noticed his articles started to get less distribution after he decided that putting them behind a paywall would not be compatible with the mission of his organization.
“As of 2019, Medium won’t give you much ‘distribution’ within their platform unless you’re willing to put your articles to be behind their paywall,” Larson said. “At the same time, if you do put your article behind their paywall, you’re limiting your readership to just the people who have the resources to pay. This is at odds with the goals of the freeCodeCamp community. We want to make these learning resources as widely available as possible.”
In an email to blog authors who had published on FreeCodeCamp’s Medium publication, Larson elaborated on more serious concerns that he had with the platform’s approach to his organization. Oleg Isonen, one of the blog authors, published the contents of the email, which was later deleted at Larson’s request.
“But over the past year Medium had become more aggressive toward us,” Larson said. “They have pressured us to put our articles behind their paywalls. We refused. So they tried to buy us. (Which makes no sense. We’re a public charity.) We refused. Then they started threatening us with a lawyer.”
Many of those who read the email encouraged Larson to write a follow-up article, as Medium’s tactics towards publishers are a matter of legitimate public concern, both to those who use the platform and readers who support the company through subscriptions.
Larson responded, confirming that he sent the email but that he wanted to move on from the situation.
This email was intended only for Oleg and a few of our other authors. I have messaged him asking to delete it. We are focused on the future and want to move on from this.
— Quincy Larson (@ossia) May 31, 2019
The new freeCodeCamp News site has migrated the organization’s 5,000 articles that were previously posted on Medium. The articles will still be available on Medium, but from now on freeCodeCamp plans to publish on its own platform. The site promises users full control, better analytics, AMP support, and a better reader experience that doesn’t require people to sign in or pay to read articles.
“I’m optimistic that all of us in the developer community can start our own blogs on the open web, then use community tools like freeCodeCamp News to raise awareness of them,” Larson said.
Medium abruptly changed course in 2017 to become a publisher of subscription-based content, scrapping the ad-driven revenue model without notifying publishers ahead of time. Many publications that had invested heavily in building a following on Medium were forced to leave after discovering that the company did not have their best interests in mind. Medium’s new paywalled content model, which CEO Ev Williams claims is “a different, bolder approach” targeted at fixing what is broken with media, could not sustain publishers who were convinced to join the platform in its earlier days.
FreeCodeCamp joins a wave of other publications that are moving back to WordPress and other open source platforms. This trend is set to continue as Medium’s obtrusive popups and poor reader experience drive readers away from the content hosted there. Publishers who are in it for the long haul, those who value stability and full control of their content, will return to the open web.
In this episode, John James Jacoby and I discuss Panethon’s acquisition of StagingPilot and why regression visual testing will likely become a standard feature across managed WordPress hosts if it’s not already. I rant about the size of text on so many sites being too large and having to shrink the site down to 80-90% in order for it to be manageable. We celebrate WordPress’ 16th birthday, discuss what happens to unloved patches, and GitHub’s Sponsors tool.Stories Discussed:
Next Episode: Wednesday, June 5th 3:00 P.M. Eastern
Subscribe to WordPress Weekly via Itunes
Subscribe to WordPress Weekly via RSS
Subscribe to WordPress Weekly via Stitcher Radio
Subscribe to WordPress Weekly via Google Play
Listen To Episode #354:
Automattic is working on a new experimental Full Site Editing plugin aimed at enhancing the page creation workflow in the block editor. Starting a new page from scratch may be overwhelming for those who don’t have a vision for how to tastefully put blocks together to lay out the page. This is a problem that this experimental plugin may be able to solve.
Full Site Editing currently provides three custom blocks for post content, templates, and a blog posts listing. The Blog Posts Listing block expands upon core’s Latest Posts block to include an excerpt and meta information.
The plugin is available in the WordPress Plugin Directory, although it is somewhat difficult to find when searching in the admin plugin installer. The most recent 0.1.1 version of the plugin seems to be broken, but if you roll back to the initial release, you can see some of the page template experiments. After activating the plugin, navigate to Pages » Add New and a new modal with a template selector should pop up.
The templates come pre-filled with demo content and images, so the user doesn’t have to think about how to configure the blocks to match the demo.
The functionality in Full Site Editing is being developed for use on WordPress.com. It makes sense for a network that regularly onboards new bloggers and site owners. It is in the company’s best interest to deliver the fastest possible site creation experience, rather than have new users get frustrated and confused about how to get started.
A template selector for creating new pages could also be useful for the broader WordPress community. Plugin developer Jeffrey Carandang tested Full Site Editing and suggested that it might be useful to add this functionality to Gutenberg with custom hooks so that developers can add their own custom templates. This would make guiding users through the new theme setup process much easier for theme shops.
Automattic has a label on the Calypso repository dedicated to categorizing issues in the full site editing project. The plugin is going to be enabled on a small set of sites for initial testing. There are quite a few issues that still need to be ironed out, including things like preventing users from deleting the header and footer and finalizing the theme used with the plugin. At the moment, the plugin seems to be tailored specifically to the Twenty Nineteen theme and the pre-filled templates do not look as good when used with other themes.
The functionality included in the Full Site Editing plugin may also be coming to Jetpack. Automattic’s developers are currently researching the best way to include it, since so far it has been developed as a separate plugin and not geared towards becoming a Jetpack module.
Full Site Editing is not recommended for use in production, as it’s still under active development. The plugin’s details explicitly state that it is “only designed to work on the WordPress.com environment and could break after an update.” Check it out if you want to explore some exciting new possibilities for how the block editor can work together with themes to make page creation more approachable for users.
Panethon, a managed host geared towards Drupal and WordPress sites, has acquired StagingPilot. Financial details of the deal were not disclosed. Nathan Tyler, founder of StagingPilot, and his brother Phil Tyler will be brought into the company.
StagingPilot is a four year old company that runs a barrage of visual regression tests on WordPress sites before they’re automatically updated.
StagingPilot creates a copy of the site and places it into a staging environment. The service then conducts a number of tests that include, checking for visual errors, a white screen of death, and elements on a page disappearing. A number of snapshots are created along with a detailed report on the errors that are discovered.
Josh Koenig, Co-Founder and Head of Product at Pantheon, says the acquisition puts the company within reach of the ‘Holy Grail’ of WebOps.
“Once you have a hundred sites (or heck, even twenty), the grind of keeping up with routine updates can be daunting,” Koenig said. “Our existing WebOps tools let our customers automate a lot of that maintenance, but building and managing that automation is on them. We want our users to automate their operations, not operate their automation.”
Pantheon plans to integrate StagingPilot into its offerings in three phases. First, it will migrate StagingPilot’s technology into its existing managed updates feature and extend it beyond WordPress to support Drupal.
Then, the company plans to fully integrate the service with its organizational features providing substantial benefits to agency partners or those who manage many sites.
The third phase looks to take advantage of services such as Google’s applied learning machines to create AI-driven testing.
Out-of-the box, WordPress only updates minor versions automatically and leaves major updates, plugins, and themes up to the user. One of the most common fears of enabling auto-updates is having something on the site break.
Often, the process of testing updates is left up to the consultant or whoever manages the site. Depending on the size or number of sites being managed, it can become a major time suck.
Hosting companies like Pantheon with StagingPilot, LiquidWeb, and others are easing the fear of auto updates in general and saving people a lot of time by using automatic visual regression testing.
To learn more about StagingPilot and to see Nathan demo the service in-person, check out this episode of WPshowandtell hosted by Jason Tucker.
Gutenberg 5.8 was released today with three new features and more than three dozen enhancements, documentation improvements, and bug fixes.
This release gives users the ability to change the text color in the Heading block. The same color options available in the paragraph and button blocks are now available in the heading block.
A recent release of the EditorsKit plugin (version 1.5) added this feature and the plugin’s author had tracked nearly two dozen issues and discussions where users have asked for text highlighting or similar features.
“We really need this for all block controls (lists, paragraphs etc),” Ben Gillbanks commented on the relevant GitHub issue. “Anything that can be used on a group block with a colored background could cause readability issues and so the text color will need to be changeable.” Gutenberg designer Mark Uraine said that adding text color options to all the text blocks is the next step following this update.
Gutenberg 5.8 adds support for reordering gallery images using a simple arrow control to move selections forwards or backwards. This isn’t an ideal interaction but Gutenberg phase 2 lead Riad Benguella said the team is exploring adding drag and drop support.
Benguella shared a video that demonstrates these two new features:
This release introduces an initial version of the new widgets screen. You can check it out in the admin under the Gutenberg » Widgets (beta) menu. It’s currently just a proof of concept and has quite a few bugs but gives a preview of how the the widget management screen is shaping up. Benguella said users can currently edit/update widget areas using any available block. The proof of concept implementation in the plugin allows the team to continue polishing the UI and fix bugs in future releases.
The editor is also making progress on mobile, adding quotes and video to the available blocks, rich captions for the image block, and fixes for several critical bugs.
The editor has also recaptured some of its performance gains that were lost in version 5.7, according to recent performance benchmarks.
We’ve had some commenters on previous posts who said they are confused about the difference between WordPress’ core editor and the Gutenberg plugin. The plugin is where active development gets committed. All the new features are put into the plugin first so they can be tested before being rolled into an official WordPress release later down the road. If you want to get access to all the latest features Gutenberg has to offer, install the plugin and you will be able to try it before it lands in core.
Google is enabling mobile-first indexing (crawling sites with a mobile user-agent) by default for new domains as of July 1, 2019. These are sites Google defines as “previously unknown to Google Search.”
Mobile searches are the primary way that users engage with the search engine for the past few years, which caused Google to begin prodding website owners to make their content more mobile friendly. Google’s indexing and ranking systems originally used the desktop version of a page’s content, but this can cause problems when desktop and mobile sites contain different versions of content.
Mobile-indexing is not default for all websites yet, but Google started rolling it out more widely in 2018. Google evaluates older websites for readiness based on a variety of factors:
For existing websites we determine their readiness for mobile-first indexing based on parity of content (including text, images, videos, links), structured data, and other meta-data (for example, titles and descriptions, robots meta tags). We recommend double-checking these factors when a website is launched or significantly redesigned.
It’s important to note that there is no separate “mobile-first index.” Google still references a unified index for serving search results. The difference is in whether a page is crawled by a desktop or mobile user-agent.
Prior to responsive web design becoming the industry standard, having a separate mobile site was a common practice. Google is actively discouraging this approach now (although still supporting it), as it often causes confusion for users and search engines alike.
WordPress sites using a responsive theme shouldn’t have any issues with mobile indexing as long as they are not farming out their mobile sites to a separate domain. A responsive theme is usually enough to make a site compatible with this method of crawling.
Website owners can check to see how their sites are being crawled by clicking on the “URL Inspection” tab inside the Google Search Console.
Webmasters of older sites will get a notification from the Search Console when their sites are moved over to mobile-first indexing.
After successfully ramping up mobile-first indexing from a small-scale experiment a few years ago, making it the default for new domains should be a good test for evaluating how aggressively it can be rolled out in the future.
I grew up in the 90s and 2000s which was a weird time for technology. Part of me remembers carrying around a case of cassette tapes and the sound of dial-up occasionally screaming from the living room. The other half recalls hacking into my dad’s email from the shared family computer for the first time when I was ten. His passwords were never very hard to guess.
In 2004 or 2005, I started taking more of an interest in the Internet. I wanted to start a blog maybe, but I wasn’t sure what a blog even was. WordPress was one of the first things I stumbled on, but it was still an infant compared to what it’s evolved into and I had no idea how it worked. Was WordPress a blogging website? Was it a thing I could build my own site with? How did it work?
I just wanted somewhere to be myself online and WordPress intimidated me. So I dabbled, but I didn’t stay. Myspace and Tumblr would teach me to use HTML, because after all, I just wanted my own place to write online.Finding My Way Back to WordPress
Eventually, my writing career led me back to WordPress. I was in college, studying English Literature when the opportunity for a Marketing Internship opened up. Around 2011, Chartwells Higher Education, a food service company for college campuses, had launched a huge multi-site network of university dining websites.
Their largest initiative that year was to drive website traffic.
Mine was to keep the students from kicking us off campus because of how much everyone hated Campus Dining.
So I started a blog.
“The Inside Scoop” gave students the perspective of a student who works for campus dining. Both goals were met and I fell in love with the idea of using writing to address business problems. Even more exciting, I finally understood WordPress. Although by then, nearly ten years had passed and WordPress had completely changed.Life Changed (a LOT), but WordPress Was Always There
At the same time throughout college, I went through a major transition from life as an extremely active athlete to someone with mobility problems. I broke my back, went through everything you can think of to fix it, and ended up with a permanent disability.
Thankfully, I knew by then how to work on a computer in an environment that didn’t necessarily require me to be in an office. It took a few years of adjustment, but eventually, I ended up working for a WordPress-based marketing agency remotely from an RV, which I took anywhere I felt like going.
For a few years, I became a professional tourist.
I’d wake up, get some work done, then adventure all day.
By the time I was done, I could tour any city in a single day and still keep up with content writing. But writing content was all I did. Naturally, I still wanted my own website to write on, but all I had was Tumblr. How to actually set up a WordPress site from start to finish was a mystery to me.
My partner at the agency was supposed to build the site for me, but it never happened. By the time my RV broke down in Rhode Island, 3,500 miles from my hometown, I had lost my chance to build a true travel blog and #vanlife became way too much of a fad to interest me anymore.Learning to Build Websites with WordPress
My next step was to build my own website. I probably owe a lot of my “self-taught” skills to websites like WP Beginner and WPCrafter, but I really can’t remember how I learned other than trying and failing many times.
After a few YouTube videos, I dove in and built the worst website that you could possibly imagine. It was atrocious, but I liked it enough, so I started writing on TaylorElizabethRose.com and building more websites.Returning to a Burning California
My next few years were spent spinning my wheels on the East Coast and essentially failing at everything I tried. So I made a plan to move back to California and start my own WordPress-based business. By then I had learned a lot about website management, or so I thought.
The first version of TaylordInk.com was launched in May of 2017 before I made the trip back to California in September.
As we drove into Napa Valley, I noticed how dry it looked and said,“This is a fire hazard.” There were no fire breaks and I had seen what the terrain looks like before it burns when my house burned in San Diego in 2007. Napa and Santa Rosa were primed for flames.
But, how many times in one person’s life can their house burn down?
It was less than two weeks later when the Tubbs Fire came through and burned my entire future. The man I’d been with for two years ended up abandoning me. My business equipment was gone. Any professional clothes I may have had were incinerated. All I had were my dogs and my 2013 MacBook Pro, which happened to be with me at the time.Nothing but a Laptop
Between October and December 2017, I couldn’t tell you much about what I did or what happened except that I ended up back in my hometown: San Diego. It was a blur of loneliness, depression, and complete failure. Finally, sometime mid-December, I logged into my personal website.
May as well start with my own identity.
It was hacked… and gone. I failed to update while I was swimming in my own sorrow.
Luckily, my friend from my agency days actually had a backup of the original site. So I salvaged the posts from his files and started rebuilding. I really didn’t get very far until much later in 2019. I just kept designing and redesigning the same pages over and over again.
On the second or third time I logged in after the fire, I saw the WordCamp San Diego information on the Dashboard and bought a ticket before I could change my mind about going.Discovering the WordPress Community
WordCamp San Diego didn’t happen until months later, but it was the next time I really did anything productive in my life. It was kind of my last-ditch attempt to start a WordPress business or any business at all.
I didn’t know what to expect. I didn’t know who I would meet, or how (or if) I would fit in. I certainly never expected to find a community with open arms.
A weight was lifted from my shoulders almost immediately. Where had all these nerds been my whole life? These were my people!
There’s a comfort that comes from fitting into a community and finding your people.
Being in the company of like-minded people makes the future less bleak. I had hope again for the first time since the fire stole that from me.
At some point during that WordCamp, a girl named Sochi found out that I was a content writer. She dragged me by the hand to meet Matt Cromwell at the Give booth. It was extremely intimidating because the entire Give Team was sitting there staring at me. I didn’t know it then, but I was meeting my own future coworkers.
Give was hiring a content writer! In fact, they were close to hiring someone else, but I was intrigued. So I inquired the next day and disrupted Matt’s hiring process a bit.
The next week, I joined Team Give.
Over the next year, I spoke at 4 WordCamps and attended 6 or 7 total.
Working at Impress.org and participating in WordCamps has been incredible and I’ve learned more about WordPress over the past year than in all the years before. I don’t think I would have succeeded as well with my own WordPress-based marketing agency without the community.
More importantly, I wouldn’t have made it through some of the hardest times in my life without WordPress. It was there when I needed to work remotely and it was there when I needed a helping hand to lift me back out of tragedy.