Vue.js logo

100 Days of Code, Day 2: Vue, me, and PHP

Day 2: December 25, 2017, Monday

Today’s Progress

I’m part of a Discord group of developers where people talk about coding things and collaborate on one another’s projects. I messaged asking if anyone needed help with JavaScript stuff, and one of the members responded with a project in PHP that he needs to convert to JS, using the Vue framework. I admittedly have almost no experience with that framework, but I decided I’d give it a shot anyway.

In the process of trying out Vue, I decided to also give JSFiddle (rather than CodePen) a try. I’ve seen it mentioned quite a bit, but never really used it. As it turns out, I much prefer it. Simpler, better interface, more responsive. As of now, it’ll be my default web-based editor when I’m working on little ideas that don’t warrant a full repo or directory on my local machine. I thought Emmet was one of CodePen’s killer features, but JSF features it, too. For how I use it, I just think CodePen is a bit much.

The PHP to JS conversion project is not the most complex thing I’ve ever seen, but it’s a solid intermediate level of coding. I’m familiar with PHP, but not intimately so, especially when it comes to PHP authentication. In order to work on this project, I cloned a Git repo to my machine and started digging through the code. I’ve cloned my own projects before, and a few repos owned by others, but those were usually for the purpose of having my own copy rather than modifying the code to check back in via pull request.

The experience of working with Vue has, so far, been a pleasure for me. I’ve had a minimal amount of experience working with React and Angular; it seems most comparable to Angular upon initial evaluation, and I just enjoy the process of writing with it better than React. That said, the extent of what I’ve written so far has strictly been limited to their demo examples (with some modifications for experimentation purposes). I’m especially interested in the Vue v-model attribute, which allows for two-way data binding similar to Angular. For example, you could have a text input field which is echoed elsewhere on the page as you type rather than upon pressing submit. Very cool.

When thinking about potentially having multiple clients with multiple WordPress installations to periodically update, I started thinking about how to unify them all on one page. This led me to the ManageWP product, which in turn led me to the WordPress CLI (Command Line Interface) utility. I haven’t spent much time with it, but I can envision incorporating it into my workflow in the near future.


I like Vue, so far, but I’ve got a lot of reading and practice to do before I incorporate it into a legit app. One step at a time. PS: Merry Christmas, if you’re into that!

Link(s) to Work

Still none yet, but soon.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s