One of the things that prevents CV's and resumes from going away is how big companies hire. When CodePen hired programmers we looked at some of our favourite people on CodePen. When I worked at a large company recruiters brought people into the company and passed them off to the technical people to interview. Until we've overcome the problem with non technical people approving engineers we won't be able to fully replace the resume or CV.

We don't have any planned features at the moment. But officially supported JavaScript is very high on our list. We'd love to hear what you have in mind.

We haven't really considered that. Have you seen all the other layouts we offer for a Pen? Check out this screenshot .

We sure hope so. We're just getting started with CodePen Projects. What you see today is the foundation of Projects. We may not create an official CodePen CLI but if we created an API making an open source CLI would be very simple.

I'll give my input only on what insights we've gleaned while running CodePen. Two things. Find the minimum amount of process that works to coordinate your team and formalize it. We were pretty ad hoc when we added people to the team and it felt inefficient. We've come up with processes we follow when doing our work and it's helped how we communicate. Everyone understands how we decide what to do and when we do it. Add the fewest number of steps you can. Team happiness is still the most important thing. There are great ideas and there are great ideas the team can accomplish. We hold back on adding features until we feel we can give them the love they deserve. For example we've wanted an API for a long time, so have our users but we've never had the time to support it. Five years in we can finally start discussing adding an API to CodePen.

Build something small with a backend language. When you succeed with that move onto a bigger challenge. Repeat until you're a full back end developer. If you code a frontend project you have the skills for many backend languages. I recommend Ruby. It's a sweet language.

There are some amazing examples being created on CodePen as projects. Look at the examples here http://codepen.io/projects/ . You'll find lots of inspiration. I would take these steps: Come up with an idea you want to see as a website. Anything that you'll be happy working on. Write out the steps it'll take you to build the site with as much detail as possible. Work on every step until you're satisfied it's complete. Enjoy your success!

CodePen was supposed to be a weekend project. Chris always wanted something like Jsfiddle/JsBin but with a simple way to see what everyone else was doing. He was making lots of examples on his site CSS-Tricks and he wanted something better. He asked Tim and I to help him work on it. We did and we never stopped working on it because it kept getting more interesting. Five years in and our weekend project isn't done. Quite a bit of scope creep if you ask me.

There isn't an algorithm that decides what preprocessors make it into CodePen (I wish there was!). It's based on popularity and how many requests we get for the tech. If we get enough requests for a preprocessor over Twitter/Facebook and email we'll add it to our list. Lots of times the team itself wants a preprocessor to be added. Every vote counts so we'd love to hear from you if you see something you'd like us to add.

We've just started discussing an API. We've held back on supporting an API for a long time because we wanted to continue building out CodePen itself. Now that we've built a lot of our favorite features supporting an API is very high on the list. I'd love to have it for some open source ideas I have. Really hoping we can start work on it soon.