- Build.One Development Best Practices
- Introduction
- 1. General Points
- 2. Working with Databases, DSOs, and Entities
- 3. Structuring Frontend and Backend Code
- 4. Theming and Styling
- 5. Hardware and Software Requirements
Build.One Development Best Practices
Introduction
Welcome to the Build.One development journey! This guide aims to provide you with best practices for getting started with Build.One, ensuring a smooth and efficient development process. Whether you're new to the platform or looking to enhance your skills, these guidelines will help you make the most out of your development experience.
1. General Points
- Naming Conventions: Adopt a consistent and meaningful naming convention for your objects, variables, and functions. This practice enhances code readability and collaboration among team members.
- Unique Object Names in Repositories: Ensure that object names within a repository are unique. This prevents naming conflicts and contributes to a cleaner and more maintainable codebase.
- Repository Structure: Decide whether to have one repository for multiple apps or a separate repository for each app. Choose an approach that aligns with your project's organization and scalability needs.
2. Working with Databases, DSOs, and Entities
- Using Databases: Familiarize yourself with database integration in Build.One. Understand how to set up, configure, and manage databases for your applications.
- Database Access: Learn the methods to access and interact with databases within your code. This includes querying, updating, and managing data seamlessly.
- Creating Custom DSOs with Code: Explore the process of creating custom Data Source Objects (DSOs) using code. This allows you to tailor your data structures to meet specific project requirements.
3. Structuring Frontend and Backend Code
- Structuring Backend Code: Establish a well-organized structure for your backend code, including the organization of routes, controllers, and services. This enhances code maintainability and readability.
- Structuring Frontend Code: Apply best practices for structuring frontend code, including the organization of components, styles, and scripts. This ensures a modular and scalable frontend architecture.
- Calling Backend Code from Frontend: Understand how to invoke backend functionalities from the frontend. This may involve making API requests, handling responses, and ensuring seamless communication between the two layers.
4. Theming and Styling
- Understanding Themes: Gain insights into the concept of themes within Build.One. Themes define the visual style of your applications, and understanding them is crucial for creating visually appealing interfaces.
- Creating Custom Themes: Learn how to create your own themes and customize the styling of your applications. This allows you to align the visual appearance with your project's branding and design guidelines.
5. Hardware and Software Requirements
- Hardware Requirements: Familiarize yourself with the hardware specifications recommended for optimal Build.One development. Ensure your system meets these requirements to guarantee a smooth development experience.
- Software Requirements: Understand the software dependencies and tools necessary for Build.One development. Install and configure the required software components to create a conducive development environment.
These best practices are designed to guide you through the key aspects of Build.One development. Implementing these recommendations will contribute to the efficiency, maintainability, and scalability of your projects. Happy coding!
→ Do’s and dont’s
→ Wie arbeitet man mit local and global buffers
→ Debugging
→ Kette Low Code → Frontend → Backend
→ Gebt mir alles an Informationen die man braucht um mit b1 zu arbeiten
Back to 
Documentation
Back to 