Maharaja Surajmal Brij University Students: A Local Business Website Internship Project

Yes, you can scope and build a useful local business website in 14 days: a public menu or catalogue page, an enquiry form that stores messages, and a small admin panel the shopkeeper can use without calling you. The trick is to cut scope hard on day one, write down what “done” means, and finish with a handover document so the project survives after your internship ends.

This guide is written for students of Maharaja Surajmal Brij University and any learner near Bharatpur who wants a real portfolio project. It gives you a client brief template, a day-by-day plan, a scope scorecard, a data model, and a handover document outline. You can use it with a family shop, a sweet shop, a coaching centre, a tailor or a stationery store.

What a 14-day shop website should and should not include

A neighbourhood shop does not need a full e-commerce platform. It needs customers to find its menu or product list, see timings and location, and send an enquiry. The owner needs to change prices and items without editing code. That is the entire product.

The three core features

• Menu or catalogue page: items grouped by category, each with name, price, short description, availability flag and optional photo.
• Enquiry form: name, phone, message, optional item of interest. Submissions are saved in a database and shown in the admin panel.
• Admin panel: a password-protected area to add, edit, hide and delete items, and to read and mark enquiries as handled.

What to leave out in 14 days

• Online payments and order tracking (they bring refunds, legal and security obligations).
• Customer accounts and login for the public.
• Multi-language switching, unless the owner insists on Hindi only. Writing the content in Hindi or English as requested is simpler than building a toggle.
• Delivery logistics, coupons and loyalty points.

Write these exclusions into the brief as “Phase 2 ideas” so the owner feels heard and you are protected from scope creep.

Client brief template for a nearby shop website

Sit with the owner for 30 to 45 minutes, ideally at the shop, and fill in this template together. Print it or share it on WhatsApp as a document, then ask the owner to reply “approved” in writing. That message is your scope agreement.

Rules for using the brief

1. Get consent to use the shop’s name, photos and prices in your portfolio before you publish anything.
2. Do not collect personal data you do not need. A phone number and name are enough for an enquiry.
3. Agree early who owns the final files. A simple line such as “the shop owns the content and the finished site; the student may show it in a portfolio” avoids disputes.
4. Never promise search ranking, sales growth or free hosting forever.

Scope scorecard: deciding what fits into 14 days

Rate every requested feature on effort and value. Build high value, low effort items first. Anything scoring below the cutoff goes to Phase 2.

The effort numbers are planning estimates, not measurements; adjust them to your own speed after day 3.

A 14-day plan from brief to handover

If you are doing the free two-week online internship from CareerSwami, which offers a free offer letter and a free completion certificate after successful completion, this plan maps neatly onto its 14 days. Pair it with a track that matches the stack you choose.

Data model and routes for the menu, enquiry and admin features

Keep the database to four tables. This is an illustrative structure, not code that has been run.

categories(id, name, sort_order)
items(id, category_id, name, price, description, image_path, is_available, updated_at)
enquiries(id, name, phone, message, item_id NULL, status, created_at)
admins(id, username, password_hash, created_at)

Suggested routes

• Public: home, menu, contact (GET and POST).
• Admin: login, logout, dashboard, items list, item create and edit, enquiries list, enquiry detail.

Any stack works: React with Node and a database, Django, Laravel, or plain PHP with MySQL. Pick the one you can debug alone. Familiarity beats fashion in a 14-day window.

Worked illustration: scoping a sweet shop in Bharatpur

The following case is invented for teaching and does not describe a real shop or student.

A student meets the owner of a sweet shop. The owner first asks for online ordering, delivery tracking and a Hindi-English toggle. The student scores each item on the scorecard and explains that ordering and payments need weeks, not days. They agree on this scope:

1. A menu with five categories: laddoo, barfi, namkeen, festival boxes and drinks.
2. A “Bulk order enquiry” form with name, phone, date needed and message.
3. An admin panel for two users to update prices before Diwali and mark items as sold out.

The student adds a Phase 2 list: online ordering, payments, Hindi-English toggle. The owner replies “approved” on WhatsApp. On day 9 the owner tests the inbox, finds that “date needed” is missing from the list view, and the student adds it as a column on day 11. Because the change was small and the scope was written down, the schedule holds.

Notice what made this work: a written scope, one named approver, a Phase 2 list and a review slot before the final days.

Testing checklist before you show the owner

• The menu loads correctly on a low-end Android phone and a slow connection.
• Hidden or sold-out items do not appear, or are clearly labelled.
• The enquiry form rejects empty fields and obviously invalid phone numbers, and shows a clear message.
• Submitting the form twice does not crash anything.
• Admin pages redirect to login when you are signed out.
• Passwords are stored hashed, never in plain text.
• Text from forms is escaped when displayed, to block script injection.
• Deleting a category does not leave orphaned items or broken pages.
• Every phone number and map link on the site works when tapped.

Handover document outline for the shop owner

