Hey @chema
, I'm Lisa, lead product designer here at Forem.
I've just left a comment in this related post of questions/ideas that would serve the same user needs.
What it seems like a user needs is:
When someone writes a post, they want to know what their post looks like so that they have confidence of what they're writing before they publish it live.
It's something we can accomplish with splitting the view to show a markdown preview. But a WYSIWYG editor also accomplishes the same goal. With these two directions in mind, we must decide which one is better for our platform and our community. Knowing that the long-term ambition of Forem is to extend beyond the developer ecosystem (and thus, the world of people who aren't familiar with Markdown), we're likely going more with a WYSIWYG approach.
Hey this is Lisa, lead product designer here at @forem
.
This is DEFINITELY in our roadmap for this year! But I want to share with you the complexities within this because this is where we have many product & technical questions we'd need to flesh out.
How does this more non-dev friendly editor interact with our existing editor and that infrastructure?
Do we take on the more "Medium" approach (preview what you write) or more the GitHub approach (explicit write / edit mode with markdown syntax embedded within write mode)?
Of these approaches, which could work most optimically on small-screens/mobile phones?
How does a user change their settings here?
For all these reasons, this is a larger scope project to untangle the complexities here. When we approach product development here around Q3 2021, we will make an effort to share both product approaches (via interactive demos) to get feedback and validate its utility. Hope this is helpful context.
Hey @chema , I'm Lisa, lead product designer here at Forem.
I've just left a comment in this related post of questions/ideas that would serve the same user needs.
What it seems like a user needs is:
It's something we can accomplish with splitting the view to show a markdown preview. But a WYSIWYG editor also accomplishes the same goal. With these two directions in mind, we must decide which one is better for our platform and our community. Knowing that the long-term ambition of Forem is to extend beyond the developer ecosystem (and thus, the world of people who aren't familiar with Markdown), we're likely going more with a WYSIWYG approach.
Hey this is Lisa, lead product designer here at @forem .
This is DEFINITELY in our roadmap for this year! But I want to share with you the complexities within this because this is where we have many product & technical questions we'd need to flesh out.
write/editmode with markdown syntax embedded withinwritemode)?For all these reasons, this is a larger scope project to untangle the complexities here. When we approach product development here around Q3 2021, we will make an effort to share both product approaches (via interactive demos) to get feedback and validate its utility. Hope this is helpful context.
Cheers 🌱
Wow so great! It would be nice to have both 🙊🙈 (I prefer MD to be honest) but yeah! WYSIWIYG seems to be the best option 🚀