After reading this, checked my existing styling as processed through autoprefixer, found the vendor prefixes that had been added, and manually added them to my styling — so it now doesn’t require any additional tools for cross-browser compatibility.
I think in English when you write formal text you spell the numbers until 10. From there on you just write the number. #Laravel can help with that using the 'Number::spell' helper.
Is there a clickable, 2-level, responsive #hamburger#menu with minimal javascript, simple design, header and #navigation only, separate, free to use, #webdev up to date, modern browser.
Weekend discovery. An intermediate step in the RAG process is document chunking. Determining the appropriate chunk size can become a trial & error game. James Briggs does a great job of explaining how to use Semantic Chunking to get better results.
We're looking for a new Wordpress developer at CoffeeGeek. Global location isn't important, but your skills, reliability, discretion and availability are.
We are looking for someone who
has a deep and full understanding of the entire Wordpress infrastructure, back end, multi-site usage, and all the associated coding, css, custom theme work etc.
Has a good knowledge and understanding of Elementor Pro. We use Elementor Pro and several plug in packages on CoffeeGeek, and have need of some custom work within Elementor.
working, day to day knowledge and experience with Cpanel, PHP and all the normal server-side stuff that comes along with Wordpress and managing a busy website.
The usual "back end" knowledge an experience in website management, including CDNs, site security, back up, etc.
Some SEO experience, the more the better (especially staying on top of current trends
Some design experience. This isn't crucial, as we have a WP / Elementor designer separate from our WP Developer position. But you knowing some ins and outs of basic design is beneficial
VERY IMPORTANT: Good availability. I don't expect turnaround in an hour after I send a job request, but responses within 24hr, and normal availability for several hours per week for maintenance / bug chasing (and also larger blocks of time for bigger projects) is expected and required.
VERY IMPORTANT: you have the ability and desire to make sure all the work you do for us is fully tested and bug checked before signing off on the work. We do have a dev server to test things on, but we will rely on you to deliver finished, generally bug free work.
Ideally, you are creative on the technical side, are good at hunting down bugs, innovative with fixes, and know how to get the most out of a Wordpress environment.
you don't have to love coffee, but it would not hurt your application process! :)
I am willing to pay a monthly retainer plus a preferred hourly rate (billed once a month / when tasks are completed and signed off) or a slightly higher straight hourly rate (no retainer) for your work, payment competitive in the US and Canada marketplace.
If interested, please DM me here with your email address, and I will send you more details and ask for your CV, examples of your work, and your company website information.
I am based in Canada, PDT time, and most of the work contact times would be between 1pm and 10pm PDT time.
TIL that #Statamic ships with the 'isCpRoute()' function, which allowed me to make my code a little more compact. The function will check if the current route is a control panel route or not. Here's the old and new code. Feels refreshing 😁
Is there a course/website/book/etc. that would focus on teaching CSS how it can be used today?
I learned webdev back when we positioned elements with float and IE6 compatibility was a concern. I know fundamentals. I picked some new things along the way. But I wonder how you would work when you don't shoehorn new things into outdated models I grew up with.
Most Web-savvy folks know that Chrome’s lineage can be traced back to Safari (WebKit, etc.), and be traced further back to KDE’s Konquerer (KHTML, etc.).
Es scheint so, als müsste ich mich bei der TypeScript Entwicklung auf @deno_land konzentrieren. Sicherlich, noch mit JSR genutzt, mittlerweile ein Ersatz für @nodejs professionell.
»Deno 1.44 lernt den Umgang mit privaten npm-Registries:
Das Minor Release kann mit privaten npm-Registries sowie gRPC-Verbindungen umgehen und erhöht nochmals die Kompatibilität mit Node.js.«
I just published my first #Wix site today. I have limited experience with similar site builder services like Square Space and Weebly.
Is Wix typical of these kind of tools? I found it to be extremely difficult to use. On the plus side it almost gave me every ability I could produce as an actual developer... almost.
Less would have been more in the case of Wix. Just because you can stuff every possible feature into a Web based WYSIWYG builder doesn't mean you should.
It made it really hard to produce a simple and elegant site that is really what's needed by most people using such a service. If you truly have a need for the advanced features, trying to do those through multiple layers of nested menus is the worst way to do it. You might as well as hire a developer and do it the right way.
This site coulda been an email. Instead it was an insane toothpick tower that kept exploding on me b/c nothing played nicely with anything.
This short history of web development is a useful overview for me as I haven't kept close tabs on the field. The post seems to cover all the main frameworks but a notable omission is Tailwind CSS.