At the current time, the company mostly works with Shopify projects. Some of their clients work on a retainer model and some would want a custom new Shopify theme. For those projects, usually we get a design and work on top of that, aiming pixel perfection (also minding responsiveness). We also worked a lot with the Shopify ecosystem (Shopify Functions, Shopify Custom Apps, Shopify Scripts, Shopify Web Pixels, Shopify API's [Admin GraphQL, Storefront GraphQl, AJAX API and so much more]). The company owns a base theme for new stores which was built using TailwindCSS and Vue.js. I did help while maintaining it actively from creating unstyled common components to updating dependencies and refactoring the code. We would then work on this theme to provide the desired style and functionalities for each client. We also did work with some other clients with non-Shopify platforms such as: Wordpress, Next.js on top of the Vercel infrastructure + Sanity CMS. Their Wordpress projects did use Gutenberg blocks and their Next.js projects were up-to-date to the version 14 (at the time). The projects here are indeed challenging because all the clients want their website to be flawless, competitive and all their designs make heavy use of animations and transitions. The team is also really helpful and expert in WEB development which is really exciting

Our team managed to build a lot of B2C e-commerce for our clients using Shopify or Wordpress as the main platform. Our main goal was to deliver a responsive website aiming for a Pixel Perfect design. From project to project we've decided to go with different architectures and technologies as soon as Shopify released new features and integrations. We've had cases with a custom Webpack or Gulp.js scenario, where we would parse TS/JS and SCSS outside Shopify's Liquid's (Their template language) files. Projects using Vue in a "renderless" approach, where the components would have only the logic, but not visuals which came from Liquid, because of SEO issues while dealing with SPA-like applications at the time. Projects without a build process, just VanillaJS and CSS, to use the new Shopify/Github integration. Projects with Storybook for HTML / Liquid, where I wrote a public npm lib to deliver a "render" method https://npm.io/package/storybook-liquid-render. Used this also to "Unit Test" some HTML snippets with their respective TS/JS modules. After Shopify 2.0 features we've turned those into blocks or sections. I've also expanded a lot of Shopify's functionalities by using and creating apps to improve the store abilities. With custom apps, I did use React, Typescript, Styled Components and some other Shopify related libs like Polaris, to match Shopify's UX guidelines and fast to build UI's. I've also tested some Shopify themes that used React.js or Vue.js which had a different complexity than a regular SSG website, because we didn't have access to a backend to extend functionalities. You could only do that using apps or using Metafields, which lately has a better native support from Shopify. Shopify doesn't allow SSR at the time, only if you go headless. At least now we have Hydrogen and Oxygen for that.

At this company I mostly worked using Vue.js, Java on top of the Spring Boot framework and AEM as the CMS tool for authoring content. Also they had some projects which would rely on a PostgresDB instance, but usually we would just consume any or their microservices API from an API gateway and then deal with the result on the Frontend. Most of these projects having AEM to their core, would always have to load Vue.js code on the Frontend instead of dealing with SSR or SSG approaches (SSG was allowed on pages that didn't require Vue). Also they wanted to keep the project really simple so avoiding libraries in order to maintain performance as a priority. Since our main goal was to digitally transform our clients, usually our projects were tools to improve their workflow or automate the client's routines. That enhanced my critical thinking and problem solving skills. I remember attending meetings where you don't know what to code or if you need to code at all. Also from the coding perspective, this was one the best companies regarding code quality, code maintenance and tooling for that. They used SonarQube and some other CI/CD custom routines to ensure the code, dependencies were all good. Also here I did write a lot of unit tests for new components and updated former components when needed.

Started career, learned and became a full skilled developer, recommended for those seeking to learn and grow as a developer.