Documentation Fork

[jpmc]

I noticed that in your README that you still link https://docs.dropzone.dev/ as the "Full Documentation".

I believe that there should be a fork of the documentation gitbook, a freebie github.io page would be fine, doesn't need a competing domain name.

I suggest this for two main reasons, though there could be more justification to be found:

1. What if the original Dropzone documentation disappears one day?
2. What if a bugfix or feature in this fork changes something enough that the documentation is incorrect (parameter name changed, required config option removed or added, etc.)

I would still perhaps link the original docs as well for sure, not sure how to handle that or if it would be too confusing. Some suggestions:

• "Full documentation" is the new/cloned docs, "Original Documentation" is the existing https://docs.dropzone.dev link.
• Just "Full documentation" pointing to the new/cloned docs, no old link.
• "Full Documentation" new, but "Legacy Documentation" for the old.
• Keep https://docs.dropzone.dev as the "Full Documentation" link and just add your cloned one as "Documentation Mirror"

[NicolasCARPi]

Hello James,

You don't need to argue your point. I fully agree. It was not done yet because it was not the priority, but thank you for opening this issue. I'll need to look into adding the doc in this repo.

I'll obliterate any mention of the old documentation.

[NicolasCARPi]

Unfortunately, it seems the source code for the doc is not public :/ (unless someone can point me to it?)

So for the moment it's best to leave it like that, but that means someone will have to write docs from scratch.

[stephencmorton]

Has anybody contacted @enyo Matt Simon, the original author, to see if he'd provide the help?

[NicolasCARPi]

Just sent this email to him:

[Aduffy]

When is a fork not a fork?

@NicolasCARPi first off thank you for maintaining this fork. In light of Mat not ever answering any queries regarding his plans for the original dropzone.js - It has been several years now: perhaps it is time that this version became its own project separate and distinct from the original (With its own documentation)

[NicolasCARPi]

@Aduffy I agree, but writing the doc from scratch isn't really something I have time to dedicate to. I'll probably get around it eventually, but community help would be welcome ;)

[Tuanis]

Connected to the issue of maxFileSize units:
There also seems to be a discrepancy between filesizeBase which by default seems to be 1000 (in options.js), but the error (in dropzone.coffee) is using the MiB units instead of MB
dictFileTooBig: "File is too big ({{filesize}}MiB). Max filesize: {{maxFilesize}}MiB."