beechnut
beechnut
The contributor experience for the website should be reasonable. The contributor should be able to follow instructions relatively high up in the README to get an environment set up. Assumptions...
The admin folder has a config and index file for Netlify CMS. First: do we use Netlify for the 18F site? If we do, we should migrate it to maintain...
We provide an XML-based Atom feed with latest posts. This came for free with a Jekyll plugin; we'll have to replicate in 11ty. These articles should help figure out how...
The Jekyll site has some tests, and before launch, the replatformed site should have test coverage equivalent to the Jekyll site. Tests for removed functionality don't need to come over....
```[tasklist] ### Tasks - [ ] #3862 - [ ] Social media sidebar links aren't getting fixed by our custom markdown renderers. Figure this out and refactor our renderers so...
We're doing it! The last migration of 18F sites away from Jekyll! (See https://github.com/18F/TLC-crew/issues/64) All work will be done within the 18f.gsa.gov repo, off of the [replatforming-main](https://github.com/18F/18f.gsa.gov/tree/replatform-main) branch. This branch...
Something is wrong with the `./serve` command — that `&` detaches a process, and I'm often running into port conflicts that have to be shut down with `killport`. There's a...
# Pull request summary Adds blog post for https://github.com/18F/blog-drafts/issues/873 > [!IMPORTANT] > This pull request should only be merged AFTER #3957 is merged. This post will not look good otherwise.
Previously, code blocks looked squished, didn't have any syntax highlighting, didn't have line numbers, and didn't have clear filenames. This commit: - Adds margin to code blocks, both fenced and...
The technical tutorial I'm drafting for the blog looks kind of rough. ---- #### Problems - No syntax highlighting - No diff highlighting - The fenced ``` code blocks look...