search

tdwg / website-migration-2022

Website migration 2022
0 stars 0 forks source link

Sentence case vs Title Case #27

Closed peterdesmet closed 1 year ago

peterdesmet commented 1 year ago

@gkampmeier @stanblum What is the recommendation for titles on the TDWG website? Titles are page titles, page headings (h2, h3), and menu items.

Currently a mix of the two is used. See https://medium.com/@jsaito/making-a-case-for-letter-case-19d09f653c98 for the benefits of each.

gkampmeier commented 1 year ago

@peterdesmet sentence case

TL;DR Nice article--he does, however, screw up the initial definition of Title Case, which he demonstrates later. But in so doing, points out the perils of title case: what are the rules (there are many style guides)? For our community, an international one, it likely makes more sense to use sentence case--mind you, before reading that article, I might have pushed back otherwise. The rules are simpler, as long as you can call out the text in an h-heading. Although I seem to remember that different h-headings can have different rules (title for h1&2; sentence for h3&4)—but we don't need to go there.

peterdesmet commented 1 year ago

Thanks, I agree, it is indeed simpler.

TDWG standard names will remain capitalized:

Darwin Core
Global Genome Biodiversity Network

But what about the following terms:

executive committee
functional subcommittee
- fundraising and partnership
- time and place
- technical architecture group
- infrastructure
- outreach and communications
task group
interest group
maintenance group
code of conduct
diversity and inclusion statement
liability disclaimer and release
...

My preference would be that those are lowercase.

E.g. in a title or sentence:

TDWG members of the executive committee participated in the BiCIKL hackathon in Meise
The Audubon Core maintenance group has opened public comment on the proposal to add two vocabularies to the Audubon Core standard.
 Interest and task group working sessions

Or as sentence case menu items:

About
---
Executive committee
---
Functional subcommittees
- Fundraising and partnership
- Time and place
- Technical architecture group (TAG)
- Infrastructure
- Outreach and communications
---
Code of conduct
Diversity and inclusion statement
gkampmeier commented 1 year ago

@peterdesmet I agree that Standard names should remain capitalized. I would suggest the following (I have not made things 3 deep, but could see advantages to this in some cases). Still noodling here, but...

About

†Technically, the Exec includes FSc (as well as Regional Reps, which might be encouraged to have more of a presence on the website). However, there are a bunch of historical background things currently as cards hanging off of the Exec page, which we want to be able to preserve under a history (likely its own new section).

†† should this be "Branding Guidelines" with the logos as resources?

peterdesmet commented 1 year ago

Thanks for the suggestion on the about menu.

  1. I do notice you are using Title Case (rather than the suggested Sentence case) for that menu. Is that a result of copy/pasting or intended?
  2. Can you indicate what we should recommend for the terms (executive committee, interest groups, etc.) I listed in https://github.com/tdwg/website-jekyll/issues/27#issuecomment-1327577363? Can we use lowercase for all these? That would at least avoid the current variations like these:

Functional subcommittee for Outreach and communications chair

The motivation, mission and responsibilities of the functional subcommittee are explained on the subcommittee’s page. The chair provides leaderships on outreach & communications for the whole of TDWG.

Functional subcommittee for Funding and partnerships chair

The motivation, mission and responsibilities of the functional subcommittee are explained on the subcommittee’s page. The chair provides leaderships on Fundraising and Partnerships for the whole of TDWG.

Regional Representatives: North America, Africa, Asia & Europe

Regional representatives give voice to the members, institutions, and projects in their region, and collectively provide a global perspective to the Executive Committee. As members of the Executive Committee, regional representatives have responsibility for the oversight of TDWG and the authority to approve/decline strategic initiatives, budgets, and all aspects of operations and activities. The Executive Committee also approves or declines the formation of Interest and Task Groups, as well as the ratification of standards and best practice specifications produced by Interest and Task Groups.

I would have all bolded letters above be lowercase.

gkampmeier commented 1 year ago

@peterdesmet yes it was intentional because these are proper names for groups and policies. I don't think that these named entities should be lower case because we are referring to a particular entity/proper name (TDWG Executive Committee) not just any old exec.

