Skip to content

Changes

Page history
Update DOC Office Migration to Commerce.gov authored by DAVID KUNKEL's avatar DAVID KUNKEL
Show whitespace changes
Inline Side-by-side
DOC-Office-Migration-to-Commerce.gov.md
View page @ a6601c88
......@@ -25,18 +25,18 @@ In this new office website, there are 3 menus that need to to be developed. The
![image](uploads/307946d0af86855a3e75f149b53873fb/image.png)
1. `OSY secondary top menu` to `Newname secondary top menu`
1. OSY footer to Newname footer
1. `OSY footer` to `Newname footer`
In this new office website, several fixed blocks need to be developed. Fixed blocks bring content to the production site and alleviates the need to rebuild a block. The following are the set of files that need to be mimicked and renamed:
1. osy_search_block_fixed_block to newname_search_block_fixed_block
1. osy_mobile_search_block_fixed_block to newname_mobile_search_block_fixed_block
1. `osy_search_block_fixed_block` to `newname_search_block_fixed_block`
1. `osy_mobile_search_block_fixed_block` to `newname_mobile_search_block_fixed_block`
- In the both the search fixed block and the mobile search fixed block be sure to change this `value="4digitvalue"` to the appropriate value assigned by Search.gov. This is the only way Search.gov can segment the search to the appropriate office.
3. osy_hero_block_fixed_block to newname_hero_block_fixed_block
4. osy_front_edit_fixed_block to newname_front_edit_fixed_block
5. osy_front_teaser_fixed_block to newname_front_teaser_fixed_block
3. `osy_hero_block_fixed_block` to `newname_hero_block_fixed_block`
4. `osy_front_edit_fixed_block` to `newname_front_edit_fixed_block`
5. `osy_front_teaser_fixed_block` to `newname_front_teaser_fixed_block`
- Ensure first paragraph has the "office-teaser-text" CSS class. This is a generalized office class to simplify coding and to ensure consistency. The second paragraph can have a unique CSS class
......@@ -44,37 +44,37 @@ In this new office website, several fixed blocks need to be developed. Fixed blo
In this new office website, 2 views need to be developed. The following are the set of files that need to be mimicked and renamed:
1. OSY resources to Newname resources
- This view aggregates nodes into an entitqueue on a block to the right of the front teaser block. Mimick the settings in this View
1. `OSY resources` to `Newname resources`
- This view aggregates nodes into an entitqueue on a block to the right of the front teaser block. Mimic the settings in this View
![image](uploads/fbfd2d311ba78789c03e589b1bd3ef92/image.png)
2. OSY frontpage
- This view aggregates nodes into an entityqueue to a series of blocks called top stories at the bottom of the office's homepage. This is the view that creates the office homepage. Add an overall css class called "office-top-stories. In the fomat add a css class to unformatted list called "top-stories" in Row class
2. `OSY frontpage`
- This view aggregates nodes into an entityqueue to a series of blocks called top stories at the bottom of the office's homepage. This is the view that creates the office homepage. Add an overall css class called "office-top-stories. In the format add a css class to unformatted list called "top-stories" in Row class
![image](uploads/8497ebe5a6d9d540204ab1f2b8dc7d39/image.png)
In this new office website, 2 entityqueues need to be developed. The entityqueue allow users to self curate a list. The following are the set of files that need to be mimicked and renamed:
1. OSY frontpage top stories to Newname frontpage top stories
1. OSY Resources to Newname Resources
1. `OSY frontpage top stories` to `Newname frontpage top stories`
1. `OSY Resources` to `Newname Resources`
In this new office website, generally 3 contexts need to be developed. Other offices such as OHRM require more contexts. This eventuality will need to be address on a case by case basis. The following are the set of files that need to be mimicked and renamed:
1. OSY homepage for Anonymous Users to Newname homepage for Anonymous Users
1. `OSY homepage for Anonymous Users` to `Newname homepage for Anonymous Users`
- The most involved Context is the one called, OSY homepage for Anonymous Users. Please follow the placement and order of the block in the illustration below:
This is the Context for homepage for Anonymous Users. Please follow this example for placement and block order
![image](uploads/308577a2066138ee24e06132224d97e6/image.png)
1. OSY Content to Newname Content
1. `OSY Content` to `Newname Content`
This is the Context for content. Please follow this example for placement and block order
![image](uploads/585ac910f3e741067e72d09b7dc5471c/image.png)
1. OSY homepage for Admins to Newname homepage for Admins
1. `OSY homepage for Admins` to `Newname homepage for Admins`
With the homepage for Admins context, there is only one reaction which is for the front edit button to update the blocks and entityqueues on the frontpage. Special permission need to be set for Admins and Content editors to see these buttons
......