[Feature] [Portfolio] Add portfolio landing page experience and improve site configuration

[Gautam25Raj]

Summary

This PR introduces a dedicated portfolio landing page experience with new marketing sections, improved site configuration, theme management support, and enhanced portfolio platform content.

The update also expands public-facing documentation, SEO improvements, and portfolio metadata handling.

Features

Landing Page Experience

• Added new landing page components:
  • FeatureGridSection
  • HeroPortfolio
  • HeroSection
  • HowItWorksSection
  • MarqueeSection
  • Navigation
  • SeoSection
  • TemplateLinksSection
• Improved portfolio product presentation and discoverability
• Enhanced overall marketing and onboarding experience

Theme Management

• Added ThemeProvider support
• Established shared theme handling across the application
• Improved consistency for theme-aware components

Portfolio Store Enhancements

• Added analytics data support to the portfolio store
• Added user information handling within portfolio state management
• Improved portfolio data availability across workflows

Improvements

Site Configuration

• Expanded site configuration with additional links
• Improved navigation and platform discoverability
• Enhanced SEO descriptions and metadata

Content & Documentation

• Added updated pricing information to public markdown content
• Expanded public feature descriptions
• Improved product communication and documentation quality

Template Experience

• Added template preview images
• Improved visual representation of available templates
• Enhanced template browsing and discovery workflows

User Experience

Marketing & SEO

• Improved landing page structure and content hierarchy
• Enhanced search engine optimization metadata
• Improved product positioning and discoverability

Visual Enhancements

• Added richer template previews
• Improved landing page presentation and storytelling
• Enhanced user onboarding experience

Notes

• No breaking changes
• Focused on portfolio growth, discoverability, SEO, and landing page experience

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🧪 Tests (adding or updating tests)

Checklist

• I have read the CONTRIBUTING.md document.
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.