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
Alt/caption for image field types #827
Comments
OK, so I just noticed that this is already implemented for imagelist field types. So really the issue/question is solely related to image field types. |
If you can specify in your contenttype.yml whether or not you want to have the 'alt' and 'title' fields in the "edite record" screen, that'd be cool to have. I'd favor 'title' over 'caption', though.. Just to keep it in line with the attributes in the Is this something you could do, and make a pull-request for? |
It is, I am still learning the Bolt code base though so any quick pointers would speed this up for me. Agreed on 'title' too. |
If we were to split up the work that needs to be done for this, the following things come to mind:
Let me know if you get stuck. I'll gladly help! |
You, Sir, are awesome... That is exactly what I need. I agree about backward compatibility, and is largely why I filed this instead of just trying something myself first. I shall make a start tomorrow morning (GMT) and see where I get to! |
RFC/TOL So for the Contenttype part I am thinking something like this:
Advantage I see to this approach is that if we start from the beginning by using an array of attributes, extending how we implement them in Bolt later on is less painful. |
I wonder how useful "usemap" and "crossorigin" would be in this context, though.. |
In current context, "tits on a bull" as we say in Australia. My thought was to do something that was forward compatible with anything that may be introduced into HTML5 that we haven't thought of yet and in turn not have to jump though hoops with Bolt in the future... Sort of "Why would anyone need more than 640KiB of RAM?" thing |
Fair enough! :-) |
Nitpicks very welcome on that patch... It should be a very clean try albeit any tabs or the like that snuck in. Obviously documentation will need to be updated, but give it took me 7 weeks to the day to get this done in a couple of hours, I am sure I can remove one more finger from said spot and write that up too :-) |
Feature submitted in #996 |
The first comment says "Image and imagelist". Am I correct that this feature is available for image-fields only, yet? At least I can't find a way to enter a title for an imagelist-item (using bolt 2.2.7). Would be nice if this could get added. |
Well that's embarrassing. ;) Thanks! |
Nah, it's just not obvious… and that popover text in the i could be better |
is there by any chance that we could add like a description and a link to the images in the imagelist? :) |
@edanao If you want more fields in the imagelist you might want to look into making it a repeating field with an image field and the additional fields that you want. So in your repeater you'd have a imagefield, a textfield, a textarea and a field for your link, then it should work pretty much how you want it to. |
thank you @SahAssar !!! |
Hello! By the way, is it possible to call alt attribute with this statement: |
@MikSDigital This issue is 3 years old and that sort of question is probably better for our slack/irc or the discusssion boards, but to answer your question that should work, yes. |
Hey mate. Nope, this is a limitation of |
Hey @GawainLynch That's a pitty :(. Then I think using repeater fields is the best way to go for this. Looking forward for those improvements when v4 lands :). Thanks 👍 |
Image and imagelist field types should have an additional text field to allow for linked caption/alt text to be associated with the image.
The alt="" has SEO importance and it would be nice to be able to have a caption frame automatically generated for the image that can be styled by the selected/used user theme.
Something like this would be cooler than ice:
The booleans will give template designers to option to use or ignore.
The text was updated successfully, but these errors were encountered: