Developer Environment & Onboarding

1. Developer Environment Provision After Hiring

1.1 Onboarding of New / Unknown Developers

Once a developer is selected and formally engaged (even if previously unknown to Evanto), an onboarding process is initiated which may include:

• Verification of basic credentials and communication details.
• Signing or accepting Developer Terms & Conditions and any relevant confidentiality documents.
• Mapping skills to appropriate products, modules, or project types.

1.2 Environment Setup & Access

After onboarding, a suitable development environment is provided, which may involve:

• Access to staging/test servers or development instances.
• Version control access (e.g., repository accounts) with limited, role-based permissions.
• Issue trackers, project boards, or task management tools.
• Technical documentation, coding guidelines, and project-specific notes.

2. Work Types & Environment Usage

2.1 Ready-Made Product Development

Developers may work on:

• Creating new ready-made scripts, templates, themes, or tools.
• Enhancing existing products with new features and improvements.
• Fixing bugs and performing maintenance on live or marketplace-ready items.

All such work is performed within the provided development environment and must follow Evanto’s coding and security standards.

2.2 Customized Web Apps & Client Projects

Developers may also work on client-specific customizations, including:

• Bespoke websites for various sectors (e-commerce, business, education, healthcare, etc.).
• Custom modules, integrations, and specialized workflows.
• Performance optimization and security hardening for client deployments.

Terms and conditions for such custom work may vary depending on project scope and are communicated as part of individual project briefs or contracts.

3. Developer Responsibilities & Liability

3.1 Proper Use of Environment

Developers agree to use the provided environment only for authorized work, which includes:

• Working on assigned tasks, tickets, or modules.
• Testing features in staging/sandbox areas before deployment.
• Following project-specific branching and deployment policies.

3.2 Data, Security & Confidentiality

Within the developer environment, developers must:

• Handle all client and platform data responsibly and confidentially.
• Not export or copy data/code outside the environment without authorization.
• Ensure that no malicious, harmful, or abusive scripts are introduced.

3.3 Liability for Misuse

If a developer misuses the environment, causes damage, or violates policies (intentionally or through gross negligence), Evanto/Banglar Katha may:

• Revoke environment and system access immediately.
• Terminate the engagement or collaboration.
• Seek remedies as per applicable law and any signed agreements.

4. Tools, Standards & Technical Support

4.1 Tools & Stack (Indicative)

Depending on the project, the developer environment may involve:

• Standard web technologies: PHP, MySQL/MariaDB, HTML, CSS, JavaScript.
• Frameworks or CMS platforms, where relevant.
• Command-line tools, version control systems, and deployment utilities.

4.2 Coding & Documentation Standards

Developers are encouraged and expected to:

• Write clean, modular, and well-structured code.
• Document important functions, APIs, and configuration steps.
• Follow any style guides or conventions communicated by the Evanto team.

4.3 Developer Help & Collaboration

Evanto aims to provide a supportive environment where developers can:

• Ask technical questions related to assigned tasks.
• Receive guidance on platform architecture and best practices.
• Collaborate with other developers, designers, or project coordinators.

This helps developers grow their technical knowledge and deliver better service and care in the digital field.

5. Opportunities for Developers

By joining Evanto as a developer, individuals gain:

• Exposure to real-world web projects across multiple industries.
• Experience with both ready-made product development and customized solutions.
• Opportunities to improve full-stack skills, security awareness, and performance optimization techniques.
• Potential to build a long-term professional relationship based on quality and reliability.

6. Relation to Other Developer Policies

This Developer Environment page should be read together with:

• Developer Terms & Conditions
• General Terms of Service
• Privacy Policy & Do Not Sell My Data page
• Return & Refund and Shipping policies (for work affecting deliverables)

In case of any conflict, specific written agreements or project contracts may override general environment descriptions for that particular engagement.

7. Contact for Developer Environment & Hiring

Developers interested in joining Evanto or existing developers needing clarification about the environment, tools, or responsibilities can contact:

Please mention your skills, experience, and (if applicable) current project reference for faster handling of your query.