For large orgs, Lightning pages are like rabbits: they multiply quickly and most of them look the same unless you are really close. To keep the page population under control, use a unique Developer Name and provide a description of its properties when customizing record pages that will be assigned to anything other than Default.
Salesforce uncoded: the reality of code-free Salesforce communities | InfoWorld
My other blog is a publisher’s website 🙂
Note: The tag line “An interesting challenge achieved … but at what cost?” was added to the original post by the IDG editors and I’m not really sure why. I think that it is great how Salesforce has empowered the citizen developer to mash up components provided by the vendor and IT so that IT can focus their time only on the parts that really do need a customized solution. This leads to better custom solutions and greater use of the platform.
