docs/01-start-here/06-faqs.md
If you can't find your element in views, cleaners or JS, it is likely your markup is coming from CAPI and used as-is. You can use Teleporter to view the response from CAPI on the page you're seeing the mark-up.
For example: you're trying to style a class, but can't find it in the Frontend codebase and want to make sure it's only used in the HTML where you're looking.
In this case, you can check in the content-api repo and your class will probably appear in some text fixtures and then you can look in the flexible-content repo (composer) where you'll probably see the view that adds the class you're styling.
If your class only appears on the component you expected, you can be fairly confident that it won't appear anywhere else.
Run make without any arguments or look in the makefile
To see hashed JS bundles locally you can set assets.useHashedBundles=true in your frontend.conf and run make compile.
You'll need to setup nginx and then set-up the identity frontend
Sometimes we want to create a badge for a story, but don't want the world to know what that story is until it is released. We therefore need to encrypt the tag name that the badge is being applied to. This all happens in Badges.scala.
To link a badge to a secret tag:
sbt "badgeHash [your tag]"salt=XXXXXXXXX
hash=XXXXXXXXX
model.Badges object, add a new val: val specialReport = SpecialBadge("[salt]", "[hashed tag]", Static("path/to/Badge.svg"))