Project notes

Anonymous project notes from real delivery work.

Selected examples are written to show the type of technical work delivered without exposing client names, domains, internal systems or private implementation details.

Selected delivery notes

Practical work across inherited systems, migrations and support-heavy websites.

B2C comparison platform

Technology comparison platform

Built and hardened a public comparison platform for technology products, with a dedicated crawler, structured catalogue pages and a separate management environment.

Situation

The project needed to move from an internal data-collection and staging setup into a stable public-facing comparison service, with safer affiliate routing, environment separation and ongoing catalogue refreshes.

Technical work

Built and operated a crawler pipeline for public product, offer, price and image data.
Normalised catalogue data around stable identifiers where available and structured public search, product, category and brand pages.
Added canonical product/category URLs, hierarchical taxonomy handling and price-history display.
Routed outbound merchant links through opaque tokens instead of exposing raw offer identifiers.
Separated public production, staging and internal management environments.
Added SEO controls, sitemap filtering, noindex handling and scheduled refresh/publishing jobs.
Built management views for catalogue review, crawler status, statistics and editorial publishing.

Outcome

Reduced operational risk, improved maintainability and made support easier through clearer crawler, publishing, management and deployment workflows.

B2B industrial technology website

Complex CMS migration

Migration support for a complex site into a structured WordPress build with editable content models, form handling and visual QA.

Situation

The agency needed senior technical execution for a migration involving institutional pages, service pages, editorial content, investor-related pages and light e-commerce areas. The visible scope required careful handling of redirects, forms, content models and visual parity.

Technical work

Assessed migration feasibility and defined a WordPress architecture around custom templates and editable content models.
Rebuilt global theme structure, including header, footer, navigation, wrappers, typography and shared layout rules.
Implemented priority pages, news content, forms, redirects and SEO preparation.
Prepared shop-related structure and validated priority routes, mobile navigation, search and visual parity.
Built visual QA workflows comparing live and staging screenshots across desktop and mobile.

Outcome

Created a clearer and more maintainable WordPress foundation, improved the QA process and reduced migration risk before go-live.

Public-sector data platform operator

Ticketing module for legacy platforms

Delivered and documented a secure ticketing module integrated into two existing legacy PHP platforms.

Situation

Two established internal web platforms needed platform-specific technical work within existing authentication, runtime and database constraints. The work required a controlled handover path rather than a greenfield rebuild.

Technical work

Created technical specifications for a ticketing module covering architecture, data model, workflows, roles, notifications, attachments and deployment assumptions.
Delivered platform-specific ticketing packages for two existing environments.
Integrated the ticketing module with existing authentication/session handling.
Prepared SQL foundations, deployment runbooks, smoke tests, packaging checklists, test cases and role-based manuals.
Specified security controls including prepared statements, output escaping, CSRF protection, upload validation, role-based access and protected routes.

Outcome

Created a clearer deployment and handover path, improved maintainability and made future support easier through runbooks, smoke checks, test documentation and manuals.

Retail e-commerce operation

Catalogue sync and server support

Maintained and supported a server-side product import workflow connecting XML catalogue data with a WooCommerce store.

Situation

The server contained operational PHP scripts for importing XML product data, updating product records, managing stock visibility and logging errors or removals. The workflow touched production catalogue data, scheduled jobs and database operations.

Technical work

Maintained PHP scripts for XML processing, product import and stock synchronisation.
Processed zipped/XML product feed files into database-backed import structures.
Updated WooCommerce products, variants, prices, stock quantities and catalogue visibility.
Used scheduled jobs for import processing, product synchronisation, log cleanup and maintenance.
Kept operational logs for product updates, removals, insertion errors and slow queries.

Outcome

Stabilised catalogue operations and made ongoing support easier through clearer processing, retention, scheduling and failure visibility.

Production web hosting environment

Managed LAMP server environment

Configured and supported a LAMP-based production server environment for PHP and WordPress sites, with AlmaLinux, Virtualmin, backups and ongoing operational maintenance.

Situation

The hosted sites needed more controlled server ownership than basic shared hosting could provide. The work required Linux stack configuration, hosting panel setup, backup routines, SSL/DNS handling and practical troubleshooting around production PHP websites.

Technical work

Configured AlmaLinux-based LAMP server environments for PHP web applications and WordPress/WooCommerce sites.
Set up Virtualmin/Webmin hosting management for domains, sites and server-side administration.
Managed Apache/PHP, MySQL/MariaDB, permissions, logs, cron jobs and production troubleshooting.
Handled SSL, DNS and migration-related server tasks where required by the hosted sites.
Configured backup routines and recovery-oriented maintenance for website files and databases.
Reviewed PHP versions, execution limits, cache and database settings to keep the production stack supportable.

Outcome

Created a more controlled production hosting baseline, reduced operational risk around server ownership and made ongoing support easier through clearer backups, permissions, configuration and troubleshooting paths.

Real-estate advisory business

Property-sector website support

Senior technical support for a public property-sector website with listing discovery, bilingual content and enquiry flows.

Situation

The public site showed a media-rich property platform with listings, filtering, contact forms and multiple lead-capture paths. There is not enough evidence to state what was broken before the work started.

Technical work

Implemented or maintained a CMS-based public website.
Built or supported custom front-end behaviour and property listing flows.
Supported listing detail pages, pagination, filtering and enquiry paths.
Supported bilingual content structure and third-party media embeds.

Outcome

Improved maintainability, clearer enquiry paths and easier ongoing support for a public property-sector website.

Children's education activity provider

Public education booking website

Technical support for a public-facing education activity website with content pages, product-style listings, booking touchpoints, forms and account access.

Situation

The public website combined educational content, programme information, activity listings, enquiry paths, account access and privacy-sensitive forms. The visible scope suggests that stability, content accuracy, form handling and ongoing support were important.

Technical work

Supported public content areas for schools, holiday activities and activity listings.
Supported product-style listing behaviour, detail pages and public enquiry paths.
Maintained form and account-related areas that collect or expose personal data.
Inference: reviewed operational risk around booking, catalogue and form behaviour where needed.

Outcome

Helped keep a public booking and information website easier to support, with clearer attention on operational risk, user-facing forms, account flows and ongoing content maintenance.

B2B technical services organisation

Corporate website support

Technical support for a public corporate website with multiple service areas, sector pages, portfolio content, news and contact workflows.

Situation

The public website presented a broad corporate content structure with service areas, portfolio entries, news, certifications and contact flows. That type of site needs reliable maintenance, content-led updates and production support.

Technical work

Maintained public-facing corporate website structure across services, sectors, portfolio and news pages.
Supported contact form functionality and public enquiry flow.
Supported content areas for certifications, portfolio items and news.
Inference: production support, hosting or security review should only be claimed if confirmed by private notes.

Outcome

Made the website easier to operate, support and maintain for ongoing production use, without exposing the client or internal implementation details.

These notes are intentionally anonymised because much of this work is delivered for agencies, inherited systems and production environments where client names, domains, internal workflows, credentials, infrastructure details and private implementation context should remain protected.

Start here

Need a senior technical partner?

Send the current situation, constraints and deadline. We will reply with the fastest sensible next step.

Send a technical brief hello@starter.pt