Themeisle Blog

Themeisle | https://themeisle.com | REMOTE | Full-time, Contract | Backend, Frontend, Full Stack, and DevOps engineers We're a global company, for now mostly building some of the most popular themes & plugins for WordPress. We see this as a great entry-point to get in touch directly with small agency owners and make sure we build the right tools for them in the next 10 years. At the same time we're also a media company, running various blogs, which helps us to educate our customers, attract new ones and build cool free tools like : https://themeisle.com/logo-maker/. We're looking for experienced developers ( full-time or contract) that enjoys ownership, likes to have freedom over what they build & value excellence. More details here: https://careers.vertistudio.com/jobs or email me at hi @ ionutn.com

https://www.reddit.com/r/degoogle/comments/yl9hno/best_gmail_alternati… https://www.positional.com/blog/alternative-search-engines https://themeisle.com/blog/gmail-alternatives/

I disagree from a conceptual/philosophical perspective (broken accessibility is bad delivery, not just occasional mishap/edge case for some small set of customer) and from a practical perspective. It's not an occasional customer, it's a huge chunk of the marketplace. Here are some stats: https://themeisle.com/blog/web-accessibility-statistics/ I don't think software shop owners that are ignorant of or ignoring accessibility are necessarily jerks. Before being informed, they are transgressive to good sense; after being informed, immoral. How they act directly towards someone is what defines whether they are a jerk or not, and that, in my mind, is not really connected to the conversation.

Gmail (the free consumer facing one) can configure custom domains right? Does that not address your need? https://themeisle.com/blog/use-gmail-with-your-own-domain-name/#free

Use Mailstore and download it all to a local drive. Make sure you have local backups and you run Mailstore regularly. https://www.mailstore.com/en/products/mailstore-home/ It works surprisingly well. To guard your email address, setup your own domain, create an email address and connect it to gmail. https://themeisle.com/blog/use-gmail-with-your-own-domain-name/ It's smart to do it. Google can close your account at any minute. It belongs to them.

I wouldn't dismiss the domain brokers ideas but wouldn't be too caught up with them, either, unless you have tried it yourself first. There are domain auction sites. You might start there with a handful and see how it goes. I get solicited all the time for domain names that brokers think I might be interested in due to my industry. But I've already established a reputation with the brands/URLs I have, so I'm not in the market. The people to solicit are those who are formulating a brand strategy but need a catchy name. Those people are hard to find You would have to know what people are thinking when they are CONSIDERING starting a brand. Here's a place to get started with a few and see how it goes: https://themeisle.com/blog/premium-domain-name-for-sale/

Sure, you can do that - https://themeisle.com/blog/local-wordpress-development-using-docker/ You can also install something like WAMP on Windows and develop locally http://www.wampserver.com As for the benefit... you can switch i.e. PHP version by simply editing the docker-compose.yml file - this is everything but simple on most Linux distributions.

I was bored so decided to dig a little as it interested me. I found [1] to be helpful explanation of services Hostinger offers. I would gather from [2] OP's business ought to have had access to on demand back up -- as such I would have the expectation that a large streamlined hosting service, would be able to provide a given number of back ups exported to any practical external storage area via a variety of protocols -- however again, as a non customer I have no idea if what I would expect is the actual situation. However running 70 sites without any form of external just in case back up, or monitoring them daily / closely, was an accident waiting to happen -- accidents happen and the prominent OVHcloud incident in 21 should still linger in those tasked to secure their web based company's future. Other technical fubar accidents can also happen like ssd raid dying catastrophically. I myself was amused when my own data in server was updated and data migrated to a ssd raid 5 ... it failed weeks later - expectation was it would be at most a partial loss, however hard the system admin tried over a couple days, little could be recovered, just a couple of gigs of old images - thankfully all but the newest files were backed up so it was easiest to just let it go and start from scratch. Ssds are IMO very unforgiving but in time they will get better in regard to failure detection. [1] https://themeisle.com/blog/hostinger-pricing/ [2]…

>For my purposes (set up a simple blog and get it running), I truly don't think that I need, or should, have to learn the ins and outs of the tech stack. Well ... if you want a simple blog, then you can setup an account with the 10million hosted blogging services that are out there. And if you want a wordpress blog, then you can set up an account with wordpress.com, or get a hosted solution with Wordpress/LAMP already preinstalled, or get a VM with Wordpress pre-configured (e.g. Vagrant Box with Wordpress: https://themeisle.com/blog/vagrant-wordpress/). What you wanted however, was a locally hosted Wordpress (why?) that you installed and configured (on Windows no less). That's fine, but Wordpress requires PHP, and requires a web-server, and requires a database - so you'll have to be able to understand what all those pieces are in order to install and configure them together. >In fact I chose WordPress specifically _because_ I wanted it to abstract most of the implementation details away from me. Which it does. There is a difference between being a user of Wordpress and installing and administrating Wordpress. For the former, understanding the tech stack is not required. The UI is meant to be used by non-tech savvy people. For the latter, yeah, you need to be familiar with the tech stack. That you're not, and you had some trouble installing it, that's not the fault of Wordpress.

Related: https://gist.github.com/joymon/89aeb18bef588895426b46a54e2ba970 https://themeisle.com/blog/free-zapier-alternatives/ https://github.com/triggerdotdev/trigger.dev/blob/main/README.md https://automatisch.io/ https://github.com/activepieces/activepieces https://news.ycombinator.com/item?id=34723989

https://themeisle.com/blog/css-in-wordpress/ https://developer.mozilla.org/en-US/docs/Learn/CSS https://www.w3schools.com/css/ https://30-seconds.github.io/30-seconds-of-css/ https://tympanus.net/codrops/css_reference/