@dan This is a big one for me that I did not notice in the demo. The ability to point a Markdown component to a file that will load the text would be very helpful. I do all of my Markdown writing in an external editor so that I can archive the text separately from Elements.
So being able to point to a file would save a lot of work. If there is no support for this, then it looks like I have to copy and paste the text from my file into the editor in Elements, which then means I have lost the connection to my external source. Every time I make a change, I have to repeat the process.
It’s just like a text component… or any other component for that matter. The data is attached to that instance of the component on the page and is stored in the Project file.
We’ll have the beta out early next week for you to play with.
Looking forward to it. I have already been looking at the @markdown support in the API and the Markdown component in anticipation that I might attempt to add support to it for loading the text from a file.
Very excited to try this new version, Elements is a great platform, but this seems to address so many of the things that have been missing and which Rapidweaver Classic addressed through Stacks!
Sure. I just find it odd that most settings (Spacing etc.) use the theme spacings you set in the studio. And I’m also able to adjust top/bottom and left/right together.
It’s different for border and border radius though, which I personally find rather irritating:
I mean, I get it. It’s probably because of the tailwind classes, but it would be nice if at least the settings would work in the way it does with padding and margins. But for Borders, I find those options a bit restricting.
I can’t wait for these updates. Thanks for the relentless work you guys do to push updates so quickly! I was wondering if a megamenu component is on the list for the future?
