Could you please stop switching support/knowledge base systems every few years.
Hitting brick walls because of broken links or missing images in descriptions is getting tiresome.
It's definitely gotten worse. They've stopped updating the developer docs which are full of formatting issues and broken links since the most recent move. Doesn't seem to be any way to give them feedback about articles with issues. And Neto staff have stopped responding to these forums posts.
Not really sure why they migrated Galaxy only to abandon it.
Don't know there's issues with your platform if you don't visit the platform.
@Blake and @Erik Merkley.
I wanted you to come back to this discussion, even though it is now a year old.
I’ve been in the Global Support Manager role at Maropost for coming up to a year now, and I can understand the frustration behind both of your comments. Broken knowledge base links, missing content and community questions receiving little or no response isn't the experience we want Galaxy to provide.
A significant focus for me over the past year has been rebuilding and upskilling our Support teams, particularly around our more complex products such as Neto and Retail Express. We have made progress, although I’m also very aware there is still more work to do.
More recently, I’ve also taken responsibility for our Content & Community team, which includes the Galaxy Knowledge Base and Community. One of the things I’m working on now is exactly what you highlighted here — making sure community discussions aren't simply left unanswered and that Support and other teams across Maropost are more actively involved where they can help.
I’m currently reviewing older discussions like this one for that reason. Rather than removing this post, I wanted to acknowledge the feedback and leave the discussion visible because it is useful feedback on where we need to improve.
We’re also putting more focus on identifying broken, outdated or missing Knowledge Base content and getting those gaps back to the Content & Community team for review.
So while I can't claim we've solved everything raised here, the concerns haven't been ignored, and there is now a deliberate effort to make Galaxy a more useful and supported space again.
And please continue to call out gaps when you find them — whether that's documentation that needs attention or a discussion where you feel Maropost should be contributing.
