Incomplete upload on CTAN and incomplete documentation.

[quark67]

The example directory (and Makefile file) is missing on CTAN (see this screenshot from https://www.ctan.org/tex-archive/macros/latex/contrib/essaykit: we read an example directory on the file Structure, but the example directory is not in the files).

Moreover, the examples files advanced-example.tex and complete-document.tex are also missing on GitHub (and in GitHub, the file basic-example is .txt instead of .tex):

The pdf documentation is very incomplete. Were are the describtions of the [options] of the commands?

And the prefefined colors?

They are described in the README file, but not in the PDF file, which is the documentation for the users of this package (for example, with texdoc essaykit in CLI).

Note that the key title is missing in the previous list (Customizable Options), but defined in the code:

\define@key{ek}{title}[]{\def\ek@title{#1}}

Also, why a sharelatexcolour color?

\definecolor{sharelatexcolour}{HTML}{882B21}

ShareLaTeX a been bought by Overleaf at July 2017!

And why greycolour (Colour) and box-color (Color, without u)? For users, it's better to choice between color and colour, not using the two forms.

I hope you can correct all theses missing items and typos. Thanks.

[Swifterhtmler]

Thank you for the detailed report! You're right on all points.

I've already:

• Removed the example directory and Makefile references from the README (remnants from v0.1)
  I'm currently working on:

• Updating the PDF documentation to match the README's completeness (including all options, colors, and the missing title key)

• Standardizing color naming to use consistent spelling (color vs colour)

• Ensuring GitHub and CTAN distributions are in sync (had had issues with mixing up production version folder)

Regarding the inconsistencies you found:

• The basic-example.txt vs .tex naming and missing example files will be corrected
• The sharelatexcolour reference will be removed as well

I'll push these updates within next 2-3 weeks. Really appreciate you taking the time to document all of this so thoroughly—it's incredibly helpful for improving the package.