Pick what you are submitting
Choose Paper or Blog first. Papers must fit the loop-model taxonomy. Blogs stay in the flat Blogs section.
Fill the metadata once, reuse existing Loop Mechanism / focus / domain tags, review the generated YAML, then copy the path and YAML into your own fork / branch for the final pull request step.
Choose Paper or Blog first. Papers must fit the loop-model taxonomy. Blogs stay in the flat Blogs section.
Reuse existing Loop Mechanism / focus / domain tags, add alias tags manually if needed, then review the generated path and YAML before leaving this page.
Copy the generated path and YAML, fork the repository on GitHub, create a branch in your fork, add the file at that path, then open a pull request back to this repo.
The form below generates the final YAML file path and content. GitHub does not provide a public no-auth link that can automatically fork this repo and create the file in your account, so the final step is manual: fork the repo, create a branch in your fork, create the file at the generated path, paste the YAML, and open a pull request.
Paper submissions need a taxonomy category. Blog submissions stay in the flat Blogs section and use filenames of the form blogs/YYYY-MM-DD-shortname.yaml.
After filling the core paper / blog fields above, reuse existing Loop Mechanism / focus / domain tags here and add alias tags manually only if needed. GitHub pull requests do not support structured form fields, so this page keeps the structured tag inputs local before handing you off to the manual fork / branch / PR flow.
Loop Mechanism and focus tags are controlled vocabularies. If this submission needs a taxonomy or tag-vocabulary change, describe the proposal in the PR message instead of inventing YAML values here.
papers.json.