robert-bryson
commented
2 years ago Thanks to @mogul's help yesterday untangling the rebase issue, the builds relatively correctly but with many conflicts.
Here is one, for example:
Conflict: The following destination is shared by multiple files.[0m
2022-03-16 18:04:32 INFO [build-jekyll] [33m The written file may end up with unexpected contents.[0m
2022-03-16 18:04:32 INFO [build-jekyll] [33m [36m/tmp/work/site_repo/_site/food/dr-woteki-on-scientific-integrity/index.html[0m[0m
2022-03-16 18:04:32 INFO [build-jekyll] [33m - /tmp/work/site_repo/www.data.gov/food/dr-woteki-on-scientific-integrity/index.html[0m
2022-03-16 18:04:32 INFO [build-jekyll] [33m - /tmp/work/site_repo/www.data.gov/_posts/2013-07-25-dr-woteki-on-scientific-integrity.md[0m
2022-03-16 18:04:32 INFO [build-jekyll] [33m [0m
User Story
In order to manage datagov-website easily, data.gov admins want all raw HTML files replaced with template versions and Jekyll layouts.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
Background
This is coming from https://github.com/GSA/datagov-deploy/issues/2873. While the AC is complete, and some files were transitioned to templates here.
Styling the jekyll site will be the bulk of the work; this will be a manual process. The whole site will share some common header/footer element. Other than root level pages, all contents can be grouped into different categories and each category will have some different UI elements that need custom layout. There are 20-30 categories, depending on what tool is used to do the counting, so there are 20-30 layouts needed to be coded in Jekyll. For reference, here are the templates that existed in the Wordpress era.
Security Considerations (required)
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]
Sketch
Next steps from basic build: