-
Notifications
You must be signed in to change notification settings - Fork 525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Your config description and examples are quite unspecific #453
Comments
Hello, thanks for the pointer, I didn't see the one in the README, I fixed it. I also changed the indents on all documentation pages, you're right it's better when it's uniform. Just in case, you can find all configuration options on these two documentation pages |
Not completly. For example, the The readme looks great now! I think it's an real improvement here. You only misses two examples: And since yesterday, there should be an example added for |
You're right, some options are scattered around pages. They can be checked out here : |
Great! Thats better now! |
As a new user to
daux.io
it is pretty hard to find out, what config parameter are available and where to place them.At first, there is no overview anywhere, what parameters are available with a short description. You have to search all of them here on GitHub or in the documentation on many different sites. A small table would give users an overview what is possible.
On the other hand, the examples given in your documentation here on GitHub or on the official docs is very unspecific too. For example:
You always say "place it into config.json in docs folder" and give such example code:
But what you don't tell your users it, that this for example needs to be placed inside the
html
block of the config. So the example should be looked like this:It is even more confusing, because some examples have the
html
block included, as the rest don't have this. For example,inherit_index
is documented with thehtml
block:It tooke me quite a lot time now to figure out, where to place my configurations to let them take effect. The documentation of the capabilities could be much better imo.
Antoher small hint on your documentation and files:
Nearly all your
json
files use a different intend. Your examples uses atap
, yourcomposer.json
uses four spaces, yourpackage.json
uses two spaces, and so on. The mostly used type out there is to use two spaces, like you did in yourpackage.json
already. This is better readable too, imo. Maybe use a default type of intention here.As taken from the example above:
The text was updated successfully, but these errors were encountered: