Version control, documentation workflow, and Fab Academy setup
As part of the project management and planning phase, I began exploring the conceptual design of my final project. The sketch below represents an early-stage idea for a compact, enclosed embedded system that integrates sensing, processing, and user interaction in a single physical unit.
This preliminary sketch was created to visualize the overall form factor,
component placement, and user interaction flow. The design emphasizes a
modular enclosure, accessibility for internal electronics, and a front-facing
interface for display and control. This early ideation step helps define the
project scope and guides future decisions related to digital design,
electronics integration, and fabrication techniques.
ChatGpt Prompt "i have one original image and i draw, can you make one visionry image for my tool"..
Link of the original Image: https://www.cgrain.ai/products/
This week focused on setting up the project infrastructure for Fab Academy. I created a structured website for documentation, configured version control using Git and GitLab, and established a workflow for maintaining weekly assignments and the final project documentation.
This section documents the step-by-step progress made during Week 01, focusing on project management, version control setup, and establishing a reproducible documentation workflow for Fab Academy.
The first step was to verify that Git was correctly installed and accessible from the command line. This ensured that version control operations could be performed reliably throughout the course.
After confirming Git availability, I navigated to the local Fab Academy repository directory. This repository serves as the central location for managing all website files and weekly documentation.
The git status command was used to inspect the current state
of the repository. This step helps identify modified, deleted, and untracked
files before staging changes for a commit.
All updated website files, including HTML, CSS, JavaScript, and image
assets, were staged using git add .. This prepares the files
for committing to the repository.
A descriptive commit message was used to record the changes made during this iteration. Committing frequently with clear messages improves traceability and supports incremental development.
Finally, the committed changes were pushed to the Fab Academy GitLab server. This step publishes the updated website and ensures that the documentation is available online for review.
This week i was working on the old templte though i have planned to changes the template to new one which i found over the internet. Will update the page once the template updateion is complets.