Organizing a #WordCamp is not an easy task. But it turns out that organizing a bilingual WordCamp is even more difficult. 🤯

On paper, it should be easier (bigger pool of everything), but in reality, you hit quite a few problems. 😬

Check out the whole article in the comment 👇

Read the whole article on 
https://maciekpalmowski.dev/blog/from-polish-only-to-bilingual-lessons-from-wordcamp-gdynia/

Bilingual WordCamp Challenges

Second article about connecting CMSs with #Astro.

This time it's time for @thekeystatic 🚀 

Quick bits:
🔑 Keystatic is totally distraction-free
📄 It creates Markdocs or markdown files (no API needed)

Check the comment for more 👇 

Keystatic x Astro

https://maciekpalmowski.dev/blog/keystatic-x-astro/

Connecting Flotiq CMS with Astro

I promised to write tutorials about connecting CMSs with #Astro.

Here's the first one about @flotiq 🚀 

Quick bits:
🌐 Content Layer API is amazingly flexible
⚡ Flotiq is powerful
🔗 You can connect a CMS just by updating the content config
Check the comment for more 👇 

Flotiq CMS x Astro

https://maciekpalmowski.dev/blog/flotiq-cms-astro

There are still 12 hours to vote on my talk about "How we closed almost 1K plugins in a month" to bring me on stage in Florence 🍕 

To be selected, my talk needs to be in the top 8 - to vote, you need to leave a 👍 reaction at https://github.com/Schroedinger-Hat/osday/issues/577

Thanks 🙏 

#osday

I need your help to speak at the Open Source Day conference. 🆘 

My talk about "How we closed almost 1K plugins in a month" was selected for voting. 🗳️

To be selected, my talk needs to be in the top 8 - to vote, you need to leave a 👍 reaction at https://github.com/Schroedinger-Hat/osday/issues/577

#osday

I just got back from #JSWorld, and I'm already packing my @kinsta SWAG for @PHPUKConference.

I can't wait for the conference, as there are some really amazing talks. Here are my top 5 talks that I want to attend 🧵

#phpuk23

Asynchronous PHP with React PHP by @marcelpociot

I heard a bit about ReactPHP but never dived more into this. And Marcel is a really amazing speaker, so I think it's a perfect combo.

GraphQL, REST, or RPC? Making the choice! by @akrabat

I'm always keen to listen to all the arguments in this discussion.

What is Performance Driven Development and why aren't you doing it? by @SecondeJ

I see the word "performance," and I'm in. Really.

Bye bye drupalisms! Propelling Drupal into a modern PHP ecosystem by @mupsigraphy

I really like the way that CMSs like Drupal, Craft, and Statamic went - they are standing on the shoulders of a framework. Can't wait to listen to how Drupal did it.

Continuous Integration: Tips & Tricks by @dr4goonis

I'm a total sucker for CI and I always want to learn a bit more about it. That's why I can't wait to listen to this talk.

Also, there are some cool coffee places nearby, so I can't wait to test some of them ☕

PHP UK 2023

As you probably know already - I'm doing two newsletters. One for #WordPress - called @WP_Owls and a more private one (https://www.getrevue.co/profile/palmiak_fp).

While it's not an easy task, it's totally worth it. Here is why 🧵 

📫 You can share your thoughts
It's a great way to share your weekly findings, what you are excited about etc.

This helps your readers to know you better.

📭 You can learn to write better
If you are not a native speaker, writing in English will just help you write better. Because you have to send each week an email you will be motivated to write. At some point you it will just become more and more natural.

🔎 You will learn how to find content
WP Owls helped me to learn how to find information about WP. Now I have places to look for it.

When I started my private newsletter, finding info was easier, becasue I knew better how search for it.

🧑‍🤝‍🧑 It helps to connect with others
Thanks to WP Owls I met a lot of people. Such connection should never be underestimated because even if don't see sense in some of them it may change at some point.

