You are viewing our old blog site. For latest posts, please visit us at the new space. Follow our publication there to stay updated with tech articles, tutorials, events & more.

Static Consolidation v2

0.00 avg. rating (0% score) - 0 votes

At naukri.com change is good especially when it brings scalability and transparency to the system.
Here at FED (Front end development) team we follows a pre-defined folder structure for our UI projects. Previously the following folder structure was used:
  • /c – css files
  • /i – images
  • /j – js files
index.png
Issue with it was except the above three type of resources one cannot keep other resources in here as deployment tags which only includes c, j, i were to be made from the same directory.
The new structure
It has two major folders: /src & /gen.
  • /src – This is the working directory
    • /c – css files
    • /i – images
    • /j – js files
    • /sass – sass files
    • /jass – js module
    • /resources – It containers all htmls, psd’s etc (other than c,i,j)
  • /gen – This is the deployment ready directory
    • /c – css files
    • /i – images
    • /j – js files
index2.png
Reasons to adopt the new static consolidation structure
  1. Earlier html & psd (s) were kept separately and were difficult to track. But with the new format they are kept in /resources inside the respective project folder.
  2. Earlier deployment ready resources were kept in different branch from the main working tree. Now with /gen  all of them lies in same working tree well compressed and minified.
  3. To support a single directory structure for developer and designer.
Posted in General