11ty as default SSG

content/engineering/languages-runtimes/language-selection.md

@@ -41,7 +41,7 @@ The following are used widely at 18F:
 | ---- | ---- |
 | CSS framework  |  [_More info_]({{ "/engineering/languages-runtimes/css/#frameworks" | url }})  |
 | Infrastructure/configuration as code | [Terraform](https://www.terraform.io/)  |  
-| Static site generator  | [Jekyll](https://jekyllrb.com/) (with the [uswds-jekyll](https://github.com/18F/uswds-jekyll) theme) or Hugo |
+| Static site generator  | {% include "engineering/tag-default.html" %} [11ty](https://www.11ty.dev/)/Eleventy |
 
 ## Project scope
 Perhaps the most important factor to weigh when considering languages is the estimated project scope. If we anticipate a large, long-standing project which will be handed off to our agency partners, we should be conservative in our language selection. These projects warrant our most standard approach, which generally translates to the selection of one of our primary languages.  On the other hand, if writing a one-off script or small internal project, we have significantly more latitude to try experimental languages.