Skip to content
View ljclark's full-sized avatar
1 follower · 1 following

Achievements

Achievement: Pair ExtraordinaireAchievement: Pull Sharkx3Achievement: Quickdraw

Achievements

Achievement: Pair ExtraordinaireAchievement: Pull Sharkx3Achievement: Quickdraw

Block or report ljclark

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
ljclark/README.md

👋

Hey. I'm Lewis - a front end developer based in North Yorkshire, UK.

I'm a self taught front end developer with a background in technical marketing and integrated solutions, working across a number of leading agencies throughout the UK and Canada.

Current Roles 👨‍💻

Stack 🤓

My tools of choice are currently:

Shopify, Craft CMS, Alpine.js, Digital Ocean, Ploi and Valet

Experience 🤘

I've worked with blue chip enterprises all the way through to local, single person businesses across a variety of different industries. I love the variety that these offer and finding solutions that offer both a functional solution to both merchants and customers, backed by a solid design and user experience.

Pinned Loading

  1. ronswansum ronswansum Public

    A lorem ipsum generator inspired by the legendary Ron Swanson from Parks & Recreation. Add a little humour to your lorem ipsum in your design projects. Built on Craft CMS with Tailwind & Sprig (HTMX).

    CSS 2 1

  2. craft-colour-swatches craft-colour-swatches Public

    Forked from craftpulse/craft-colour-swatches

    Let clients choose from a predefined set of colours.

    PHP

  3. Resource Data ID mapping and replace... Resource Data ID mapping and replacement
    1 
    // This function will:
    2 
    // 1. create a lookup/dictionary from Staging Resource and Prod Resource
    3 
    // 2. find the matching entity based on the handle (this must be present in both datasets)
    4 
    // 3. grab the ID from the staging resource and create a new column in Prod Resource with it's value
    5 
    // This then gives us the staging and prod ID's in the same sheet, identified by handle.