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

Setting a global default markup #1594

Open
sebix opened this issue Feb 9, 2024 · 4 comments
Open

Setting a global default markup #1594

sebix opened this issue Feb 9, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@sebix
Copy link
Contributor

sebix commented Feb 9, 2024

When creating a new page, the user sees a long page of available markup languages:
image
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.

@UlrichB22 UlrichB22 added the enhancement New feature or request label Feb 9, 2024
@UlrichB22
Copy link
Collaborator

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:

# ENABLED_CONTENT_TYPES = ['MoinMoin', 'PDF', 'PNG', 'JPEG',] # example: restrict content types

The result looks like this:

MoinMoin_NewItem_2024-02-09

@sebix
Copy link
Contributor Author

sebix commented Feb 9, 2024

This is a nice feature, although not configurable in the settings, as far as I can see. Could we move ENABLED_CONTENT_TYPES to wikiconfig.py?

@ThomasWaldmann
Copy link
Member

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.

@sebix
Copy link
Contributor Author

sebix commented Feb 9, 2024

This dialogue is NOT about markup, but about content-type (which includes text, image, video, audio, ...).

Yes, it is related to the issued I described, but not a 100% solution.

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 depends on the use case and audience

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

No branches or pull requests

3 participants