In This Section
- Concepts
- Data
- Build
- The App Composer
- The Page Index
- Context
- Pages
- Models
- Components
- Best Practices
- Debugging Skuid in the Console
- Logic
- Style
- Deploy
- Extend
- Reference
- The Property Library
- API Reference
- skuid.debug
- skuid.runtime
- skuid.$
- skuid.actions
- skuid.ajax
- skuid.builder.core
- skuid.builder.core.coreProps
- skuid.calendar
- skuid.collaboration
- skuid.component
- skuid.componentType
- skuid.events
- skuid.formula
- skuid.hotkeys
- skuid.label
- skuid.lightning
- skuid.load
- skuid.model
- skuid.model.Model
- skuid.mustache
- skuid.page
- skuid.sfdc
- skuid.snippet
- skuid.time
- skuid.utils
- skuid.version
- Component-Specific APIs
- Skuid Model Metadata Object
- Skuid Model Child Relationship Metadata Object
- Skuid Model Condition Metadata Object
- Skuid Model Field Metadata Object
- Skuid Model Record Type Metadata Object
- Page XML API
- skuid-sfdx
- skuid CLI
- Skuid Metadata Object Reference
- Skuid Glossary
- Formula and Function Reference
- Open Source Software Attributions
- Site Administration
- Tutorials
- Legal terms and conditions
- Skuid for Salesforce Evaluation Guide
In This Topic
Can my entire team develop with Skuid?¶
Skuid supports distributed development. Skuid for Salesforce pages can be exported as XML files through page packs or the skuid-sfdx
Salesforce CLI plugin, and they can then be stored in source control software, such as git. Because of this, any developer building with Skuid can work in their own development site.
When a developer is assigned an issue or task, they can pull down the latest code from a central source code repository, like Github, and make the appropriate changes. These changes would then be pushed as a branch to the source code repository, reviewed in a test environment and, if accepted, merged with the master branch.
For more information, see skuid-sfdx docs