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

[Content Author Module 2: Structure] [low] Avoid metaphors #594

Open
iadawn opened this issue Jul 1, 2022 · 6 comments
Open

[Content Author Module 2: Structure] [low] Avoid metaphors #594

iadawn opened this issue Jul 1, 2022 · 6 comments
Labels
question Further information is requested

Comments

@iadawn
Copy link

iadawn commented Jul 1, 2022

In the Headings topic is it worth mentioning something about avoiding metaphors?

@daniel-montalvo
Copy link
Collaborator

Hey @iadawn

Thanks for this feedback.

I am not sure where this would be getting at.

If it relates to Making Content Usable for People with Cognitive and Learning Disabilities -- Amy Scenario 3: Designs that Make Use of Abstract Imagery and Metaphors, why would this only apply to headings?

Would you give me an example of what you would expect here?

@daniel-montalvo daniel-montalvo added the question Further information is requested label Jul 6, 2022
@daniel-montalvo daniel-montalvo added done Done. Will close when related PRs are merged. and removed done Done. Will close when related PRs are merged. labels Jul 15, 2022
@iadawn
Copy link
Author

iadawn commented Sep 22, 2022

Metaphors in headings are more problematic because they serve to introduce the section. But if the metaphor is not understood then the value of the heading as that introduction is significantly reduced. It's not that it only applies to headings but that, as signposts, headings have more going on than just the text.

Perhaps an option would be to change:

write descriptive and meaningful heading text based on the heading purpose

to something like:

write descriptive and meaningful heading text, avoiding metaphor and abstraction, based on the heading purpose or following text content

@daniel-montalvo
Copy link
Collaborator

Thanks @iadawn

I am a bit uncomfortable with "avoid metaphors". I think it can potentially lead to contradictory/wrong advice.

What if the heading needs to be a metaphor itself, for example when you need to explain its meaning in a poetry review? Then you would probably need to put that metaphor in the heading to explain it in the content, so it would not be a good advice to avoid it!

A bit of an edge case, but still something plausible.

We could use another adjective to communicate that you should avoid abstraction/metaphors, like "concrete", "precise", or similar. Or what I'd prefer, "easy to understand", which would be a nice cross-reference to the first module.

The commit above changes it to:

write descriptive and easy to understand heading text based on the heading purpose or the following text content

@iadawn
Copy link
Author

iadawn commented Sep 22, 2022

I am happy with the rewrite for the purposes of publication. I feel there is something still there though. For example, could use something like:

refrain from using non-literal heading text

'Refrain' is a nice word as it isn't as absolute as 'avoid' or 'don't'! :)

@daniel-montalvo daniel-montalvo added Future iteration and removed question Further information is requested labels Sep 22, 2022
@daniel-montalvo
Copy link
Collaborator

Thanks @iadawn

Will mark then as "future iteration".

@daniel-montalvo
Copy link
Collaborator

I like "liberally" because it points students to what they have to do instead of what they don't have to do.

Could be:

write clear and meaningful heading text that literally describes the purpose of the section content

@daniel-montalvo daniel-montalvo added question Further information is requested and removed Future iteration labels Sep 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants