-
Notifications
You must be signed in to change notification settings - Fork 41
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
Netlify CMS Limitations/Options #292
Comments
Just as an FYI. The Netlify CMS only generates the markdown files. GatsyJS is the site builder, and it actually builds the pages. So whatever solution we look at for this, it likely has to have a way to be supported both in the NetlifyCMS and Gastby. |
I'm not really sure why you need text alignment. I usually only use block and the normal (left bound) one. So we are only missing block? |
It's not the most important thing in the world - it was an observation when adding captions to inline images. IMO they look better centred - both images and captions - than they do left-aligned. |
We might be able to just center images then, and maybe we can just render the alt text you should be able to set. But we might need to add a component for that in the CMS via https://www.netlifycms.org/docs/custom-widgets/#registereditorcomponent and then rendering it correctly on the blog side of things. Similar to this decaporg/decap-cms#1058 |
Right, I've been fighting a bit with the WYSIWYG and Markdown editors in Netlify CMS for a while. The issue is probably twofold:
There are also some quirks around workflow, e.g. you can't properly see an image in the preview until the post is deployed, as the images aren't moved to the correct directories before that point. @pkscout turned Deploy Previews on, which addresses much of this in that I can at least see the blog posts "live" now before we actually publish them, which is a huge help (thank you) - but we could perhaps do more.
A placeholder for my own thoughts, as much as anything...
Immediate thoughts:
I'll keep digging, but that's a starting point.
The text was updated successfully, but these errors were encountered: