search

GetmeUK / ContentTools

A JS library for building WYSIWYG editors for HTML content.
http://getcontenttools.com
MIT License
3.94k stars 393 forks source link

Chatroom e.g. on Slack for faster developers' question resolution #562

Open voltel opened 4 years ago

voltel commented 4 years ago

I believe having StackOverflow as the environment for peer communication and online help has proven to be ineffective. I researched questions on StackOverflow and found only 20 or so posts with answers, many of which feel outdated (using older API). I suggest starting a group on Slack or having other recently introduced instant information exchange tools to give developers an opportunity to ask questions in real-time with faster inquiry-response time.

As an illustration I have a still unresolved inquiry on StackOverflow at the time this post is written. I posted a question on StackOverflow and didn't have any response. Could you please see to the problem of mine and help?

Whatever alternative means of communication are going to be introduced, I hope it will appear at the documentations site.

anthonyjb commented 4 years ago

Sorry you've not gotten answers on stackoverflow, I often struggle to find time to search StackOverflow these days when once I was very active there. We used gitter at one time but it was underused and so I dropped it in the end.

I'll add this as an issue to address in ContentTools 2 as well, it's partly better documentation that's needed, (tutorials, references, etc) and channels devs are comfortable with (e.g slack). I use slack daily so I don't see a problem with this though I would worry people would expect swifter responses than they do when posting an issue and that's something I can't always provide - hopefully there's enough developers out there using CT that the slack channel would provide community support more so than gitter did.

So yes I'll create a slack environment for CT / CT2 as a first step.

voltel commented 4 years ago

Thank you, Anthony! Have you posted your intentions (roadmap) for ContentTools2, I'd like to see what are the major changes you have in mind?

I am not a JS pro, so you may as well (should) disregard my opinion below. I very much liked the idea of "semantic" properties/css classes assignment (e.g. properties "Definition" and "Note" in the demo). The abstraction is to have a fully html-agnostic user to produce a good-quality html markup.

But I am not supportive of the idea of having to re-build the library for any tool or modification I'd like to introduce. I do not know CoffeeScript and I'm very sure I won't learn it. So, I'd feel better knowing there is a build-in way to customize my own tools and introduce modifications to the widget using plain JavaScript. The tutorial "Adding new tools" is daunting.

I personally would also appreciate a simplified/more intuitive API in CT2 to my taste. But these are the things I feel would be better to share somewhere else (not is this issue).

PS Could you please help me out or at least comment with issue on StackOverflow, please? So far, I implemented Image Upload following the "Handling Image Uploads" tutorial and would like to be sure that the widget can be of help with the rest of my task of providing users with the tool for producing html markup similar to ed books with all their nested structures (Sections, Units, Chapters), tables, nested lists, notes, illustrations, references, etc.