{"type":"doc","content":[{"type":"blockquote","content":[{"type":"extension","attrs":{"extensionType":"com.atlassian.confluence.migration","extensionKey":"legacy-content","text":"","parameters":{"cxhtml":"INLINE

Common resources share a strong naming scheme, so that new resources with a similar scope are easy to locate, regardless of which team member creates the resource. This practice applies to version control repositories, named packages, shared usernames, development environments, and so forth. ^(TBD)

","nestedContent":{"type":"doc","content":[{"type":"bodiedExtension","attrs":{"extensionType":"com.atlassian.confluence.macro.core","extensionKey":"excerpt","parameters":{"macroParams":{"atlassian-macro-output-type":{"value":"INLINE"}},"macroMetadata":{"macroId":{"value":"0df58333-972a-4665-8f8b-901cf56d9b1d"},"schemaVersion":{"value":"1"},"title":"Excerpt"}}},"content":[{"type":"paragraph","content":[{"text":"Common resources share a strong naming scheme, so that new resources with a similar scope are easy to locate, regardless of which team member creates the resource. This practice applies to version control repositories, named packages, shared usernames, development environments, and so forth. ","type":"text"},{"text":" (TBD)","type":"text","marks":[{"type":"subsup","attrs":{"type":"sup"}}]}]}]}],"version":1}}}}]},{"type":"paragraph","content":[{"text":"Namespace declaration","type":"text"}]},{"type":"paragraph","content":[{"text":"https://www.linkedin.com/post/edit/two-sf-morsels-managed-package-developers-ted-husted","type":"text","marks":[{"type":"link","attrs":{"href":"https://www.linkedin.com/post/edit/two-sf-morsels-managed-package-developers-ted-husted"}}]},{"text":" ","type":"text"}]}],"version":1}

Resource Naming Conventions