Feature request: Option to disable the anchor field

[arnaudjuracek]

First of all, thank you for your plugin. It is so simple that I may use it by default on all my new Kirby projects, until it ends up being eventually integrated to the Kirby core.

It would be really nice to have a config option to disable the anchor field, to allow building simpler websites for unskilled clients who do not need to know what an anchor is.

[gearsdigital]

You are very welcome @arnaudjuracek! Glad you find my plugin useful 🙏🏻

I like your idea and I'm going to implement this not only for the anchor, but also for every other field. It's a bit more challenging to keep the layout consistent. Not every field takes the full width, but I'm confident to find a proper solution :)

[gearsdigital]

@arnaudjuracek Before I'm going to start to work on this issue I need to clarify what do you mean by disable.

1. The field is visible to the user, but disabled, so that he can't add any input

2. The field is invisible to the user and removed completely

[arnaudjuracek]

IMHO the UX is better for the user when the field is completely hidden, but you may have other scenarios in mind where disabling the field makes more sense ?

Thanks for your time.

[gearsdigital]

Okay, let's do both ^^ The user can decide whether he wants to disable or hide a field. Thanks for your input!

[gearsdigital]

:tada: This issue has been resolved in version 3.2.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

[gearsdigital]

@arnaudjuracek Let me know if this feature works for you :)