These are different from other sorts of titles for headings, to me. If I were to refer to the Executive Committee (meaning TDWG Exec) or the Program Committee (not the concept of a program committee), there is a difference. It is harder for the reader to know if you don't capitalize these. The practice of putting everything e e cummings is not a comfortable space for me.

stanblum commented 1 year ago

+1 for capitalizing proper nouns (names). The problem I have is determining what is part of the name; e.g.,

On Gail's menu items and grouping:

Overall, I like the grouping and order; would just suggest that "Contributing to website" and "Logos" aren't the same kind of Process and Procedures as the "TDWG Process" and "Review Manager Guidelines". Those are names of documents. Also, if Steve Baskauf's suggestion is developed, "Procedures" might become a top-level menu item.

I don't think "Incorporation and Status" is the name of something, so leave status lowercase, right?

peterdesmet commented 1 year ago

I agree with Stan that we should define how to capitalize those groups (Functional Subcommittee vs Functional subcommittee, Interest Group vs Interest group). I think in most cases we have chosen to capitalize both, and we could stick to that, but we should have a clear list.

I would not capitalize roles and policies, as that can get unwieldy, so I prefer deputy chair, convener, representative, code of conduct. The context is almost always clear in sentences.

In the menu Gail suggests, I would thus write (capitalizion changes only):

Incorporation and status Policies and statements Terms of use Code of conduct Diversity and inclusion Liability disclaimer and release - COVID-19 Process and procedures TDWG process (arguable, since also IG?) Review manager guidelines

gkampmeier commented 1 year ago

@peterdesmet I am OK with the capitalization changes you list just above and the idea of having a clear list of how groups should be capitalized. I think that if you refer to a specific person in a role, that this should be capitalized, however (e.g., Ely Wallis is Deputy Chair of TDWG; Holly Little is Representative for North America). Similarly, referring to TDWG's Code of Conduct, I would capitalize it because it is not just a code of conduct but our Code of Conduct.

You mention that "TDWG process" is also the title of an IG, but this document is an output from that IG. You could change the wording to TDWG framework, but I think that is more opaque to the reader. @stanblum This took me back to the Process IG webpage, which has broken links and a misuse of capitalization for Lee belbin[sic] ;)

stanblum commented 1 year ago

To my understanding, the "TDWG Process" is a named thing, like our Constitution, so Process should be capitalized.

On Fri, Nov 25, 2022 at 3:31 PM Peter Desmet @.***> wrote:

I agree with Stan that we should define how to capitalize those groups (Functional Subcommittee vs Functional subcommittee, Interest Group vs Interest group). I think in most cases we have chosen to capitalize both, and we could stick to that, but we should have a clear list.

I would not capitalize roles and policies, as that can get unwieldy, so I prefer deputy chair, convener, representative, code of conduct. The context is almost always clear in sentences.

In the menu Gail suggests, I would thus write (capitalizion changes only):

Incorporation and status Policies and statements Terms of use Code of conduct Diversity and inclusion Liability disclaimer and release - COVID-19 Process and procedures TDWG process (arguable, since also IG?) Review manager guidelines

— Reply to this email directly, view it on GitHub https://github.com/tdwg/website-jekyll/issues/27#issuecomment-1327929430, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACKZUDIW3JAIZ36ORLNZLA3WKFD6BANCNFSM6AAAAAASLHAIMA . You are receiving this because you were mentioned.Message ID: @.***>

peterdesmet commented 1 year ago

Note: my preference would be to not capitalize roles, as I find it rather unwieldy to have:

Mareike Petersen, Chair of the Functional Subcommittee of Outreach and Communications

But I can adapt. 😄

Most of all, can you (@gkampmeier or @stanblum) provide a list of words that should be consistently capitalized? That should help me and others in reviewing/contributing content for the website.

gkampmeier commented 1 year ago

@peterdesmet @stanblum I've started a Google doc in the TDWG docs > Guidelines > Capitalizations Guidelines - TDWG Website. Suggestions for how it should be organized are welcomed.

peterdesmet commented 1 year ago

I have tried to stick to the rules in the document: