Editable Module Headers

[roximonoxide]

Title:
Editable Module Headers

Area:
styles / customization

Summary:
User input fields to control the text headers of all modules, not just the custom text module.

Description:
Currently, the the Custom Text module allows for the user to change the module heading from the Text customization options for your journal. (The same page where you might edit other default page text such as metadata labels and navigation links). Though you can hide module headers entirely with css, other modules have no such customization options other than order and page placement. It would be exceedingly helpful to both users and communities who use their journals, and the modules available to them, differently if all other modules allowed for the user to alter the default module headings to text of their own choosing.

This might logically be implemented either from the Text page, as it already exists for the with the Custom Text module, or from the Modules page where order and organization of your modules takes place.

Poll #9210 Editable Module Headers

Open to: Registered Users, detailed results viewable to: All, participants: 68

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
39 (57.4%)

Should be implemented with changes. (please comment)
1 (1.5%)

Shouldn't be implemented.
2 (2.9%)

(I have no opinion)
26 (38.2%)

(Other: please comment)
0 (0.0%)

Comments

[ratcreature]

I have to admit that I already dislike the customized naming that exists, because for me it always makes it harder to find things. So I'm not sure I want more of that. I mean, like the people who use clever things instead of "reply". I then often have to hover to see the URL to find which link to click. Same when the profile isn't called something obvious. I can see why depending on how you use for example the link list, different module titles make sense to be more specific, e.g. I use it as a "my on other sites" list, not a "blogs I read" list, and for module titles it might be less disruptive than for navigation links, but I still like the same fields be called the same across journals.

[jeshyr]

This. I find it confusing and I worry that it has the potential to be a cognitive accessibility issue...

[montuos]

For the same reasons you note, I too am not always thrilled with the use some people make of the custom text, but honestly, I think custom module headers would be less confusing than custom navigation text. As far as I can tell, most of the modules are easily recognizable via their content, and if they are actually being used for some other purpose, I think it would be rather nice to have the additional clue.

[azurelunatic]

It's the sort of thing that a reload in ?style=mine ought to work on, in case of alterations that are too weird.

[zing_och]

I agree with ratcreature; I often get confused by custom text.

(Especially since I'm not at my best right now. I was rather disappointed that the title of this post is not actually "edible module headers"n *g*)

[pauraque]

I would like to be able to change the text. Just the other day I went to do so and was surprised that it was not possible.

It doesn't really bother me when other users have a journal that is hard for me to navigate (whether because of changed text, a wacky color scheme, or whatever) because I spend so little time actually looking at other people's journals, and I figure that the most important thing is it looks right to *them*, not to me. It's their layout and they're going to be looking at it the most, by far.

[matgb]

If you know how to play around with S2 layers, then you can do it. There's a series of properties in the Core2 layer under:
##===============================
## Text - module headings
##===============================

I've just set my page summary module to Page Contents using:

set text_module_pagesummary = "Page Contents";

at the top of my Theme layer.

@OP: Given that these are all available as varialbes in the core layer I'm surprised they're not in the wizard and think they should be.

[pauraque]

Oh, thanks. I'll look into that.

[ninetydegrees]

I also get confused by custom text but I think it wouldn't make sense to let people edit entry links and navigation links, and not modules headers.

[matgb]

Any idea why it's not in the wizard at all? Just looked through Core2 and there are variables for all of them that look like they're designed to be in the customisation wizard. Took me a bit but I just changed my page summary to 'page contents'.

[ninetydegrees]

Nope. Maybe to prevent confusion/inaccessibility until you had the permanent style=mine option.

[matgb]

Maybe, I guess. There's just quite a lot of effort put into that section with, unusually, no commenting to say why it's not live-it looks like it's an oversite and should be live already.

[manifold]

Many of our problems with custom text are easily handled with "style=mine" (we tend to use it all the time anyway because we have a css killfile in our style), but maybe the problems people have could be addressed in a more user-friendly way.

For instance, there could be an account settings option that would allow people to choose whether or not to view custom text for headers and navigation links, regardless of layout style. Then if people want to make use of custom text, they can do so freely without having a negative impact on those who have problems with it.