Technologies

Technology stack for digitizing your business

A modern, consolidated stack for ERP integration, B2B/B2C e-commerce, multisite and process automation. Cloud on Azure and AWS, Google and social APIs, AI as a development accelerator. 20+ years of experience, from BASIC on the Commodore 64 to today's cloud architectures: every technical choice serves the digitization of your company.

The CMS

Why OctoberCMS and not WordPress

WordPress was born as a blogging platform and evolved through plugins. Every update is a risk: incompatible plugins, conflicts, sites that break.

OctoberCMS is built on Laravel, the most widely used PHP framework in the world. This means solid architecture, modern code and core updates that never break your site. Business logic is all proprietary code: no conflicts, no downtime, no surprises.

CMS updates without incompatibility risks

Proprietary code: your site's logic is under your control

Intuitive backend: your team manages content without training

Native performance: no plugin overhead

The traditional approach (WordPress & similar)

Third-party plugins for every feature

Updates that break the site

Plugin conflicts, continuous patches

Performance degraded by plugin count

My approach (OctoberCMS + Laravel)

Custom-built business logic

Core updates without conflicts

Proprietary, maintainable and tested code

Optimal performance, no overhead

Current stack

The technologies I work with today

OctoberCMS

Enterprise CMS built on Laravel. Intuitive backend, plugin architecture, stable updates.

WordPress · PrestaShop

Extensive experience on WordPress (porting to OctoberCMS, custom plugins and themes) and PrestaShop for established e-commerce stores.

Laravel

The most widely-used PHP framework. Eloquent ORM, Artisan, queues, events, migrations.

PHP 8.x

Typed properties, enums, fibers. Modern, performant and maintainable code.

Node.js

Server-side JavaScript runtime for build tooling, automation scripts and integration micro-services.

MySQL · MariaDB · SQL Server

Relational databases for structured data. Optimized queries, custom indexes, profiling. Direct connections to SQL Server too, for Microsoft-based business systems.

Stored Procedures

DB-side logic for top performance: price-list sync, aggregate calculations and batch operations executed right where the data lives.

Tailwind CSS

Utility-first CSS. Responsive, consistent design that's fast to develop. No custom CSS to maintain.

Alpine.js · Vue · jQuery · Pjax

Lightweight frontend reactivity. Alpine.js right in the HTML, Vue for targeted SPAs, jQuery and Pjax for legacy projects or push-state navigation.

Swiper

Performant, accessible, touch-friendly sliders and galleries. A recurring building block for case studies, heroes and product catalogs.

Twig · Blade

Template engines that separate logic from presentation: Twig for OctoberCMS, Blade for Laravel. Automatic escaping and reusable components.

Composer · Git

PHP dependency management and code versioning. PSR-4 autoload, branches, merges, controlled deploys.

REST API · Cron jobs

Integrations with any system (ERP, PIM, CRM, cloud) and scheduled processes for sync, retry, batch import and automated mailing.

Nginx · Apache · SFTP/SSH

Virtual servers with dedicated resources, deploy over SSH/SFTP, SSL, virtual hosting. Nginx as default, Apache when the project calls for it.

Cloud · Microsoft Azure · AWS

Hosting and deploy on dedicated VPS or on the main cloud providers — Microsoft Azure and Amazon Web Services — picking the infrastructure that best fits the project and the customer's budget.

Google APIs

Integration of Google Maps, OAuth 2.0, Google Analytics 4, Search Console, Workspace, Drive, Calendar and YouTube Data API for authentication, geolocation, analytics and content.

Social: Meta · LinkedIn · YouTube

Automatic publishing and integration with Facebook, Instagram (Meta Graph API), LinkedIn API, YouTube Data API. RSS feeds, post scheduling, contact sync and ad campaigns.

Languages, formats and tools in the everyday toolkit

HTML5 CSS3 SCSS / Sass JavaScript ES6+ TypeScript-friendly JSON XML YAML CSV Bash · Shell scripting PowerShell Webpack Vite Laravel Mix npm Markdown OAuth 2.0 JWT Webhook cURL WP-CLI Artisan

Infrastructure: a dedicated environment for each project

Every web application is hosted on virtual servers with dedicated and isolated resources. No site shares resources with others: each project has its own environment with reserved CPU, RAM and storage. Primarily on Nginx for superior performance, with Apache available when the project requires it. Configuration on cloud services or dedicated servers, depending on the client's needs.

App 1 App 2 App 3

Each app in its own isolated environment

Developer Analysis Prompt AI Claude / OpenAI <code/> Developer Optimization and Debug <code/> Deploy The last word is always the developer's
AI-assisted development

AI as accelerator, experience as guarantee

I use artificial intelligence (Anthropic's Claude and OpenAI) as a development tool: code analysis, solution generation, debugging, optimization. AI accelerates the work, but it's 20+ years of experience in logic, data analysis and problem-solving that guarantees the quality of the result.

AI doesn't replace the developer: it amplifies the ability to solve complex problems in less time. The advantage for you is a project that arrives sooner, costs less and works better.

Analysis and debugging of complex code, including code written by others

Generation and review of architectural solutions

Performance and database query optimization

The developer decides, AI executes: never the other way around

Technical background

From the Commodore 64 to cloud architectures: 20+ years writing code

My technical roots go back to BASIC on the Commodore 64 and DOS: '80s and '90s of curiosity, taking software apart and putting it back together. From there I moved through the Microsoft enterprise stack (Classic ASP, ASP.NET, C#, Visual Basic, Access, SQL Server, IIS) and Office automation (VBA, Excel/Word/Access macros), all the way to today's modern open-source stack. This historical depth lets me talk to any system, debug legacy code, normalize data inherited from Excel files or aging business software, and migrate projects from Microsoft to open-source stacks without losing anything along the way.

1980s / 1990s — Roots

Commodore 64

The first BASIC listings, the blinking cursor. This is where it all started: the curiosity to understand how software really works.

1980s / 1990s — Roots

BASIC

The language of my first programs. The if/then/goto logic is the same logic I now use to model workflows and APIs.

1980s / 1990s — Roots

MS-DOS · batch

Command line, batch files, text-based automations. The roots of today's shell scripting and scheduled jobs.

2000s — Microsoft enterprise stack and Office automation

ASP Classic

'90s/2000s server-side web

ASP.NET / WebForms

Microsoft web framework

C# (.NET Framework)

Strongly-typed enterprise language

Visual Basic 6 · VB.NET

Desktop applications and business logic

Microsoft Access

Databases, queries, forms and reports

IIS

Windows enterprise web server

VBA · Macro Office

Excel, Word, Outlook, Access automation

Crystal Reports

Classic enterprise reporting

What does this mean for your project? When you come in with a business app built on Access, a VBA app that's been running for 15 years, a SQL Server database packed with stored-procedure logic, or a Classic ASP site nobody has touched in years — I can read it, understand it and bring it into the present. Migrations from Microsoft to open-source stacks, integration of heterogeneous systems, normalization of data inherited from Excel files or aging business software: a regular part of the work for anyone who really wants to upgrade the digitization of their company.

How I adapt and work with you

I adapt to your stack, not the other way around

I work as a freelance systems integrator and digital transformation consultant for Italian SMEs. I can join your team in any mode: turnkey project, body rental, support to in-house developers, code review and debugging on existing systems, training for your IT department.

Turnkey project

From requirements gathering to production deploy, step by step. Ongoing maintenance included.

Integration with your in-house team

I plug into existing teams — developers, IT managers, consultants — respecting processes and tooling already in place.

Code review · audit · debug

Inherited-code analysis, identification of performance, security and maintainability issues across any language.

Migration from legacy

Porting from WordPress, Magento, Joomla, Classic ASP, VB/Access desktop apps to a modern OctoberCMS/Laravel stack.

Pre-project consulting

Process analysis, stack selection, feasibility and budget assessment. Even just to figure out where to start.

Training for your team

Technical onboarding for in-house developers inheriting the project: documentation, training sessions, structured knowledge transfer.

Method

How I work on each project

01

Analysis

I study your processes, your ERP, your data. I identify what to automate and how to integrate systems.

02

Data normalization

I clean, restructure and normalize existing data. It's the starting point of every project: without clean data, no automation works.

03

Design

I define the architecture, integrations, data flow. Clear roadmap with milestones and timelines.

04

Development

I implement iteratively with frequent releases. Every feature is tested and validated before moving to the next.

05

Support

Monitoring, evolutionary maintenance, updates. The project grows with your business. Always.

Frequently asked questions

Answers to the technical questions we get asked most often.

Significa che la parte di amministrazione del sito (dove vengono inseriti i contenuti, gestiti i prodotti, configurate le regole di business) non è quella generica del CMS, ma viene sviluppata su misura per il flusso operativo del cliente. Il risultato è che chi usa il backend lavora più velocemente, fa meno errori, e non vede campi/menu inutili.
L'ERP gestisce i processi aziendali e amministrativi (ordini, magazzino, contabilità). Il PIM (Product Information Management) gestisce i dati di prodotto strutturati: schede multilingua, varianti, dataset tecnici. Il CRM gestisce la relazione commerciale (clienti, lead, opportunità). Spesso convivono nello stesso ecosistema e devono parlarsi: l'ERP è la fonte autorevole per anagrafiche e ordini, il PIM per le schede prodotto, il CRM per il funnel commerciale. Il nostro lavoro è far comunicare questi sistemi tra loro e con il sito.
Dipende dal dato. La disponibilità prodotti su un e-commerce B2B richiede real-time (webhook o polling rapido) per evitare oversell. Anagrafiche e listini che cambiano poco si sincronizzano in batch notturno, costa meno e non degrada il sistema. Il design corretto è quasi sempre ibrido: real-time sui dati che generano transazioni, batch sui dati anagrafici stabili.
Significa separare il backend (dove gli editor inseriscono contenuti) dal frontend (dove gli utenti vedono il sito). I contenuti vengono esposti via API e consumati da uno o più frontend (sito, app mobile, totem, kiosk). È utile quando lo stesso contenuto deve essere riusato su più canali, o quando il frontend ha esigenze di performance/SEO che un'architettura monolitica non garantisce.

Want to know how these technologies can help your business?

Let's talk with no obligation. Write and I'll reply.

Contact me

Fill in the form and I'll get back to you within 24 hours.