Sync your Webflow CMS with Xano

แชร์
ฝัง
  • เผยแพร่เมื่อ 3 พ.ย. 2024

ความคิดเห็น • 10

  • @rileycx
    @rileycx ปีที่แล้ว

    Thank you! I just sent an email about this a few days ago and it's great to see this put together.

  • @fathom5209
    @fathom5209 ปีที่แล้ว +2

    Great video, thank you. Currently Wized does not offer server-side rendering (it is on the roadmap), so using Xano without the Webflow CMS will likely result in poor SEO performance. What about using Xano as the master database for the Webflow CMS - all CRUD actions are conducted on the Xano side and pushed to the Webflow CMS? Would you still envisage the performance issues discussed?

    • @nocodebackend
      @nocodebackend  ปีที่แล้ว +1

      Using the Webflow CMS as your primary DB would mean that essentially you are doing a one-way sync (all data would be updated on the Xano side and sent to Webflow on update) which would alleviate those performance concerns for sure.

    • @fathom5209
      @fathom5209 ปีที่แล้ว +4

      @Xano one thing that is important is that the Webflow ID changes if the project ever needs to be restored to a previous backup. It cannot be relied on for syncs. It's better to setup a Xano ID field in the webflow CMS and sync to that.

  • @StoryofToday
    @StoryofToday 3 หลายเดือนก่อน

    thank you!

  • @TheDvscg
    @TheDvscg ปีที่แล้ว +1

    Would be very useful to see your mouse cursor in the recording. Would make things way easier to follow and provide context as to what items on the screen you are talking about and where you are clicking.

  • @marcusfrancis24
    @marcusfrancis24 ปีที่แล้ว +2

    what about using whalesync for 2way sync?

    • @JanMartin-e7b
      @JanMartin-e7b ปีที่แล้ว

      also interested for that answer. do you have more detailed information why its better to have only 1 way sync and manage all data from 1 place ?

  • @yashbindal_
    @yashbindal_ ปีที่แล้ว

    when I tried adding post call in between to webflow it's showing "fields' is required,". as xano is using "params" instead of "fields"