Skip to content
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

user-friendly Markdown editor #281

Open
aidemkin opened this issue Oct 2, 2024 · 6 comments
Open

user-friendly Markdown editor #281

aidemkin opened this issue Oct 2, 2024 · 6 comments

Comments

@aidemkin
Copy link

aidemkin commented Oct 2, 2024

Hello!

Please consider implementing a user-friendly Markdown editor for business users who can use it without IT experience. The current solution is convenient only for technically experienced specialists. My proposal would allow maintaining the technical approach of using Markdown but with a more user-friendly and intuitive interface for any user.

For example, a similar approach is implemented in GitHub.

Снимок экрана 2024-10-03 в 01 20 11
@0xD0M1M0
Copy link

I can only support this issue. It is the wrong way to make a tool that is made for a whole company, just useable by the IT and geek people. Nothing I want in my company!

@0xD0M1M0
Copy link

@AyshaHakeem Could you please explain why the WYSIWYG editor was removed? Who took that decision to treat end-users with software dev stuff and remove any user-friendliness?

@weldonsantos
Copy link

Dear Frappe Wiki Development Team,

I would like to request improved support for Markdown in Frappe Wiki. Markdown is crucial for users due to several key reasons:

Ease of Use: Markdown offers a simple, intuitive syntax that enables users to format content without extensive knowledge of HTML. This is particularly beneficial for Wiki platforms where quick, accessible editing is essential for contributors of all technical levels.

Consistent Formatting: By supporting Markdown, we can ensure uniformity in content presentation across the Wiki. This provides a consistent look and feel, enhancing readability and user experience.

Seamless Conversion to HTML: Markdown content is easy to convert to HTML, allowing it to be rendered elegantly across various browsers and devices. This flexibility is crucial for exporting content and ensuring accessibility on different platforms.

Cleaner and Simpler Code: Markdown syntax is minimalistic, keeping content structured without the complexity of HTML tags. This simplicity not only improves readability but also reduces potential syntax errors that might disrupt page layouts.

Streamlined Collaboration: Markdown is widely used in collaborative platforms like GitHub, so many contributors are already familiar with it. In a Wiki environment, where multiple users work together, Markdown makes it easier to contribute and edit content, supporting a seamless collaborative workflow.

For these reasons, Markdown support would be a valuable addition to Frappe Wiki, fostering a more user-friendly and efficient experience. I believe this enhancement could significantly improve usability and accessibility for all users.

Thank you for considering this feature request. I look forward to the potential of having Markdown integrated more robustly into Frappe Wiki.

@c-l-v
Copy link

c-l-v commented Nov 9, 2024

@AyshaHakeem Could you please explain why the WYSIWYG editor was removed? Who took that decision to treat end-users with software dev stuff and remove any user-friendliness?

I would also like to ask why the editor was removed? Has any answer or explanation been given?

@0xD0M1M0
Copy link

0xD0M1M0 commented Nov 9, 2024

No. @AyshaHakeem has not answered yet.

@revant
Copy link

revant commented Nov 9, 2024

This has happened before, many apps will do this in future as well. Can happen when dependencies and libraries need to be changed for better developer as well as user experience.

Have a staging or a testing setup where you try upgrades first.

Don't unnecessarily depend on apps. More apps you depend on, more sudden changes you've to be prepared for.

If the feature is important, contribute tests so that the "sudden change" need the refactor to tests as well and you'll come to know exactly what changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants