Skip to main content
This guide walks you through adding new solutions (products/services) to the solutions catalog displayed on your site.

Overview

Solutions are defined in data/solutions.tsx and automatically appear in:
  • Solutions dropdown menu in navigation
  • Solutions listing page
  • Individual solution detail pages

Solution Data Structure

Each solution follows the Service interface defined in types.ts:
types.ts

Step-by-Step: Adding a New Solution

1

Open data/solutions.tsx

This file contains the solutionsData array with all solutions
2

Import an icon from Lucide

Choose an appropriate icon from Lucide React:
data/solutions.tsx
3

Add your solution object to the array

Copy an existing solution and modify it:
data/solutions.tsx
4

Update data/data.tsx for detailed pages

If you want detailed solution pages with subtitles and multiple images, also add to siteContent.solutions.items:
data/data.tsx

Field Descriptions

Required Fields

Detail Page Fields

The subtitle1 and subtitle2 fields are only needed if you’re adding the solution to data.tsx for detailed pages.

Example: Complete Solution

Here’s a complete example from the existing codebase:
data/solutions.tsx

Choosing the Right Icon

Testing Your New Solution

1

Save your changes

Ensure both data/solutions.tsx and data/data.tsx are saved
2

Start development server

3

Check navigation menu

Your new solution should appear in the “Soluciones” dropdown
4

Test the detail page

Navigate to /soluciones/your-slug to see the full page

Image Guidelines

Use high-quality images (1200px width minimum) and optimize them before uploading. WebP format is recommended for best performance.

Image Requirements

  • Format: WebP, JPG, or PNG
  • Dimensions: Minimum 1200x800px
  • Size: Under 200KB after optimization
  • Hosting: Use a CDN for better performance

Where to Host Images

  1. WordPress Media Library (if using WordPress CMS)
  2. Unsplash (for placeholder/demo images)
  3. Your own CDN (recommended for production)

Writing Effective Descriptions

Short Description (Card View)

  • Keep it under 20 words
  • Focus on the key benefit
  • Use action-oriented language
Good: “Barrera superior contra oxígeno. Extiende vida útil hasta 40%.” Bad: “Este es un producto muy bueno que tiene muchas características interesantes.”

Long Description (Detail Page)

  • 2-3 paragraphs
  • Start with the main value proposition
  • Include technical details
  • Mention certifications or standards
  • End with use cases or applications

Features List

  • 3-5 bullet points
  • Lead with benefits, not just features
  • Use specific numbers when possible
  • Include certifications (FDA, ASTM, etc.)
Good: “Biodegradación completa en 90-180 días” Bad: “Es biodegradable”

Common Mistakes to Avoid

  • Don’t forget to add the icon import at the top of the file
  • Don’t use duplicate id or slug values
  • Don’t use relative image paths (always use full URLs)
  • Don’t skip the menuTitle field (it’s used in navigation)

Next Steps

After adding your solution:
  1. Test the solution detail page thoroughly
  2. Check mobile responsiveness
  3. Verify all images load correctly
  4. Update your sitemap if using one
  5. Deploy your changes to production