A behind-the-scenes making-of story

How We Built Teamwork Eats
From Zero to Live ๐Ÿš€

Namaste! ๐Ÿ™ Come, let us take you on a full journey โ€” from one small idea written in a Jira ticket, all the way to a working food-delivery web app with a cute pixel guy running to the cart. No fancy jargon, only simple and clear explanation.

Start the Story ๐Ÿ“– Open the App ๐Ÿ”
0
Story Steps
0
Tools Used
0
Tests Passing
0
AI-Assisted
โ–ผ Scroll down to begin the adventure โ–ผ
The Journey ยท Step by Step

From One Idea to a Live App ๐ŸŒฑโ†’๐ŸŒณ

Every big thing starts small. Here is exactly how this app came to life, in the same order it actually happened.

๐Ÿ“
Step 1 ยท The Spark

We created a task in Jira

The whole story started with one Jira ticket โ€” TE-28: "Create a simple one page Library". This was an Epic with Critical priority. In simple words, we wrote down what we wanted before writing any code. The idea was tiny: a page to order (borrow) a book and return a book.

๐Ÿ’ก Why Jira first? Jira is like a to-do register for teams. Writing the task first means everybody knows the goal. No confusion, no "kya banana hai?" later.
๐Ÿ“š
Step 2 ยท Add the Details

We added details from a Confluence page

A one-line ticket is not enough. So we added proper details and requirements โ€” the kind of information you keep in a Confluence page (your team's shared notebook). Things like the features needed, the look and feel, and the rules of the app were noted down.

๐Ÿ’ก Why Confluence? Jira says "what to do", Confluence explains "how and why" in detail. Together they give a clear picture โ€” like a recipe card before cooking. ๐Ÿณ
๐Ÿค–
Step 3 ยท Hand It Over

We assigned the task to the Jira Coding Agent

Here comes the magic. Instead of typing every line by hand, we assigned the ticket to a Jira Coding Agent (an AI developer). It read the ticket, understood the requirements, and started building โ€” creating branches and writing real code by itself.

๐Ÿ’ก The takeaway: This was our starting point of building. The agent turned words in a ticket into working software. You describe, it delivers. ๐Ÿš€
๐Ÿ”
Step 4 ยท The Foundation

The base app: "Teamwork Eats"

The project grew into a full food-delivery web app called Teamwork Eats. It already had a Home page, a Menu with search and filters, a shopping Cart, a Checkout form, and an About page โ€” all built with React + Vite.

๐Ÿ’ก In simple words: React builds the screen using small reusable blocks called "components", and Vite makes it run super fast on your computer. โšก
โœจ
Step 5 ยท Our New Features

We added a Library, a Pixel Guy & a portable pack

On top of the base app, we added three fresh things: (1) a one-page Library to borrow & return books (that original TE-28 idea!), (2) a fun pixelated guy who runs and drops your item into the cart whenever you add something, and (3) simple one-command scripts to zip and run the whole project anywhere.

๐Ÿ’ก Bonus: The pixel guy came from another branch made by the Coding Agent. We found it, understood it, and neatly merged it into our work. Teamwork indeed! ๐Ÿค
๐Ÿš€
Step 6 ยท Ship It

We tested, committed & pushed to Bitbucket

Finally, we made sure everything works โ€” running lint (checks code style), build (makes the final version), and test (17 tests, all passing โœ…). Then we committed the code and pushed it to Bitbucket, ready for a pull request and review.

๐Ÿ’ก Why test before push? So we don't break anything for others. "Measure twice, cut once" โ€” same idea for code. ๐Ÿ“
The Big Picture

How Everything Connects ๐Ÿ”—

One idea flows through these tools and comes out as a live app. Follow the arrows!

๐Ÿ“Jira TicketThe idea (TE-28)
โžœ
๐Ÿ“–ConfluenceThe details
โžœ
๐Ÿค–Coding AgentWrites code
โžœ
โš›๏ธReact AppThe product
โžœ
๐Ÿš€BitbucketShipped!
The Toolbox

What We Used to Build It ๐Ÿงฐ

Every tool below played a specific role. Here is each one in plain language.

๐ŸŽฏ

Jira

Where we wrote the task (TE-28) and tracked the work. The "what to build" board.

๐Ÿ“–

Confluence

Where the detailed requirements lived. The "why & how" notebook.

๐Ÿค–

Jira Coding Agent

The AI teammate that read the ticket and wrote real code for us.

โš›๏ธ

React 19

Builds the user interface using small reusable pieces called components.

โšก

Vite

The lightning-fast tool that runs and builds the app.

๐Ÿงญ

React Router

Handles moving between pages like /menu, /library, /about.

๐ŸŽจ

CSS Modules

Keeps the styling of each component clean and separate.

๐Ÿงช

Vitest

Runs automatic tests to make sure nothing is broken.

๐Ÿ”ง

Bitbucket & Git

Stores our code safely and lets the whole team collaborate.

The Result

What the App Can Do ๐ŸŽ‰

Open the app and try each of these live!

๐Ÿ 

Home

A welcoming landing page with a featured carousel and "cookie of the day".

๐Ÿฝ๏ธ

Menu

Browse food with live search, category filters and quick-view popups.

๐Ÿ“š

Library (new!)

Borrow a book and return it โ€” the original TE-28 idea, now live.

๐Ÿ›’

Cart & Checkout

Add items, review your cart, fill the form and place the order.

๐Ÿ•น๏ธ

Pixel Cart Guy (new!)

A pixelated character animates your item flying into the cart. Pure joy!

๐ŸŒ—

Dark / Light Mode

Switch the theme to whatever is easy on your eyes.

Try the Star of the Show

Meet the Pixel Cart Guy ๐Ÿ•น๏ธ

Pick a food, press the button, and watch our little hero run to the cart โ€” just like in the real app!

๐Ÿง
๐Ÿ›’
Items delivered to cart: 0
Try It Yourself

Run the App on Any Computer ๐Ÿ’ป

Just three simple commands. You only need Node.js installed.

1
Make a portable zip
# creates dist/teamwork-eats.zip with only required files
npm run pack
2
Install everything
# unzip, then inside the folder:
npm run install:all
3
Start it locally
npm run dev   # open http://localhost:5173

๐ŸŽ“ The Big Lesson

You do not need to write every line of code yourself. Start with a clear idea in Jira, add details in Confluence, let a Coding Agent build it, then review, test and ship. That is modern, AI-assisted software making โ€” and now you know the full story! ๐Ÿ™Œ

๐Ÿ” Open the Teamwork Eats App