Here I've outlined my front-end development related skills as well as some design skills.
HTML
I am self-taught in HTML and am very comfortable building it from scratch.
I've got a good grasp of semantic HTML and am working on incorporating it into anything new I build. Time permitting, I plan on refactoring older sites I've made, to make use of it.
CSS
Self-taught with many a tutorial, I can write CSS from scratch or make use of frameworks like Foundation or Bootstrap. I can handily troubleshoot CSS and rarely encounter something broken in CSS that I can't fix with trial and error. It's my favorite part of frontend development, I think. I ❤️ it.
PHP
PHP is a language I'm comfortable looking at, and have a basic understanding of how it pulls together, but at this time cannot write it from scratch.
It is something I would like to learn more about with time.
Javascript
I'm learning JavaScript through sources like Codecademy (Pro Intensive - Build Front-End Web Apps), and Wes Bos' "JavaScript30" courses. I also have Wes' "Beginning JavaScript", "ES6 for Everyone", "React for Beginners" and "Learn Node" courses lined up to start on after I'm done with JavaScript30.
I have some basic concepts down, and am working on building up my skill level with JS.
jQuery
jQuery, like Javascript, is another language I'm just starting to learn. I learned just enough to get something working on a site I was building, and then decided I should probably learn Javascript more in depth first before going back to jQuery.
Adobe Suite
I'm comfortable using Adobe Photoshop, Illustrator and XD, the latter which was used to design the orange/pink 2019 design of this site.
Other Design Tools
I've looked into some alternatives to Adobe Illustrator and Photoshop in hopes in cutting out the monthly cost of Adobe CC. I've looked at Affinity Designer, and Sketch. I used Sketch for a previous design of this site. Affinity seems like it could be a good replacement for Adobe's products, but I'm not quite ready to give up AI and AP yet.
CMS
I have experience building sites with ExpressionEngine, CraftCMS, and WordPress.
Before joining Aquarian, I mostly made basic sites or blogs for myself or a handful of clients. I did one e-commerce site with ExpressionEngine 2 + Brilliant Retail, and one with WordPress + WooCommerce. I converted a couple of old WordPress blogs to CraftCMS, as well as from WordPress to ExpressionEngine. In 2021, I converted my business entity site from WordPress to ExpressionEngine.
At Aquarian, the biggest projects I've worked on there so far have been: an upgrade of EE5 to EE7 along with several add-ons, which included assessing which ones to keep, replace, or utilize core EE functions that hadn't been available before; a rescue of a WordPress site dying on PHP5.6 and converting it to Craft CMS with a brand new design provided by a colleague; an upgrade of EE3 to EE7; applying code (HTML, CSS) fixes for a site that was undergoing an accessibility audit in order to achieve WCAG2.1 certification; and working on a Craft CMS site with a wide range of complex field options (definitely not a "keep it simple" type of set up), which included adding content.
The day to day work with Aquarian consists of design updates as requested to various sites, CMS and add-on/plugin updates, and miscellaneous bug troubleshooting & resolution.
At my previous job, I built a prototype configuration generator using ExpressionEngine. Usually to produce these configurations, a user is required to copy a template into a text editor and use "find/replace" to get the needed data into the template. I thought it was time to move beyond this and build a tool that would do all of that for the user. Once I received approval from my manager to "build the tool", rather than reinvent the wheel, I chose to use ExpressionEngine. For the most part, the "text input" field had been sufficient for what I needed it to do, with one exception: IP addresses. There are no built-in field types for that, so I asked around the EECMS Slack community and got some pointers on how to go about building my own custom field type since I had not done it before, and created two new fields: one for IPV4 addressing and one for IPV6 addressing.
I completed enough of the prototype to demonstrate it to my coworkers, but unfortunately they didn't seem very receptive to it. I used it for a few of my own build instances, but not long after, the sub-groups in my department got split up to fall under different managers, and I was no longer part of the group who would've been using it.
Git
I learned Git as part of the Codecademy Pro Intensive courses I took for "Build Websites from Scratch" and "Build Front-end Web Apps". My GitHub repo is here: https://github.com/ttmwebdesign.
I've gotten more experience with it beyond a single user capacity since working with Aquarian where it is heavily utilized. Git stash has come in handy many times.