[Not released][JS] Implement the Temporal proposal

[bsmth]

Acceptance Criteria

• The listed features are documented sufficiently on MDN
• BCD is updated
• Interactive example and data repos are updated if appropriate
• The content has been reviewed as needed

For folks helping with Firefox related documentation

• Set bugs to dev-doc-complete
• Add entry to Firefox release notes if feature is enabled in release
• Add entry to Firefox experimental features page if feature is not yet enabled in release

Features to document

Related Gecko bugs

• https://bugzilla.mozilla.org/show_bug.cgi?id=1519167 - released but just starting work
• https://bugzilla.mozilla.org/show_bug.cgi?id=1840374 - continuation

Other

• Check content open issues to see if any pertain to the subject matter. If there are any that can be closed because of the work, do so. If there are any that can be fixed relatively quickly because of the knowledge from completing this issue and you have time, feel free to go ahead and fix them.
• Check if glossary updates are required for the feature you're documenting - whether an existing term needs to be updated or a new term should be added.
• Check if BCD update means that content pages need to have experimental markup removed or deprecated markup added (front matter tags and macros).

[Josh-Cena]

Wow! It's coming?

@meyerweb As I recall, you have a branch for this already, right? I'm open to reviewing PRs if you make one.

[hamishwillee]

FYI @Josh-Cena we're supposed to look at this for FF116. I might start next week if no one else takes it.

[Josh-Cena]

Documenting Temporal from fresh is a huge undertaking, so you should probably use https://github.com/meyerweb/content/tree/temporal/ in openwebdocs/project#29 as a starting point. There are probably a lot of discrepancies from the current editorial conventions, but we can fix that gradually.

[hamishwillee]

Thanks @Josh-Cena - I know (literally) nothing about it yet.

EDITED @Rumyra I think we need to defer this - probably not yet ready. We should work work closely with OWD on this as Josh suggested. Needs a few people on it and is huge enough that it needs a plan.

FF looks like it is not ready either - the first bug reported is just considered "initial work". There is also https://bugzilla.mozilla.org/show_bug.cgi?id=1840374 and whatever is to follow it. This is behind a build preference: --with-temporal-api.

[Josh-Cena]

FF looks like it is not ready either - the first bug reported is just considered "initial work". There is also https://bugzilla.mozilla.org/show_bug.cgi?id=1840374 and whatever is to follow it. This is behind a build preference: --with-temporal-api.

Mmmm, I thought there was news, but maybe there isn't. Other engines (V8, JSC) are already shipping it behind prefs.

[Josh-Cena]

Apparently it's shipping flagged in FF 135. Luckily I'm on break for the next two weeks, so I'll start making plans for docs.

[hamishwillee]

Thanks @Josh-Cena - Living the dream ? :-). Hope you have a wonderful break, though it does not sound like a holiday to me!

[Josh-Cena]

Just scaffolded all the docs and now have 241 pages to be filled. Oh lala! I'm going to have fun :) Day in Epcot, night in ep-docs.

[bsmth]

Just scaffolded all the docs and now have 241 pages to be filled. Oh lala! I'm going to have fun :) Day in Epcot, night in ep-docs.

Please share so we can divide and conquer if needed, I would love to help.

[Josh-Cena]

I will put up a really draft PR once I have all the template filled in. I will probably leave guides to a second PR.

[Josh-Cena]

Closing in favor of #37515