-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
Setting a global default markup #1594
Comments
There is also issue #1500 related to limiting the available content_types. Wiki administrators may prefer to restrict the markup language to a specific one, as users are trained to use that particular language. The solution is still under development and is not documented. You can comment out the following line if you want to test it: moin/src/moin/items/content.py Line 82 in 7792aa9
The result looks like this: |
This is a nice feature, although not configurable in the settings, as far as I can see. Could we move |
This dialogue is NOT about markup, but about content-type (which includes text, image, video, audio, ...). So while the list could be shorter or differently worded, it must include all sorts of CTs, not just text markups. Not offering something the user wants might be a bigger problem than offering some additional stuff the user does not want. |
Yes, it is related to the issued I described, but not a 100% solution.
yes, it depends on the use case and audience |
When creating a new page, the user sees a long page of available markup languages:
For advanced users, this can be very handy. Beginners and users with average technical backgrounds need help figuring out what to do here. The usability can be improved by defining a preferred markup language system-wide.
This is also very handy to enhance consistency in some setups.
The text was updated successfully, but these errors were encountered: