Skip to content
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

Field Instructions for Entry Title #1790

Closed
shbchk opened this issue Feb 5, 2022 · 5 comments · Fixed by #2562
Closed

Field Instructions for Entry Title #1790

shbchk opened this issue Feb 5, 2022 · 5 comments · Fixed by #2562

Comments

@shbchk
Copy link

shbchk commented Feb 5, 2022

I could really use Field Instructions for the Entry Title. Why is it the only field that don't have it?

@shbchk
Copy link
Author

shbchk commented Feb 5, 2022

Maybe, ability to add (or override, in case it exist in field settings) Field Instructions can be added in Publish Layouts?

@shbchk
Copy link
Author

shbchk commented Feb 5, 2022

Like this:
ssss

@robsonsobral
Copy link
Contributor

We can already customize the title field per channel. To customize its instructions isn't a bad idea.

This looks like a feature for a PR.

@blue-dreamer
Copy link

Can we add the ability to add title overrides and instructions to all core fields, Entry/Expiration date, Statuses etc, This would be handy to describe what those fields do, e.g. if I'm using Entry/Expiration dates for events it's handy for less savvy clients to understand what each field is for.

And while we're talking field instructions it'd be super handy to add a instructions for category groups as well.

@tboelskifte
Copy link

Also, if we could add instructions to the Title field, we could avoid this:

https://www.dropbox.com/s/coa6exw9wieoswq/ee-title-field-misalignment.jpg

This of course only happens when changing the layout for a channel, to have the Title and URL Title on the same line. But for us with medium-strength OCD, it's an abomination ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants