We can create a nice representation of a file tree structure in markdown by combining characters in particular ways. This is sometimes useful when writing documentation where emphasizing file structure is important and we don't want to take screenshots. Screenshots just don't age well and are a hassle to update.
There are several ways we can name and organize new blog posts with Docusaurus. You can check all the Docusaurus blog post naming patterns on their documentation site. Though let's check some out in this post.
I really like using pull requests templates in Github. They're not only useful to collect vital information about a pull request, but also can serve as a checklist reminder for the contributor.
As you can see in the template, I love clean code so it serves to remind team members to use ESLint and Prettier, though recently I have started using lint-stagedand husky to handle that during a pre-commit hook.
I also think that pull request templates don't have to be boring. They should be fun! That's why I like to sprinkle mine with emojis. 💪😃
Fonts are an integral part of the coding experience. They can affect our productivity and enjoyment. An exceptional font will be easy on our eyes, not causing severe eyestrain. It will also make code easier to read and write. And lastly, a great font will help us identify purpose and distinguish letterforms quicker, all which leads to legibility and readability. Over the years I have experimented with various fonts for coding. From this, I have learned that monospace fonts that support ligatures can provide with an excellent coding experience.
Over the weekend I finally got a chance to try out Vite to create the React app initial boilerplate, bundler, and dev server. Previously, I had been using Create React App (CRA) (
npx create-react-app) and sometimes using it to deploy to Github pages.
Vite is framework agnostic and was created by the creator of Vue.js. As of now you can use Vite to scaffold not only React apps, but also Vue, Preact, Lit, Svelte, and good ol' vanilla JS. It currently uses Rollup.js as the bundler behind the scenes. This differs from CRA which uses Webpack.
In this post I'll do a quick comparison on how to start one up and deploy it (to Github Pages) with both CRA and Vite. With Vite is super easy, just as with CRA. Since I mostly use NPM I'll be using the NPM approach, but if you're using Yarn it'll be just as easy, you'll just have to do the equivalent commands.
I built my first iOS app 10 years ago in 2012 when the only way to build one was by collectively using Objective-C, the Storyboard visual builder, and UIKit. I never became an expert at it since it wasn't something I wanted to do professionally, after all web technologies had always been my bread and butter. However, I learned enough iOS development to get things working and eventually deploy an app to the AppStore. Since that time the ecosystem has changed for the better.
When I first tried to deploy Docusaurus 2 site to Github Pages following the Docusaurus Github Pages instructions it didn't quite work. It took a bit of trial and error, but I finally got it down.
I had been longing for a dedicated space on the web where I could document concepts related to software development. I wanted to effortlessly add technical notes that in the future could help me refresh what I had already learned. For a while I did this on my physical notebook and large whiteboard because it was convenient, until it wasn't. I love writing and highlighting physically, but it was less accessible and harder to find things as oppose if it were in digital format. I then stumbled across Docusaurus and that facilitated my objective.