I hadn't really thought about reconfiguring the current editor. I like your idea. However, my users are very non-technical--so expecting them to edit code like that might be problematic.
Your suggestion got me looking at another option--a TinyMCE plug-in. I found one specifically for Bootstrap. But I have another question... Can you offer any recommendations for adding such a plugin? It appears that Mezzanine's TinyMCE configuration isn't structured similar to the examples at TinyMCE's website (being new to Mezzanine, I'm also new to TinyMCE). It also appears that TinyMCE is plugged into many areas of Mezzanine (RichTextField plus file uploads and other areas I haven't explored too much yet. My concern is that I don't want to break other functionality by modifying the editor interface. Am I overthinking this? Or is it as simple as adding the plugin and configuring it? (I'm demo-ing some functionality to a customer tomorrow, so a little under the gun and not much time to properly test and explore this particular functionality right now. If I don't work it out tonight, I'll leave it out of the demo and work on it over the weekend. 🙂) On Wednesday, August 8, 2018 at 1:39:17 PM UTC-7, Eduardo Rivas wrote: > > I have achieved something similar using TinyMCE (the builtin editor). What > I do is have the site CSS applied to editor. So if site editors want to > build a grid with Bootstrap classes, they have to edit the markup, but can > at least see how text and other images will appear in the grid. > > > > To do this, you need to tell TinyMCE to load Bootstrap’s CSS files: > > 1. Create your own version of tinymce_setup.js. Put it in > static/mezzanine/js in one of your apps and copy the contents from here: > > https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/static/mezzanine/js/tinymce_setup.js > 2. Change the content_css option into an array (line 82). We want to > include the base CSS and then add our own entries to the array. Something > like: content_css: [window.__tinymce_css, ‘/path/to/bootstrap.css’] > 3. Now TinyMCE should have Bootstrap styles applied. Clear your cache > if you don’t see the changes applied. > > > > Hope that helps! > > > > *From: *Thomas Smith <javascript:> > *Sent: *Wednesday, August 8, 2018 2:25 PM > *To: *Mezzanine Users <javascript:> > *Subject: *[mezzanine-users] Recommendations for Bootstrap WYSIWYG editor? > > > > I do a lot of work with Bootstrap. I recently began learning Mezzanine and > it's working great. > > > > However, I'm finding that in order to maintain the responsiveness of the > sites I manage, I'm having to create custom page types and models in order > to allow content managers to edit various responsive elements without > messing up the responsiveness. > > > > Maybe there's a better way to handle this (I am new to Mezzanine), but it > seems logical to me that using a Bootstrap-aware editor would allow editing > an entire responsive page without the need for new page types or models. > > > > Can anyone offer suggestions for addressing this problem please? > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to mezzanine-use...@googlegroups.com <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
