Open-source eCommerce platform for C# and ASP.NET Core 10 with MongoDB. Build multi-store shops and multi-vendor marketplaces with B2B/B2C, REST API, plugins, Vue 3 and Docker.
GrandNode Repository Map
Root
GrandNode.slnx: main solution.global.json: pinned .NET SDK behavior.Directory.Packages.props: central NuGet package versions.src/Build: common MSBuild props and targets.src/Tests: test projects.src/Core: domain, data, infrastructure, mapping, shared kernel.src/Business: business interfaces and implementations.src/Web: public site, admin panels, shared web libraries, frontend app.src/Plugins: installable provider plugins and themes.src/Modules: application modules.src/Aspire: local orchestration and service defaults.
Technologies In Use
- .NET and ASP.NET Core.
- MongoDB through repository/data abstractions.
- Redis for caching and data protection integration.
- Custom mediator in
Grand.Mediatorfor commands, queries, and events, with a MediatR-compatible API (IRequest,IRequestHandler,INotification,INotificationHandler,IMediator). MediatR package is not used. - FluentValidation for validators.
- Custom mapping framework in
Grand.Mappingwith an AutoMapper-compatible profile API (Profile,CreateMap,ForMember). AutoMapper package is not used. - Razor views, partials, view components, and tag helpers.
- Vue 3 and Vite for storefront frontend assets.
- Bootstrap and Bootstrap Icons.
- DotLiquid for message templates.
- OpenAPI and Scalar in the API module.
- Aspire and OpenTelemetry for local orchestration and observability.
- Docker and Azure Pipelines for build and deployment workflows.
Core Projects
src/Core/Grand.Domain
Use for domain entities, settings objects, enums, and domain-level contracts.
Examples:
CatalogOrdersCustomersVendorsStoresPaymentsShippingTaxPermissionsMessages
Do not put UI models, persistence details, or controller behavior here.
src/Core/Grand.Data
Use for repository abstractions and MongoDB/LiteDB data infrastructure.
Use this area for:
- repository contracts and implementations
- MongoDB context behavior
- data provider configuration
- audit provider integration
Do not put business workflow rules or UI preparation here.
src/Core/Grand.Infrastructure
Use for cross-cutting runtime infrastructure.
Use this area for:
- startup abstractions
- caching
- plugin infrastructure
- module infrastructure
- endpoint provider infrastructure
- type scanning
- migrations infrastructure
- model binding
- validators infrastructure
src/Core/Grand.Mapping
Use for shared mapping infrastructure and mapping support.
src/Core/Grand.Mediator
Use for the mediator itself — request/notification abstractions, dispatch, and handler registration. Handlers and the messages they handle belong to the owning project, never here.
src/Core/Grand.SharedKernel
Use for low-level shared primitives, attributes, extensions, and small cross-cutting helpers.
Business Projects
src/Business/Grand.Business.Core
Use for business interfaces, commands, queries, utilities, and cross-business contracts.
Put interfaces here when implementations live in a feature-specific business project.
Feature Business Projects
Use these for implementations:
Grand.Business.AuthenticationGrand.Business.CatalogGrand.Business.CheckoutGrand.Business.CmsGrand.Business.CommonGrand.Business.CustomersGrand.Business.MarketingGrand.Business.MessagesGrand.Business.Storage
Use the closest feature project. Register implementations in that project's Startup/StartupApplication.cs.
Web Projects
src/Web/Grand.Web
Use for public storefront controllers, views, view models, commands, handlers, validators, components, and static web assets.
Important folders:
ControllersViewsViews/SharedViews/PdfTemplatesComponentsCommandsFeaturesModelsValidatorswwwrootvueapp
src/Web/Grand.Web.Admin
Use for main Admin panel controllers and views.
Controllers are in:
src/Web/Grand.Web.Admin/Controllers
Views are in:
src/Web/Grand.Web.Admin/Areas/Admin/Views
src/Web/Grand.Web.Store
Use for Store Owner panel controllers and views.
Controllers are in:
src/Web/Grand.Web.Store/Controllers
Views are in:
src/Web/Grand.Web.Store/Areas/Store/Views
src/Web/Grand.Web.Vendor
Use for Vendor panel controllers, views, models, services, components, and vendor-specific access behavior.
Controllers are in:
src/Web/Grand.Web.Vendor/Controllers
Views are in:
src/Web/Grand.Web.Vendor/Areas/Vendor/Views
src/Web/Grand.Web.AdminShared
Use for shared admin models, validators, mapper profiles, extensions, and contracts used by Admin, Store Owner, and sometimes Vendor panels.
Check this project before adding duplicate admin models.
src/Web/Grand.Web.Common
Use for shared web infrastructure, base controllers, base components, themes, tag helpers, and common MVC helpers.
src/Web/Grand.SharedUIResources
Use for shared static UI resources.
Plugins
Plugins live under src/Plugins.
Existing plugin categories:
Authentication.*DiscountRules.*ExchangeRate.*Payments.*Shipping.*Tax.*Theme.*Widgets.*
Use plugins for installable providers, integrations, widgets, payment methods, shipping methods, tax providers, authentication providers, discount rules, exchange rates, and themes.
Plugin build output goes to:
src/Web/Grand.Web/Plugins/{SystemName}
Use the plugin-module skill for plugin work.
Modules
Modules live under src/Modules.
Existing modules:
Grand.Module.ApiGrand.Module.InstallerGrand.Module.MigrationGrand.Module.ScheduledTasks
Use modules for application-level features that are not installable provider plugins.
Module build output goes to:
src/Web/Grand.Web/Modules/{ModuleName}
Use the plugin-module skill for module structure.
API Module
API functionality lives in:
src/Modules/Grand.Module.Api
Use for:
- REST controllers
- DTOs
- validators
- command and query handlers
- JWT
- OpenAPI metadata
- API mapping profiles
Installer And Migration
Installer behavior lives in:
src/Modules/Grand.Module.Installer
Migration behavior lives in:
src/Modules/Grand.Module.Migration
Use installer for initial seed data. Use migration for versioned updates to existing installations.
Common seeded areas:
- permissions
- admin sitemap
- settings
- message templates
- stores
- schedule tasks
- localization resources
Scheduled Tasks
Scheduled task module:
src/Modules/Grand.Module.ScheduledTasks
Register tasks in:
Startup/StartupApplication.cs
Use keyed scoped registration:
AddKeyedScoped<IScheduleTask, TaskType>("Task name")
Frontend Assets
Storefront frontend source:
src/Web/Grand.Web/vueapp
Committed frontend output:
src/Web/Grand.Web/wwwroot/bundles
Theme CSS source:
src/Web/Grand.Web/wwwroot/theme/css
Run frontend build when changing Vue source or theme CSS that affects committed bundles.
Admin, Store and Vendor panel frontend project:
src/Web/Grand.SharedUIResources/adminapp(Vite, Vitest, Playwright, Kendo grid analyzer)
Its output src/Web/Grand.SharedUIResources/wwwroot/administration/bundles is not loaded by any panel and not committed yet. See .ai/skills/frontend-bundle-workflow.md.
Tests
Tests live under:
src/Tests
Choose the closest test project by target ownership:
- Business changes:
Grand.Business.*.Tests - Data changes:
Grand.Data.Tests - Domain changes:
Grand.Domain.Tests - Infrastructure changes:
Grand.Infrastructure.Tests - Mapping changes:
Grand.Mapping.Tests - Mediator changes:
Grand.Mediator.Tests - Module changes:
Grand.Modules.Testsor module-specific tests - API changes:
Grand.Module.Api.Tests - Web common changes:
Grand.Web.Common.Tests - Admin changes:
Grand.Web.Admin.Tests - Storefront changes:
Grand.Web.Tests - Store Owner changes:
Grand.Web.Store.Tests - Shared kernel changes:
Grand.SharedKernel.Tests
Expansion Rules
Add Domain Data
- Add or update entity or settings class in
Grand.Domain. - Update data access behavior only if repository or MongoDB configuration requires it.
- Update business services and interfaces.
- Update UI/API models, mappers, validators, and tests.
Add Business Logic
- Add interface to
Grand.Business.Corewhen used across projects. - Add implementation to the closest
Grand.Business.*project. - Register implementation in
StartupApplication. - Add or update tests in the matching business test project.
Add Public Storefront UI
- Update
Grand.Webcontroller, command, query, handler, model, validator, component, or view. - Update localization resources.
- Update frontend bundles when Vue or theme CSS source changes.
- Add web tests when behavior changes.
Add Admin UI
- Use
admin-area-changes. - Update
Grand.Web.AdminSharedif shared models, validators, or mapper profiles are involved. - Update Admin, Store Owner, and Vendor panels only where the role should own the workflow.
Add Plugin Or Module
- Use
plugin-module. - Start from the closest existing plugin or module.
- Keep output paths aligned with
Grand.Web/PluginsorGrand.Web/Modules.
Add Message Template
- Use
template-creation. - Update
MessageTemplateNameswhen code references the template. - Update installer seed data for new installations.
- Add DotLiquid tokens only through
Liquid*drops and token provider patterns.
Add Permission Or Menu Item
- Update permission constants and seed data using existing installer utilities.
- Update
StandardAdminSiteMapwhen navigation is required. - Enforce permission server-side in controllers or services.
- Check Admin, Store Owner, and Vendor differences.