SSWConsulting / SSWConsulting/SSW.Rules
🔥Netlify CMS | Remove the title field from the image widget
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
(Checked by Brady)
Hi Myself,
As per the email including @pierssinclairssw,@bradystroud, @tiagov8, @adamcogan, @theixdev with subject: SSW Rules - Is Title needed for images, the "title" field on the Image widget isn't used and should be removed.
- Investigate the best option below and implement it
Option A: Create a custom widget (recommended) 🚀
Create a custom widget that is basically a copy of the default Netlify CMS image widget without the "Title" field.
Pros:
- This could be quicker
- Allows for more customization - allowing us the ability to implement @tiagov8's suggestion to change the name of the alt text field to "Figure"
Cons:
- Might require extra work
- Need to investigate if we can add custom widgets to the markdown widget
Option B: Add an option to hide the title from Netlify CMS📉
Create a pull request with Netlify CMS to add an option to check if title should be used.
Pros:
- Potentially helps the community
- No redundant code
Cons:
- This would require creating a PR to Netlify CMS repo
- This could take more time or not be accepted
- Further customization would require repeating this process

Figure: Title field on the Image Widget
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Netlify CMS image widget integration and checking how it is embedded in the markdown widget. Compare the custom-widget and upstream-option approaches described in the issue; done means the image widget no longer displays a Title field while image editing still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- content, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100