Ever open a file in VSCode and get annoyed by all of its highlights of your code, or find that it has mis-identified the content? Sometimes it’s just easier to turn off the language highlighting in Visual Studio Code. It’s simple:
It’s nice that you can customize the 4xx/5xx error blade files if they’re published in Laravel - I like that. But what if you want to access the current user - or even use your standard layout - for the not found / 404 error? It’s actually quite easy. Let’s check it out.
What do you do when your website looks great to you - but others say the text is hard to read and the image is grainy? Well, because of this specific reason, I use two monitors always - one with a higher resolution and one with less. So, as it turns out, there’s a way to make both resolutions - and people - happy. Let’s see how.
The specific challenge is to sort users in a Laravel Nova application by their role. For this specific example, though, we have a number of assumptions. Although this article solves this very specific problem, you can probably extend it to apply to other custom data challenges in Nova. Let’s check it out.
When running a geo-location query out to Google, we found a zip code that wasn’t found. The city/state was found in Google maps, but if you searched just the zip code, no results turned up. This is the fix I came up with.
I just moved from Jekyll and Github pages to Hugo and Netlify. And made a new design. It’s overall much better - but with a few things to note.
Sometimes you may want to make a completely empty git branch in your repo. This is how you can do it.
Whether you’re on the side that just landed the big deal - or you’re the business eager to get your project launched - you need to know what a statement of work is. Let’s talk about contracts and statements of work for developers.
Gathering requirements for a new project can get unwieldy and unorganized pretty easily. It’s easy to get lost or go down a deep rabbit hole. You may be getting excited about the new project’s technical challenges or be blindly following the client’s explanation and description. How do you know you’ve covered everything, though? What if you’re missing vital points?
Creating a requirements document for a project can seem daunting. Where do I start? What sections are required? How do I capture everything and keep scope limited?