Roadmap

[fballiano]

This is a high level mid-future roadmap

• customer segmentation module
• blog module
• sitemap split by entity and URL number limit per file
• import/export support for categories
• array adapter for import
• removal of prototypejs from the backend
• removal of Zend_Framework (only Zend_Db remaining)
• followup emails module
• removing all Varien classes and make them into lib/Maho namespace
• login via magic link
• rule based product upsell/crossell/related
• giftcard module
• one page checkout
• USPS: convert to new REST APIs
• feed manager for facebook, google shopping etc
• content versioning for CMS/blog
• VIES based VAT validation
• new paypal module
• new custom image editor with local AI based background removal
• LSP/MCP module with support for VSCode and Zed
• schema.org structured data
• API-Platform based new API system
• basic AI module
• RMA
• new admin theme
• full EAV editor for all entities
• scheduled updates module
• login with Google, Facebook, Apple (via hybridauth)
• add sample data to test suite and add navigation tests to home, category, product, cms page, blog page, blog post

--

• Make sure to check our milestones and our issues (most specs for future developments are there) to see what we're working on in deeper detail
• Feel free to add suggestions!

Need one feature faster? Think about sponsoring its development, contact me to discuss it!

[alessandro-magi]

Hi,
It would be really interesting to have a visual editor for CMS pages, categories, and even product descriptions.

In general, it would be useful to have it in all sections where the editor is present, to enhance and improve the content of the pages without having to modify the HTML/CSS.

Perhaps the implemented editor, Tip Tap, allows this?

Thanks.
Alessandro

[alessandro-magi]

Hi,
The sitemap generated by the core sitemap could be improved, for example by adding the image link if present and various other information, as Google reports in its documentation:

https://developers.google.com/search/docs/crawling-indexing/sitemaps/combine-sitemap-extensions?hl=en

Thanks,
Alessandro

[alessandro-magi]

Of course, for that it might be useful to split the sitemap into smaller sitemaps of 5,000 or 10,000 records.

[fballiano]

from what i've seen, images/videos extension are only for images and videos that are not part of any other page, so it shouldn't be necessary to have those in the sitemap. it would still be interesting to split the sitemap for bigger catalogs tho. am I missing something?

[alessandro-magi]

I proposed this idea because, taking other platforms such as Shopify and Prestashop as examples, they by default generate the sitemap with all the content on the site, while also adding additional instructions for Google.

It starts with having a sitemap that includes specific sub-sitemaps, based on the type of content:

<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<!--  This is the parent sitemap linking to additional sitemaps for products, collections and pages as shown below. The sitemap cannot be edited manually, but is kept up to date in real time.  -->
<sitemap>
<loc>https://example.com/sitemap_products_1.xml?from=100000&to=200000</loc>
</sitemap>
<sitemap>
<loc>https://example.com/sitemap_products_2.xml?from=200001&to=400000</loc>
</sitemap>
<sitemap>
<loc>https://example.com/sitemap_pages_1.xml?from=50000&to=600000</loc>
</sitemap>
<sitemap>
<loc>https://example.com/sitemap_collections_1.xml?from=10000&to=50000</loc>
</sitemap>
<sitemap>
<loc>https://example.com/sitemap_blogs_1.xml</loc>
</sitemap>
</sitemapindex>

From here, the sitemap branches out into specific ones, starting with products:

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:image="http://www.google.com/schemas/sitemap-image/1.1">
<url>
<loc>https://example.com/</loc>
<changefreq>daily</changefreq>
</url>
<url>
<loc>https://example.com/products/wooden-ornamental-border-180x18-verdemax</loc>
<lastmod>2025-08-27T17:35:57+02:00</lastmod>
<changefreq>daily</changefreq>
<image:image>
<image:loc>https://cdn.example.com/products/wooden-border-180x18.jpg?v=123456789</image:loc>
<image:title>Wooden ornamental border with tips - 1.80 m x h 18 cm - Verdemax</image:title>
<image:caption>Wooden ornamental border with tips - 1.80 m x h 18 cm - Verdemax (2492121)</image:caption>
</image:image>
</url>
</urlset>

Example of a sitemap for collections / categories:

<url>
<loc>https://example.com/collections/winter-salad-endive-escarole</loc>
<lastmod>2025-08-27T09:13:39+02:00</lastmod>
<changefreq>daily</changefreq>
<image:image>
<image:loc>https://cdn.example.com/collections/endive-escarole.png?v=987654321</image:loc>
<image:title>Winter salad seedlings: Endive or Escarole</image:title>
</image:image>
</url>

Example of a sitemap for the blog:

<url>
<loc>https://example.com/blogs/garden/best-tools-for-working-the-soil</loc>
<lastmod>2022-08-10T20:50:54+02:00</lastmod>
<changefreq>weekly</changefreq>
<image:image>
<image:loc>https://cdn.example.com/articles/best-soil-tools.webp?v=1659705770</image:loc>
<image:title>What are the best tools for working the soil?</image:title>
</image:image>
</url>

Example of a sitemap for pages (CMS pages):

<url>
<loc>https://example.com/pages/help-contact-us</loc>
<lastmod>2022-06-24T11:45:09+02:00</lastmod>
<changefreq>weekly</changefreq>
</url>

The product and category sitemaps, if they contain many records, are split into blocks of 5,000 entities.

It is also considered best practice to include the pages related to brands, if they are not managed as categories (although in such cases, a specific extension normally exists).

[fballiano]

@alessandro-magi #297 ;-)

[alessandro-magi]

Ohh great, thank you

[JonLaliberte]

login with Google, Facebook, Apple (via hybridauth)
"Magic" links would be interesting to support. I'm not a huge fan, but some customers really like them.

[fballiano]

interesting idea, added it to the roadmap!

[fballiano]

@JonLaliberte it should be ready: #353

Tomorrow I'll re-test everything before merging

[JonLaliberte]

@fballiano Wow. Did not anticipate that turn around haha. We just started looking into moving from OpenMage this afternoon, but great to see this. Thanks!

[fballiano]

:-) when something seems not too difficult I try to pop it in front of the roadmap ;-)

[alessandro-magi]

Hi, i think it's necessary a One Page Checkout layout, like Firecheckout or Shopify layout.

Thanks
Alessandro

[fballiano]

Hey @alessandro-magi, although I find onepagecheckouts more confusing, it's what people want so we should do that. I've tried in the past but it turned out to be more difficult than I was expecting, will try again soon

[empiricompany]

Hi @fballiano!
In my opinion, the most urgent thing to implement is the new PayPal APIs. Some work on this has already started in OpenMage:
https://developer.paypal.com/serversdk/php/getting-started/how-to-get-started

[fballiano]

I'll put this on the roadmap, shipping/payment methods are not easy :( let's see

[empiricompany]

Thank you, I’ll be happy to test it and contribute.

[gputignano]

Please, update the roadmap. Thanks.

[fballiano]

wooopsss sorry 😅 partially done!

[gputignano]

Thanks