Multiple content type changes to support future features

[dvidsilva]

Key Models Created

1. Product:
   • Core content-type for products sold in the marketplace.
   • Attributes include name, price, description, inventory, and metadata for SEO.
   • Integrated with Stripe for payment processing and handling unique identifiers (IDs).
2. Order:
   • Captures orders placed by customers, with attributes like total amount, status, and customer information.
   • Order snapshots were added to ensure consistency (e.g., if a product changes after the order is placed).
   • Tracks Stripe payment attempts and status for each order.
3. Shipments:
   • Tracks deliveries associated with an order.
   • Multiple shipments per order are allowed.
   • Attributes include tracking code, status (shipped, in transit, delivered), and carrier info.
4. Inbox:
   • Allows users to send messages to store owners without being logged in.
   • Messages are categorized by thread using a parentMessageId, enabling simple conversation threads.
   • Store owners can reply, creating an ongoing dialog.
5. Pages:
   • For managing static content (e.g., about us, policies, etc.).
   • Pages have metadata for ordering in menus and SEO attributes.
6. Categories:
   • Used for classifying products and content like blog posts.
   • Users can create their own categories, which are related to different content types.

Recent Focus

• API Integration: Preparing the endpoints for reading products, creating orders, and handling payments.
• Content Structure: Refining how categories are managed across content-types to keep everything organized.
• Inbox Threads: Introduced conversation threading for store owner-customer communication.
• Shipment Tracking: Ensuring that multiple shipments can be associated with a single order.

Next Steps

• Finalize authorization roles: Ensure different types of users (store owners, customers, admins) have the appropriate permissions.
• Test API with Frontend: Connect the API responses to the sample storefront.
• Add SEO components: Ensure all models support meta-data for SEO purposes.

This gives us a solid foundation for Markket.place, and we’re now focusing on ensuring smooth front-end integration and finalizing the user experience!