0% found this document useful (0 votes)
15 views3 pages

Internship Weekly Log

Sanket Kalekar's internship at DigiBread India involves developing the website empowr360.com over a three-month period. The project includes initial research, design, technology selection, and integration of ERP and CRM systems, followed by full website development and testing. The final phase focuses on optimization, deployment, and documentation of the integration process.

Uploaded by

Sanket Kalekar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views3 pages

Internship Weekly Log

Sanket Kalekar's internship at DigiBread India involves developing the website empowr360.com over a three-month period. The project includes initial research, design, technology selection, and integration of ERP and CRM systems, followed by full website development and testing. The final phase focuses on optimization, deployment, and documentation of the integration process.

Uploaded by

Sanket Kalekar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Internship Weekly Log

Name: Sanket Kalekar

Internship Duration: [2/Dec] – [3/Mar]

Company Name: DigiBread India

Project : empowr360.com

Day 1-2: Initial Research & Requirements Gathering

• Website Goals: Define the objectives of the landing page (e.g., capture leads, provide information,
etc.).

• Features of the Website: Identify the pages to be included (e.g., Homepage, About Us, Services,
Contact Us, Testimonials).

• Dynamic Functionality: Define what dynamic functionality will be required (e.g., forms,
interactive elements, data-driven content).

• ERP & CRM Integration: List out specific features needed in ERP and CRM (e.g., tracking sales,
customer management, invoicing).

Day 3-4: Design Wireframes and Architecture

• Create wireframes for each landing page to outline layout.

• Identify key dynamic components like forms, data feeds, etc.

• Outline how ERP and CRM will interact with the website (e.g., capturing leads from forms and
syncing with CRM).

Day 5: Technology Stack Selection

• Website: Choose frontend and backend technologies (e.g., React, Vue.js, Node.js, or WordPress
for dynamic capabilities).

• ERP & CRM: Decide whether to integrate existing software (e.g., Salesforce, Zoho, Microsoft
Dynamics) or build custom modules.

• Integration Platform: Select the API or middleware to connect ERP/CRM to the website (e.g.,
Zapier, custom APIs, etc.).

Day 6-7: Finalize Planning & Project Management

• Set timelines for each page development and software integration phase.

• Determine project management tools for tracking progress (e.g., Trello, Jira).

Week 2: Website Structure & Basic Design

Day 8-9: Develop Initial Website Structure


• Set up the project repository (e.g., GitHub).

• Initialize the development environment.

• Build the basic structure for the 5 pages.

o Homepage: Add placeholders for hero image, text, and dynamic elements.

o About Us: Set up sections with placeholder content.

o Services: Build a layout to display services and dynamic elements.

o Contact Us: Add basic contact form structure.

o Testimonials: Design a section for displaying customer feedback.

Day 10-11: Basic Dynamic Functionality

• Implement dynamic components (e.g., form submission handling, interactive elements).

• Integrate initial form submission to store data locally or in a database (without yet linking to
CRM).

Day 12-14: Preliminary Design

• Create the basic UI/UX design for the website using tools like Figma or Adobe XD.

• Apply styles and colors to the website’s structure.

• Make the layout responsive (mobile and desktop-friendly).

Week 3: ERP & CRM Integration Design and Basic Functionality

Day 15-16: Define ERP/CRM Integration Flow

• Design the data flow between the website and the ERP/CRM.

o For example: Form submissions on the website lead to new customer records in CRM.

• Determine what data needs to be sent from the website to the ERP/CRM (e.g., customer data,
purchase data, leads).

Day 17-18: Set Up API Integration

• Research the ERP/CRM APIs or middleware (e.g., Salesforce API, Zoho API).

• Set up the API integration to send data between the website and CRM/ERP systems.

• Write API endpoints that will send and receive data.

Day 19-21: Test Initial Integration

• Run test cases for integrating website forms with the CRM/ERP (e.g., submitting a contact form
and verifying that data appears in CRM).

• Debug any issues with data syncing or API calls.


Week 4: Full Website Development & CRM/ERP Sync

Day 22-24: Advanced Dynamic Website Features

• Implement advanced dynamic features (e.g., form validation, dynamic content loading).

• Implement user authentication if needed (e.g., customer logins, dashboard access).

• Enhance website's interactive features (e.g., displaying dynamic content based on CRM data).

Day 25-27: CRM/ERP Full Integration

• Full integration between ERP and CRM systems: Ensure that customer data, orders, and inquiries
are correctly reflected in both systems.

• Set up automated workflows (e.g., new leads automatically create opportunities in CRM,
inventory tracking in ERP).

Day 28: Test Full System

• Conduct end-to-end testing of website and ERP/CRM integration.

• Test the entire customer journey: From website visit to form submission to CRM/ERP record
creation.

Week 5: Finalizing & Deployment

Day 29-30: Optimize & Refine the Website

• Optimize website performance (e.g., image compression, lazy loading, minimizing JavaScript).

• Refine dynamic elements and forms to improve usability.

Day 31-33: Testing and Bug Fixing

• Conduct comprehensive user testing, including functionality and UX testing.

• Address any issues that arise from user testing (broken links, incorrect data syncing).

Day 34-35: Prepare for Launch

• Set up hosting environment (e.g., AWS, Netlify, or traditional hosting).

• Set up DNS settings and domain name.

Day 36-37: Launch and Final Testing

• Deploy the website to the production environment.

• Perform final testing of ERP/CRM integration post-launch.

Day 38-40: Post-Launch & Documentation

• Document the integration process for future reference.

• Monitor the website for any issues post-launch and ensure the ERP/CRM systems are working
seamlessly.

You might also like