For my own development environment I figured CodePen wouldn’t be around to hold my hand developing in an actual environment, and didn’t use it for actual development for that reason. I’m running Ubuntu and just fired up an Apache server, used a text editor for all of my projects, visiting my FreeCodeCamp folder at 127.0.0.1/fcc/whateverprojectImdoing.html
I’m at the part right now where literally ALL I have to do is add sound to Simon, and everything’s golden. However, since I’ve started moving projects from text files into CodePen, I’ve noticed some weird behaviors.
I’ll point to an example here:
Has anyone else run into this? Or any other little kinks that CodePen throws at ya that you wouldn’t otherwise normally deal with?
You need to check the browser console. (ctrl-shft-j) There are several errors.
Going from local to codepen can be a pain. Codepen doesn’t let you link to local files so lines like …
<link rel="stylesheet" type="text/css" href="ttt.css"></link>
… are going to fail.
All of the CSS has to be in codepen’s own CSS window. You shouldn’t have any
script elements to get external CSS or JS files. And things should be loaded over https. And there is no need for
As far as resizing the button font, your CSS has:
You don’t specify a unit for your font size. When I change it to:
it seems to work.
If you want it to be exactly the same and use CodePen, then you need to use Projects, but you only get one on the free tier (I assume this is where CP is going to make most of its money going forward - even on the lowest paid level you only get ten projects). Otherwise, it’s as @ksjazzguitar says. Pens are sketches really, they aren’t designed for building full apps in & are fairly constrained.
Thanks guys! I’m cleaning up my projects now.