The handover is what separates a college exercise from a professional deliverable. Write it in plain language, in Hindi if the owner prefers, and include screenshots.

1. Project summary: what was built, the live address, date of handover, and your contact for questions.
2. What is included and not included: copy the approved scope and Phase 2 list.
3. Access details: admin URL, how credentials were shared, and an instruction to change the password on first login. Never paste passwords into a document that is widely shared.
4. How to update the menu: step-by-step with screenshots for adding, editing, hiding and deleting an item.
5. How to read enquiries: where they appear, what the statuses mean, how often to check.
6. Hosting and domain: who holds the accounts, renewal dates if any, and what happens if renewal lapses.
7. Backups: how data can be exported and who is responsible.
8. Technical notes: stack, repository location, how to run it locally, environment settings, database structure.
9. Known limitations: bugs not fixed, features deferred.
10. Support terms: state clearly whether any support continues after the internship, and for how long. Do not leave this vague.
11. Sign-off: a short acceptance line the owner confirms in writing.

Maharaja Surajmal Brij University students: how to fit this project into your course

The university is described on Wikipedia (not an official page) as a state university at Bharatpur, Rajasthan, with its main campus in the Kumher area outside the city. The same page says it was set up in 2012 under the Brij University, Bharatpur Act, 2012 and renamed in 2014. It also indicates that the university affiliates colleges from three districts, which suggests an affiliating model. Treat these as background, not as official rules.

What this means for you in practice: internship, training and project-work rules may be set by the university, by your affiliated college, or by both, and that has not been confirmed from an official source. So do not assume that this project will count towards a practical, a summer training requirement or a project report. It may be perfectly valuable as a portfolio piece even if it earns no formal recognition. CareerSwami offers a free internship with a certificate but does not promise academic credit, so any credit decision rests with your institution.

Because a nearby shop is a real client, also think about logistics. Bharatpur-area shops will often prefer a visit or a WhatsApp conversation over email, and festival seasons can make owners hard to reach. Book your client meeting and your review slots early.

Verification steps for your department and college

1. Ask your department coordinator or training and placement officer, in writing, whether an online or self-arranged internship is accepted for your programme and semester.
2. Request the current scheme or regulation document for your course and look for the internship, summer training or project-work clause: duration, evaluation, and required documents.
3. Ask whether a certificate from an online provider, plus a project report, is acceptable proof, and who signs the verification form.
4. Check the official university website for notices and your college notice board, since the Wikipedia details above may be outdated.
5. Ask your faculty whether a local-client project can be submitted as a mini-project, and if so who approves the topic.
6. Keep copies of every reply, since written answers protect you if rules are interpreted differently later.

Turning the finished shop site into a portfolio case study

Write a one-page case study with these headings: the problem, the agreed scope, the stack, the data model, three screenshots, one hard bug you fixed, what you deferred, and what you would do next. Add a link to the repository with a clear README. If the owner permits, add the live link; if not, record a short demo video with sensitive details hidden.

In interviews, talk about decisions rather than features: why you cut online payments, how you validated input, how you explained the admin panel to a non-technical owner. Those stories show judgement, which entry-level candidates rarely demonstrate.

Frequently Asked Questions

Can I really finish a website with an admin panel in 14 days?

Yes, if you limit it to a menu, an enquiry form and a basic admin panel, and defer payments and ordering. Fix the scope on day one and keep the daily plan above as your guide.

Do I need to charge the shop owner?

This guide treats the project as a learning internship. If money is involved, agree it in writing before starting. CareerSwami’s internship itself is free and does not include a stipend.

Which tech stack should I choose?

Choose the stack you already know well enough to debug alone. A familiar framework with a relational database such as MySQL or PostgreSQL is enough for these four tables.

Where should I host the site?

Pick a free or low-cost host suited to your stack, and agree with the owner who will hold the account and pay any future fees. Record this in the handover document so nobody is surprised later.

Will this project count as university credit or a college internship?

That depends on your university and college rules, which this article cannot confirm. Use the verification steps above and get the answer in writing before you rely on it.

What if the owner keeps adding requests?

Point to the approved brief and the Phase 2 list. Offer to schedule new requests after handover, and never accept changes verbally without updating the written scope.

How do I use the free internship alongside this project?

Treat the 14 days of the internship as the delivery window for this project, and use the day-by-day plan to report progress. The certificate is issued on successful completion of the internship, not for the shop website itself.

Is it safe to put the shop’s details in my portfolio?

Only with the owner’s permission. Ask for it in the brief, and leave out customer enquiries, phone numbers and any admin credentials from screenshots and repositories.

Related Full Stack Web Development guides

• Mahindra University Students: Setting Up CI Checks for an Internship Repository
• HBNI Students: Research Lab Tools as a Full Stack Internship Project
• Kolhan University Students: Learning Full Stack Web Development Through Short Daily Practice Blocks
• All Full Stack Web Development internship guides