Any suggestions for adding a WYSIWYG editor to our app?

Ask us anything
#1

Can you provide tips and suggestions for adding a WYSIWYG editor to our app?

1 Like
#2

Hi @talentbender :wave:

We expect to deliver a rich text input field in the next 3-4 weeks.

Would that work for you or do you need it sooner?

5 Likes
#3

Thanks, Joyce. That time frame is cool. I have a number of other things I can work on during that time.

Dewayne

1 Like
#4

Perfect! Thank you @talentbender :slight_smile:

#5

Hopefully an emoji picker could squeeze into the plugin :sweat_smile::pray::grin:

2 Likes
#6

I’m really looking forward to this - any update on that timeline?

In advance of the feature release, it would be super helpful to understand how the input will be stored in the variable, so that I can work on the backend APIs. For example, will I be passing messages in markdown language to my backend, or will the WYSIWYG editor create HTML that can be saved/sent through a backend?

3 Likes
#7

Ha, exactly 4 weeks later! I’d love to add this to my site as well. Working on a form for an event app. Will it be possible to include images? I’m not sure where the image file is stored in that case, but ideally it could be loaded directly to xano instead of filling weweb storage. Thank you

1 Like
#8

It’s taking longer than we expected. We’re a couple of weeks late on that one :confused:

The editor will output HTML or JSON, markdown is not possible with the solution we chose.

Not with the first version of this element, no. We will iterate on the element but not sure when images will be available.

2 Likes
#9

Thank you for the update, @Joyce! I am really looking forward to this component going live - I’ll be using it in lots of places across my app.

2 Likes
#10

Hey @Joyce :wave:

I realize there are a lot of other priorities and features in development, but I’m curious—is there any update on this by chance?

2 Likes
#11

Hi @caffeinatedwes, it is currently being reviewed but I don’t know when it will be ready for release.

2 Likes
#12

Hey there, just wanted to update you on the rich text input element:

  • the lead dev on this addressed all the comments from the initial QA last week
  • the element will now go through a second round of QA
  • BUT… I don’t know when that will happen yet because most of the team is on holidays this week :slight_smile:

Sorry the update isn’t more precise! We know you’ve been waiting for this for a long time now.

We ran into a few bumps in the road and had to prioritize a couple of other things like the Supabase and Stripe plugins but, rest assured, it’s still very much top of mind for us!

4 Likes
#13

Thanks for the update, Joyce :muscle:

1 Like
#14

Thanks for the update, Joyce!!! No problem with the delays. I’m just recently getting back to working on my app. WeWeb is such a cool tool. I’m probably slower with development than your typical users, but it’s fun when I get things to work and check items off my list.

Sincerely,
Dewayne

1 Like
#15

I hope this is realeased soon! :smiley:

1 Like
#16

@pipeleteli I’m anxiously waiting too :nerd_face:

1 Like
#17

Any news on this front? Is there perhaps a beta version some of us could try?

2 Likes
#18

Hello @kyanaloe, most of the team is back since this week. We should release soon, but I don’t know exactly when, sorry

3 Likes
#19

I understand that you’ve all had a lot going on and sometimes things take longer than expected. That said, this is an important element for my app and I need to be prepared to demo with clients soon. Should I be exploring alternative solutions (like TinyMCE for example)? Or are you confident that it will be released in the next week or so?

#20

I only need a way to collect and display multi-paragraph text correctly. All the heading, decoration, links etc is not required.

(Paragraph break :wink:)

Is there another option, long answer doesn’t send paragraph breaks right? This is the missing piece for my mvp.