💰 It can help you find a job
Those connections I mentioned above helped me in getting my #DevRel jobs. Knowing people and knowing how to find informations can be crutial in your job. 

🕺 It's fun
I love sharing whatever I learned. So having a newsletter is one of the best way to do so. So, if feel the simillar urge to share your findings... well, just start doing it.

And what about you? Do you have a newsletter (don't forget to share the url here)? Did it helped you in your career?

Also, don't forget to subscribe to https://www.getrevue.co/profile/palmiak_fp

Why it's a good idea to start a newsletter

I mentioned yesterday that I just discovered that @Cloudflare has an API for deploying pages. I tested it and it works nicely and it's very easy to connect with @BuddyGit.

A thread 🧵 

The first step is to go to the Cloudflare dashboard > pages and add a new page. Select "Create a project" and pick the Wrangler CLI guide. 

That way we'll achieve the Account_ID.

Next, go to profile/API Tokens to get the API Token.

Store both as variables in Buddy:

Now, normally build your app. In my case, it's a typical @astrodotbuild blog. No magic here.

Time to deploy. We have to add a node action first and install an additional package first - the Wrangler CLI.

Next, we have to create and deploy our app.

That's why I'm using project create and publish comments. 

I'm setting branches manually here, but passing the actual branch variable would be a better idea.

After the initial deployment is complete - you should remove the first line

And that's it :) We are deploying our site to Cloudflare.

One thing to remember. It takes time from the initial deployment to the site to start working (in my case it was 5 minutes).

Also, visit https://developers.cloudflare.com/workers/wrangler/commands/#pages for more info :)

Using Cloudflare CLI & Buddy

Last week, during the @buddygit webinar, I had the pleasure to talk with @filiptepper about Site reliability engineering. What is it, who needs it, and what do we need to learn to work in SRE?

A thread 🧵 


What is SRE? This term was created by Google, but based on a company we work at it sometimes means something different.

In general, it's a culture of collaboration between software engineers and system operators to bring scalable and reliable software.

The term that really interested me was "blameless debrief" - it means that if an accident occurs the team concentrates on the accident itself rather than on the person who caused it. 

It's all about the WHY it happened rather than WHO caused this.

Who should implement SRE? Everyone.

The good news is that you don't the team for that to start with. You can start just by implementing the methodology. When you'll grow, you'll see more and more benefits of it.

One of the key aspects of SRE is observability. It's key to have your application provide you constantly with all the data that can help you fix bugs if an error occurs or even prevent them.

What do you need to know to become a Site Reliability Engineer? A bit of everything from the software engineering and system ops worlds. 

If you want to watch the whole webinar head to https://www.youtube.com/watch?v=R33UoHWVUqo

Also, don't forget to subscribe to our YouTube channel to get informed about all the upcoming webinars.

SRE Webinar with Filip Tepper

Last week I was doing a @buddygit #webinar about headless #WordPress together with @fran_the_dev. 

It was really amazing to learn so much about @nextjs, here are some key takeaways. 

A thread 🧵 

I loved Fran's origin story. He's a living proof that if you want to learn programming you can do it. It's not easy, it requires time and heavy work, but it's doable for everyone.

Adding a GraphQL endpoint is as easy as airfrying a pizza - all thanks to the @wpgraphql plugin by @jasonbahl. Just install it and you are ready to go.

Using GraphQL is also simple thanks to the IDE build-in.

Connecting NextJS with the API is also simple. We used the Apollo Client, but using Fetch is also OK.

Grabbing the data is as simple as coping queries from the WP admin panel. The cool part about GraphQL is the fact it's up to you which data to fetch.

It's also quite simple to deploy a @nextjs app using @BuddyGit. In this case we deployed it to @Netlify.

If you want to watch the whole webinar head to https://www.youtube.com/watch?v=N6KOkZmpgdE

Also, don't forget to subscribe our YouTube channel to get informed about all the upcoming webinars.