You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's been a while since the main Symphony website has been designed and I'd like to raise the question how we like to set up the user comment form?
I often notice that users have problems to post code snippets and block quotes. Attaching files needs a bit of luck, too.
When I think of a modern comment form, I'd expect drag and drop attachments and easier styling options. Maybe – as we are providing our own XSL service – it would be neat to tighter integrate xPathr with the comment form. Still things should be clearly laid out.
Which other places besides the forum/blog make use of such form?
Ideas, wishes?
Mockups, maybe?
The text was updated successfully, but these errors were encountered:
Embedding snippets would be really great, I'd expect it to work much like how github let you embed gists. I don't think we should prioritize anything which is upload related, there are tons of (good) services for that and people won't complain if they can't upload an image directly to getsymphony.com. Do you have any markdown editor in mind or do you think it's better to keep it simple and just provide a preview pane as seen in github comments?
@symphonycms/symphony-network:
It's been a while since the main Symphony website has been designed and I'd like to raise the question how we like to set up the user comment form?
I often notice that users have problems to post code snippets and block quotes. Attaching files needs a bit of luck, too.
When I think of a modern comment form, I'd expect drag and drop attachments and easier styling options. Maybe – as we are providing our own XSL service – it would be neat to tighter integrate xPathr with the comment form. Still things should be clearly laid out.
Which other places besides the forum/blog make use of such form?
Ideas, wishes?
Mockups, maybe?
The text was updated successfully, but these errors were encountered: