-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azimuth cms package support #9
Comments
This would be very cool, looking forward to seeing your progress! |
I'll take a look - we were planning on building a simple CMS, integration shouldn't be too hard - particularly if Azimuth is using iron-router. |
It does use iron-router, so that's good to hear I am looking forward to your built-in CMS too! |
We're going to be adding our own CMS, I'm closing this, reference #20 |
cmbirk
pushed a commit
to cmbirk/reaction
that referenced
this issue
Aug 18, 2019
…t-plugin Product import plugin
brent-hoover
pushed a commit
that referenced
this issue
Sep 20, 2022
…ormalize-url-5.3.1 chore(deps): Bump normalize-url from 5.3.0 to 5.3.1
brent-hoover
pushed a commit
that referenced
this issue
Sep 20, 2022
…6c9b9936059173aa19c9 [Snyk] Upgrade @reactioncommerce/api-utils from 1.14.2 to 1.16.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there a way to integrate this package and use admin interfaces together? As soon as possible I'll try out reaction with azimuth cms package. I'll start building simple website with azimuth and then adding to it reactioncommerce package. I think it's a good idea to use this package as a cms module and reaction as a shopping module.
The text was updated successfully, but these errors were encountered: