In the UI, tell users why a post can't be saved based on known structural post requirements

[chackomathew]

I've been trying to create a new post for quite some time, but somehow the save button is missing. This is my hubpress blog repository: https://github.com/chackomathew/blog

[patrikwm]

Same here. my save button missing.

[anthonny]

Hi @chackomathew, @patrikwm

The minimum requirement to save or publish a post is a title.
Could you try with this content:

= My title

My content

[jaredmorgs]

https://hubpress.gitbooks.io/hubpress-knowledgebase/content/write/titles_and_headings.html
covers what Anthonny is saying.

On Fri., 11 Nov. 2016, 07:00 Anthonny Quérouil, notifications@github.com
wrote:

Hi @chackomathew https://github.com/chackomathew, @patrikwm
https://github.com/patrikwm

The minimum requirement to save or publish a post is a title.
Could you try with this content:

= My title

My content

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#459 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6J2Y61Bs_PI-ZvAZq38oiLovCwnK_pks5q84X9gaJpZM4KuUQm
.

Sent from Mobile.

[chackomathew]

My bad, I didn't read FAQs before raising an issue. I agree with header validation, but better user experience?

[jaredmorgs]

We've improved the first post experience in 0.7.0 by adding in some template info which you can uncomment and use.

I agree that some better validation would be helpful, or maybe even a link to the troubleshooting article on the knowledgebase.

How do you think we could improve this for users @chackomathew ?

Update now and give it a go.