Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions base.css
Original file line number Diff line number Diff line change
Expand Up @@ -121,3 +121,25 @@ td {
color: #666;
text-align: left;
}
.enum {
-webkit-column-gap: 4rem;
-moz-column-gap: 4rem;
column-gap: 4rem;
-webkit-column-rule: 1px dotted #ddd;
-moz-column-rule: 1px dotted #ddd;
column-rule: 1px dotted #ddd;
}
@media (min-width: 25rem) {
.enum {
-webkit-columns: 2 10rem;
-moz-columns: 2 10rem;
columns: 2 10rem;
}
}
@media (min-width: 39rem) {
.enum {
-webkit-columns: 3 10rem;
-moz-columns: 3 10rem;
columns: 3 10rem;
}
}
79 changes: 78 additions & 1 deletion content/index.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -296,13 +296,90 @@ yet are broadly used and agreed upon.
* `profile:first_name` - [string](#string) - A name normally given to an individual by a parent or self-chosen.
* `profile:last_name` - [string](#string) - A name inherited from a family or marriage and by which the individual is commonly known.
* `profile:username` - [string](#string) - A short unique string to identify them.
* `profile:gender` - [enum](#enum)(male, female) - Their gender.
* `profile:gender` - [enum](#enum)(male, female, other – see the complete [gender enum](#gender_enum) list) - Their gender.

<a name="type_website" href="#type_website">`website`</a> - Namespace URI: [`http://ogp.me/ns/website#`](http://ogp.me/ns/website)

No additional properties other than the basic ones.
Any non-marked up webpage should be treated as `og:type` website.

#### <a id="gender_enum" href="#gender_enum">Gender enum</a>

The following are all the gender types previously identified and implemented on Facebook. You can also opt to leave out the field entirely as these properties are optional anyway.

<ul class="enum">
<li>agender
<li>androgyne
<li>androgynes
<li>androgynous
<li>asexual
<li>bigender
<li>cis
<li>cis female
<li>cis male
<li>cis man
<li>cis woman
<li>cisgender
<li>cisgender female
<li>cisgender male
<li>cisgender man
<li>cisgender woman
<li>f2m
<li>female to male
<li>female to male trans man
<li>female to male transgender man
<li>female to male transsexual man
<li>ftm
<li>gender fluid
<li>gender neutral
<li>gender nonconforming
<li>gender questioning
<li>gender variant
<li>genderqueer
<li>hermaphrodite
<li>intersex
<li>intersex man
<li>intersex person
<li>intersex woman
<li>m2f
<li>male to female
<li>male to female trans woman
<li>male to female transgender woman
<li>male to female transsexual woman
<li>man
<li>mtf
<li>neither
<li>neutrois
<li>non-binary
<li>other
<li>pangender
<li>polygender
<li>t* man
<li>t* woman
<li>trans
<li>trans female
<li>trans male
<li>trans man
<li>trans person
<li>trans*female
<li>trans*male
<li>trans*man
<li>trans*person
<li>trans*woman
<li>transexual
<li>transexual female
<li>transexual male
<li>transexual man
<li>transexual person
<li>transexual woman
<li>transgender female
<li>transgender person
<li>transmasculine
<li>two* person
<li>two-spirit
<li>two-spirit person
<li>woman
Comment on lines +311 to +381
Copy link

@circl-lastname circl-lastname May 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No </li> closing tags which is theoretically OK because browsers will fix it up, but they are actually needed per HTML spec

</ul>

---
## <a id="data_types" href="#data_types">Types</a>
Expand Down