# 🏓 Fibery Product Report: October 2025 **URL:** \ **Category:** News & Announcements\ **Created:** [November 7, 2025, 1:51pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971 "2025-11-07T13:51:59Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [November 7, 2025, 3:23pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/9 "2025-11-07T15:23:32Z")
You guys are amazing! Lovely month of updates. > [@mdubakov](#): > > (it is taking us 3 years… 🥲) So worth it though! > [@mdubakov](#): > > Access the previous value for Rules Super interested to see what will be possible with this! > [@mdubakov](#): > > WYSIWYG editor instead of plain text templates in automations (aka replace markdown editor) Personally I would much perfer something like this: [Rich text to Markdown with relations in automation](https://community.fibery.io/t/rich-text-to-markdown-with-relations-in-automation/8289). My goal is to leave as much content outside of automations, and into entities, then use those entities as the templates. This allows granular control on who can edit what, and doesn’t require someone to be an architect in order to edit the email template. The exception to this is when using the “Ask User” on a markdown field. The alternative is to have them make a new entity, and have the automation get triggered on creation. The upside of this is that it could be set up as a draft, and only send when the user presses “Send”. Not sure of how it could work exactly. But just some ideas! * * * Super excited for all the things coming!! Files, access, mobile, there’s just to much good stuff coming. Thank you all for putting your love and energy in this product! --- _[View the full topic](https://community.fibery.io/t/fibery-product-report-october-2025/9971)._