A repository template for ECMAScript proposals.
Please ensure the following:
- You have read the process document
- You have reviewed the existing proposals
- You are aware that your proposal requires being a member of TC39, or locating a TC39 delegate to "champion" your proposal
Follow these steps:
- Click the green "use this template" button in the repo header. (Note: Do not fork this repo in GitHub's web interface, as that will later prevent transfer into the TC39 organization)
- Go to your repo settings “Options” page, under “GitHub Pages”, and set the source to the main branch under the root (and click Save, if it does not autosave this setting)
- check "Enforce HTTPS"
- On "Options", under "Features", Ensure "Issues" is checked, and disable "Wiki", and "Projects" (unless you intend to use Projects)
- Under "Merge button", check "automatically delete head branches"
-
"How to write a good explainer" explains how to make a good first impression.
Each TC39 proposal should have a
README.md
file which explains the purpose of the proposal and its shape at a high level....
The rest of this page can be used as a template ...
Your explainer can point readers to the
index.html
generated fromspec.emu
via markdown likeYou can browse the [ecmarkup output](https://ACCOUNT.github.io/PROJECT/) or browse the [source](https://github.com/ACCOUNT/PROJECT/blob/HEAD/spec.emu).
where ACCOUNT and PROJECT are the first two path elements in your project's Github URL. For example, for github.com/tc39/template-for-proposals, ACCOUNT is "tc39" and PROJECT is "template-for-proposals".
- Make your changes to
spec.emu
(ecmarkup uses HTML syntax, but is not HTML, so I strongly suggest not naming it ".html") - Any commit that makes meaningful changes to the spec, should run
npm run build
and commit the resulting output. - Whenever you update
ecmarkup
, runnpm run build
and commit any changes that come from that dependency.