Documentation and Community

[markeaston63]

What we need is two things:

1. Documentation on HugeMCE and lots of it. Googing for info about how to use TinyMCE 6.8.3 is difficult as so much info relates to other versions. In using HugeMCE I have had to sift through all that as I resolved issues. ANd a lot of misinformation as well. I am willing to make a start on this documentation as I am doing it internally at my company anyway. So I may as well do it here. ie https://github.com/hugemce/hugemce-docs - everything there currently is for TinyMCE - eg git clone git@github.com:tinymce/tinymce-docs.git
2. We (Naverisk) are committed to HugeMCE and so will be willing to be active in this community and with resolving issues. We need an active community.

[markeaston63]

So are you all happy if I start working on this? - Updating the docs ...

[carlosmintfan]

Sure, thank you very much! However, what exactly is out-of-date there and what type of misinformation? I'm interested. And you'll have to see for yourself that you do all the stuff correctly, there is the main branch forked from TinyMCE which does NOT contain the actual docs; rather, the docs branch, forked from the tinymce/6 branch, I think, and the scripts in the main branch clone the branch containing the real docs, however, it may still clone from tinymce and then from a different name (tinymce/6 branch in TinyMCE docs repo is named docs in my repo). So there may be some confusion for you at first. I'll start working on it soon.

[carlosmintfan]

I hope you should be okay with licensing your contributions to the docs under MIT in addition to CC BY-NC-SA. I don't know if it's viable, but maybe we could buy the docs from TinyMCE under the MIT license (and code snippets included in it preferably under BSD zero clause to eliminate all legal issues that could occur when copy-pasting them from the docs into a project, without attribution), it would be very very great; we could then hopefully reimplement their AI plugin and take all prompts etc. from the docs - but I don't know if they'd sell it like that and I myself don't have the money for it.

[markeaston63]

I have read the discussion on the TinyMCE forum. ie tinymce/tinymce#9453. We are very supportive of HugeMCE. So yes we are OK.

The issues with the docs is more in relation to the tinymce docs in general. Even the 7.3.0 docs are out of date. As a small example in their paste page they have some code that has as an argument the plugin! But as we know in 6.0 paste was moved to core. And hence the argument is the editor.

But the docs also are in relation to TinyMCE - not HugeMCE so there are a few issues there.
The docs in relation to paste are full of ssues.,

I will work at your direction carlos. Very happy to assist this effort.

[carlosmintfan]

If you feel like it, you could take a look at fixing tinymce/tinymce-docs#3436. Note that it seems partly a problem of TinyMCE itself (not the docs), that when bundling instead of including the TinyMCE script directly (I'll have to search for the condition it tests or when it behaves like that in its code) it simply doesn't create an iframe with its own styles but rather just a div and applies the styles to the global document, which is...not nice.

[carlosmintfan]

Hey @markeaston63, may I ask how it is going? I now have more time to work on HugeRTE.

[markeaston63]

Hey Carlos, I have just completed on Thursday our "NavEditor" epic (using TinyMCE 6.8.3). Phew a big job and a LOT of features! Have done a lot of work with QA already but it will be deployed to our QA environment and be in test next week. I am having a good break this weekend - I was putting in 60 hour weeks. But yeah, my knowledge of the product has grown immensely and I will have much to contribute! I'm having a good break this weekend - will be keen to help with HugeRTE moving forward. I have the blessing of my company to do so. I will look back at the HugeRTE forum next week and deal with the things I said I would. Cheers Mark

…

On Sat, 23 Nov 2024 at 04:02, carlosmintfan ***@***.***> wrote: Hey @markeaston63 <https://github.com/markeaston63>, may I ask how it is going? I now have more time to work on HugeRTE. — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM64TDGHB2EACLYUB4U4WST2B5BRXAVCNFSM6AAAAABOORGOA2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZVGAYTGMY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[carlosmintfan]

Hi Mark,
thank you for your willingness to contribute. Just a gentle ping as your message is "3 weeks ago" now - but yeah, it also often takes long until I do / complete things here LOL…
Regarding the docs, I‘ve just archived my fork of the TinyMCE docs, LOL, but yes, I‘d like to start from scratch…however, did you modify the docs from https://github.com/tinymce/tinymce-docs or created your own documents? It’d just be great if much of your docs could not be considered a derivative work of the TinyMCE docs but rather your own work (though of course not for the whole editor yet) so we can license it MIT (and codesamples better CC0, Unlicense or 0BSD) instead of CC BY-NC-SA.
I created a GitHub wiki today at the HugeRTR repo, then disabled it again. What do you think would be the best way to host our docs? (If we start from scratch and don‘t take the ones from TinyMCE.) GitHub wikis have the problem that anybody can edit without review or only I can edit and nobody can propose changes (I saw no PR feature). So maybe an own repo for the docs as markdown or host them in the HugeRTE repo directly?

[carlosmintfan]

I have created a dedicated repo for the docs: https://github.com/hugerte/hugerte-docs.

[carlosmintfan]

Dear @markeaston63, where have you gone? 😒

[carlosmintfan]

Great you‘re back again. https://github.com/orgs/hugerte/discussions/37#discussioncomment-11766520

[markeaston63]

Yes and when I am back I am developing a SmartDragAndDrop plugin for HugeRTE. We need it, for example, to determine whether the file should be attached or embedded. AND I promise promise I will make myself available to your efforts.

…

On Wed, 8 Jan 2025 at 11:57, carlosmintfan ***@***.***> wrote: Great you‘re back again. hugerte/hugerte#37 (comment) — Reply to this email directly, view it on GitHub <#5 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM64TDEGSMS33RGTC2TA5CL2JRLV7AVCNFSM6AAAAABOORGOA2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZWGY2TKNA> . You are receiving this because you were mentioned.Message ID: ***@***.***>