sboulahtit/orion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: rename Wizamart to Orion across entire codebase

Browse Source 
Replace all ~1,086 occurrences of Wizamart/wizamart/WIZAMART/WizaMart
with Orion/orion/ORION across 184 files. This includes database
identifiers, email addresses, domain references, R2 bucket names,
DNS prefixes, encryption salt, Celery app name, config defaults,
Docker configs, CI configs, documentation, seed data, and templates.

Renames homepage-wizamart.html template to homepage-orion.html.
Fixes duplicate file_pattern key in api.yaml architecture rule.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Samir Boulahtit
2026-02-14 16:46:56 +01:00
parent 34ee7bb7ad
commit e9253fbd84
184 changed files with 1227 additions and 1228 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/guides/email-settings.md
View File

@@ -1,6 +1,6 @@
# Email Settings Guide
This guide covers email configuration for both **stores** and **platform administrators**. The Wizamart platform uses a layered email system where stores manage their own email sending while the platform handles system-level communications.
This guide covers email configuration for both **stores** and **platform administrators**. The Orion platform uses a layered email system where stores manage their own email sending while the platform handles system-level communications.
## Overview
@@ -199,12 +199,12 @@ The email system includes tier-based branding for store emails:
| Tier | Branding |
|------|----------|
| Essential | "Powered by Wizamart" footer |
| Professional | "Powered by Wizamart" footer |
| Essential | "Powered by Orion" footer |
| Professional | "Powered by Orion" footer |
| Business | No branding (white-label) |
| Enterprise | No branding (white-label) |
Business and Enterprise tier stores get completely white-labeled emails with no Wizamart branding.
Business and Enterprise tier stores get completely white-labeled emails with no Orion branding.
---

18
docs/guides/email-templates.md
View File

@@ -2,7 +2,7 @@
## Overview
The Wizamart platform provides a comprehensive email template system that allows:
The Orion platform provides a comprehensive email template system that allows:
- **Platform Administrators**: Manage all email templates across the platform
- **Stores**: Customize customer-facing emails with their own branding
@@ -25,7 +25,7 @@ Each template shows its customization status:
| Status | Description |
|--------|-------------|
| **Platform Default** | Using the standard Wizamart template |
| **Platform Default** | Using the standard Orion template |
| **Customized** | You have created a custom version |
| Language badges (green) | Languages where you have customizations |
@@ -49,7 +49,7 @@ Templates use special variables that are automatically replaced with actual valu
| `{{ customer_name }}` | Customer's first name |
| `{{ order_number }}` | Order reference number |
| `{{ store_name }}` | Your store name |
| `{{ platform_name }}` | Platform name (Wizamart or your whitelabel name) |
| `{{ platform_name }}` | Platform name (Orion or your whitelabel name) |
Each template shows its available variables in the reference panel.
@@ -149,7 +149,7 @@ Logs show:
1. **Use all 4 languages**: Provide content in EN, FR, DE, and LB
2. **Test before publishing**: Always send test emails
3. **Include plain text**: Not all email clients support HTML
4. **Use consistent branding**: Follow Wizamart brand guidelines
4. **Use consistent branding**: Follow Orion brand guidelines
5. **Keep subjects short**: Under 60 characters for mobile
---
@@ -175,14 +175,14 @@ When sending an email, the system determines the language in this order:
### Standard Stores
Standard stores' emails include Wizamart branding:
- Wizamart logo in header
- "Powered by Wizamart" footer
Standard stores' emails include Orion branding:
- Orion logo in header
- "Powered by Orion" footer
### Whitelabel Stores
Enterprise-tier stores with whitelabel enabled:
- No Wizamart branding
- No Orion branding
- Store's logo in header
- Custom footer (if configured)
@@ -224,7 +224,7 @@ Enterprise-tier stores with whitelabel enabled:
### Common Variables (All Templates)
```
{{ platform_name }} - "Wizamart" or whitelabel name
{{ platform_name }} - "Orion" or whitelabel name
{{ platform_logo_url }} - Platform logo URL
{{ support_email }} - Support email address
{{ store_name }} - Store's business name

2
docs/guides/inventory-management.md
View File

@@ -2,7 +2,7 @@
## Overview
The Wizamart platform provides comprehensive inventory management with support for:
The Orion platform provides comprehensive inventory management with support for:
- **Multi-location tracking** - Track stock across warehouses, stores, and storage bins
- **Reservation system** - Reserve items for pending orders

28
docs/guides/letzshop-marketplace-api.md
View File

@@ -2,7 +2,7 @@
## Introduction
This guide covers the Wizamart platform's integration with the Letzshop marketplace, including:
This guide covers the Orion platform's integration with the Letzshop marketplace, including:
- **Product Export**: Generate Letzshop-compatible CSV files from your product catalog
- **Order Import**: Fetch and manage orders from Letzshop
@@ -15,7 +15,7 @@ This guide covers the Wizamart platform's integration with the Letzshop marketpl
### Overview
The Wizamart platform can export your products to Letzshop-compatible CSV format (Google Shopping feed format). This allows you to:
The Orion platform can export your products to Letzshop-compatible CSV format (Google Shopping feed format). This allows you to:
- Upload your product catalog to Letzshop marketplace
- Generate feeds in multiple languages (English, French, German)
@@ -118,9 +118,9 @@ The following sections document the Letzshop GraphQL API for direct integration.
## GraphQL API
Utilizing this API, you can retrieve and modify data on products, stores, and shipments. Letzshop uses GraphQL, allowing for precise queries.
Utilizing this API, you can retrieve and modify data on products, stores, and shipments. Letzshop uses GraphQL, allowing for precise queries.
**Endpoint**:
**Endpoint**:
http://letzshop.lu/graphql
Replace YOUR_API_ACCESS_KEY with your actual key or remove the Authorization header for public data.
@@ -141,8 +141,8 @@ Authorization: Bearer YOUR_API_ACCESS_KEY
## Playground
- Access the interactive GraphQL Playground via the Letzshop website.
- It provides live docs, auto-complete (CTRL + Space), and run-time testing.
- Access the interactive GraphQL Playground via the Letzshop website.
- It provides live docs, auto-complete (CTRL + Space), and run-time testing.
- **Caution**: You're working on production—mutations like confirming orders are real. [1](https://letzshop.lu/en/dev)
---
@@ -168,10 +168,10 @@ The following GraphQL fields will be removed soon:
Using the API, you can:
- Fetch unconfirmed orders
- Confirm or reject them
- Set tracking numbers
- Handle returns
- Fetch unconfirmed orders
- Confirm or reject them
- Set tracking numbers
- Handle returns
All of this requires at least "shop manager" API key access. Multi-store management is supported if rights allow. [1](https://letzshop.lu/en/dev)
@@ -307,10 +307,10 @@ Each event includes:
A variety of event types are supported. Common ones include:
- `ShipmentConfirmed`, `ShipmentRefundCreated`
- `UserAnonymized`, `UserCreated`, `UserDestroyed`, `UserUpdated`
- `VariantWithPriceCrossedCreated`, `...Updated`
- `StoreCategoryCreated`, `Destroyed`, `Updated`
- `ShipmentConfirmed`, `ShipmentRefundCreated`
- `UserAnonymized`, `UserCreated`, `UserDestroyed`, `UserUpdated`
- `VariantWithPriceCrossedCreated`, `...Updated`
- `StoreCategoryCreated`, `Destroyed`, `Updated`
- `StoreCreated`, `Destroyed`, `Updated`
Exact payload structure varies per event type. [1](https://letzshop.lu/en/dev)