DOC-Office-Migration-to-Commerce.gov.md

-When beginning a office migration into the main Department of Commerce website, two twig files need to be developed. These files can be found in /themes/custom/commerce/templates. The most efficient approach is to copy an existing office twig file and rename it to the appropriate new office. For example I will use OSY's twig files. The following are the set of files that need to be copied and renamed:
+When beginning a office migration into the main Department of Commerce website, two twig files need to be developed. These files can be found in /themes/custom/commerce/templates. The most efficient approach is to copy an existing office twig file and rename it to the appropriate new office. For example I will use OSY's twig files. The following are the set of files that need to be copied and renamed. They relate primarily to the office's homepage.
 
 1. block--osy-branding-block.html.twig to block--newname-branding-block.html.twig
    - In the branding block you will need to update this information to the new office
@@ -28,6 +28,15 @@ In this new office website, several fixed blocks need to be developed. The follo
 
 ![image](uploads/93669f54a066e2527a2eade441181876/image.png)
 
+In this new office website, several  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
+1. 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
+
+![image](uploads/c5b205d8025c05779df80cb45132e14d/image.png)
+