CodePen is pretty amazing if you understand how to use it. Most campers don’t. This may be in part because FreeCodeCamp doesn’t require anyone to watch a video on how to set up CodePen and some people won’t do stuff unless you make them.
When creating a pen, there are options. The best option is to create from a template but to do that, you need a template first. This is one of those techniques that is helpful for people who will use CodePen more than once. That should be you. So, without further ado, let’s build a simple FreeCodeCamp template.
Create a new pen. It will come up blank, with three editing panels and a white area. If you don’t like where the editing panels are, you can click on the [Change View] button at the top and choose from left-side, top, or right-side display. If you don’t like the colors, you can change that, too, but we’ll get to that in a moment.
Click the [Settings] button. This will pop up an screen with settings for this particular pen. It will look like thisNotice on the left it has Pen Settings and some tabs. We’ll go through them one by one.
Next comes the CSS tab. This screen allows you use LESS or Sass or other CSS preprocessors or link to external CSS files. You can load Bootstrap here using the button at the bottom that says [Quick-add]. If you want to use the version of Bootstrap that has been covered in FCC lessons, use Version 3. Do that now, actually, as that’s something useful for the template.
The next tab is about CodePen itself, not about your project code.You can choose the way your code displays. I use spaces, set to two. Uncheck Save automatically. Since you’re doing this over the internet, it’s a bandwidth hog to save after every keystroke or few. AutoUpdate is also a bad idea. Make sure neither is checked.
Now let’s turn our attention to the part on the right. Give the pen a good title Template or myTemplate or something similar. Describe it in the box for that. And, most importantly, toggle ti to Template status. Now click the green [Save & Close] button and voila! you have a template.
I promised we’d get back to changing the color of our editor. Now is the time. Click on your avatar picture on the top right corner and choose Settings from the drop-down menu. You’ll get a screen similar to this one.Colors are on the top left, either individual settings or themes. There are other settings too. Once you have it how you like it, the save button is on the top right.
This is my current setup. You will notice the vim key bindings. Since I tend to run Linux Mint (that’s all my laptop has at the moment and my desktop dual-boots to Win10), I tend to use vim quite often to edit files. When I develop anything locally, it tends to be in vim (unless it’s Python, in which case I use idle).
This is not a public-service announcement for vim. I’m not recruiting anyone. Use what works for you, but here’s why I use vim.
- Most Linux or unix-flavored boxes have it. I can also get it for Windows.
- It works when I install it, without a lengthy setup procedure.
- I can add features as I need them, optionally saving to a local config file.
- I’m accustomed to it. My fingers remember how to do common tasks.
If I’m on an unfamiliar Windows machine, I’ll use NotePad. Because I know how. Same with TextEdit on a Mac. It’s not that I’m averse to other editors. People joke about not knowing how to exit vim, but honestly, any program without a menu has that issue. It’s not a vim issue, per se.
It’s all about the learning curve. CodePen has one and so does vim. CodePen has a shallower one. By all means, learn it. It makes it much easier to share your code. If you are going to do serious work in Linux, you should probably learn enough vim to edit basic files. But don’t use it for your everyday editor unless or until it becomes familiar enough that you catch yourself using vim commands in non-vim spaces.