Intro

UI component for theknot.com main footer. This project does not currently have any tests because there are no scripts for this component and the build process is run through tk-bootstrap. index.sass is the entrypoint for all footer-related styles.

footer.mustache gets compiled into the static footer file on S3 that's consumed by the_knot_layout and by proxy all theknot.com applications.

Must Read!

This repo is consumed by 2 separate applications: tk-bootstrap & brashboard. You would need to create separate branches based either from master or chore/decouple-from-layout for each feature you want to add to the footer.

TK Bootstrap Deployment

• checkout a branch from master and make your changes.
• commit and merge back into master when you are sure the changes are ready to go.
• Update the package version based on your changes. (We recommend to commit the version in a separate PR)
• git checkout master and git pull to make sure you have the latest changes.
• A clean npm install is recommended
• run npm publish and log on to Gemfury to verify the latest is being published. (dist is not created in this version of the package!)
• Go to tk-bootstrap, checkout branch and update to use latest package version for footer. (Clean install works best)
• Verify version changes in package json and shrinkwrap file, commit and merge.
• deploy tk-bootstrap on Jenkins

BHP Deployment

• checkout a branch from chore/decouple-from-layout and make your changes.
• commit and merge back into chore/decouple-from-layout when you are sure the changes are ready to go.
• Update the package version based on your changes. (We recommend to commit the version in a separate PR)
• git checkout chore/decouple-from-layout and git pull to make sure you have the latest changes.
• A clean npm install is recommended
• run ./node_modules/.bin/gulp generate_dist to create new dist.
• run npm publish and log on to Gemfury to verify the latest is being published. (dist should have been created!)
• Go to brashboard, checkout branch and update to use latest package version for footer. (Clean install works best)
• Verify version changes in package json and shrinkwrap file, commit and merge.
• deploy brashboard