deepak

byDeepak Kumar

Build the foundation of a premium personal portfolio website for me. Do NOT try to fully populate every project or every section yet. Focus first on the design system, page architecture, reusable components, routing, responsiveness, and overall visual experience. MY POSITIONING I am a Business Systems Architect / Digital Transformation & MIS professional. I design and build systems such as: - ERP systems - MIS platforms - Inventory systems - Workflow automation - HRMS - Sales & Purchase systems - Follow-up / calling systems - Ticketing tools - Import management systems - Operational dashboards - Internal business software - AI-powered business system tools IMPORTANT BRANDING RULES Do NOT mention Formative anywhere. Do NOT present me as a founder. Projects should simply be presented as systems or projects I have personally designed or developed. Do not invent: - job dates - project metrics - testimonials - education - certifications - company relationships - revenue figures - technologies not confirmed - business impact percentages We will add accurate content later. CURRENT PROFESSIONAL CONTEXT I currently work at Excel Sathi in a senior MIS / digital transformation / systems architecture role. My work involves understanding real business processes and converting them into structured digital systems. I have worked on projects associated with organizations/brands such as: - Royal Enfield - NovaCare - Finviz - and others Do not imply that I was directly employed by those organizations. CORE MESSAGE The website should communicate: "I design the systems businesses run on." My professional value is that I combine: Business Analysis + System Architecture + MIS + Automation + Software Development The visitor should understand that I do not just build websites. I study how a business operates, understand its workflows, identify problems, design the data structure, build the system, automate repetitive work, and create management reporting. DESIGN DIRECTION Create a premium, modern, highly technical portfolio. Visual inspiration may come from: - Linear - Vercel - Stripe - Raycast - Framer - modern AI SaaS products - Apple-style product storytelling Do not copy any website directly. The website should feel: - sophisticated - futuristic - minimal - premium - technical - business-focused Preferred design: - dark or near-black theme - strong typography - subtle gradients - soft borders - animated background details - smooth scrolling - premium hover states - subtle parallax - clean cards - architecture diagrams - workflow visualizations - polished page transitions Avoid: - generic developer portfolio templates - skill percentage bars - excessive neon - gaming aesthetics - unnecessary glassmorphism - random animations - cliché coding illustrations The portfolio itself should feel like a technology product. SITE ARCHITECTURE Prepare the website with these primary sections/pages: Home Projects Experience About Resume Contact Also prepare routing/architecture for individual project pages. Example: /projects/business-erp /projects/inventory-management /projects/timesheet-system /projects/hrms /projects/follow-up-system /projects/import-management /projects/ai-business-system-builder Do not fully write all project case studies yet. Create the structure so they can be added later without redesigning the website. HOMEPAGE FOUNDATION Create a strong hero section. Primary headline: "I design the systems businesses run on." Supporting message should communicate that I build ERP systems, MIS platforms, workflow automation, and internal business software. Primary CTA: Explore My Work Secondary CTA: View Projects Also prepare: View Resume Placeholders for: LinkedIn GitHub Email Create a premium hero visual based on the concept: Sales Inventory Production HR Finance Operations flow into Business System Architecture which produces Automation Dashboards Approvals Reports ERP The animation should visually communicate that I connect business functions together. ABOUT SECTION FOUNDATION Create a concise section explaining that my work exists between: Business Analysis System Architecture MIS Automation Software Development Include a visual representation of these disciplines. Do not write a long biography yet. EXPERIENCE SECTION FOUNDATION Create a modern experience timeline/component. Include an initial entry for: Excel Sathi Role: Senior MIS / Digital Transformation / Systems Architecture The exact title and dates will be added later. Build this section so more roles can easily be added. PROJECTS FOUNDATION Create a premium project grid. Each project card should support: - project title - short description - category - role - technologies - thumbnail - status - case study link Initial project placeholders: Business ERP Inventory & Order Management Employee Timesheet System Business Operations / Mini ERP HRMS Calling / Follow-Up System Import Management System AI Business System Builder Do not fabricate detailed content yet. Create filtering categories such as: ERP MIS Inventory HR Automation AI Operations PROJECT CASE-STUDY TEMPLATE Create one reusable project-detail template. It should support these sections: 1. Project Hero 2. Business Problem 3. Before vs After Workflow 4. System Architecture 5. Modules 6. Key Features 7. Product Screens 8. Automation Flow 9. Technology Stack 10. Business Impact 11. What I Learned 12. Next Project Do not populate all project pages yet. Build one flexible reusable template that can later be populated from project data. HOW I BUILD SYSTEMS Create a visual process section: 01 Understand the Business 02 Map the Workflow 03 Identify Bottlenecks 04 Design the Data Architecture 05 Build the System 06 Automate Repetitive Processes 07 Create MIS & Reporting 08 Deploy and Improve This should visually reinforce that I solve business problems, not just coding problems. CAPABILITIES Create grouped capability cards instead of percentage bars. Groups: Business Systems Development Automation Data & MIS AI Deployment Prepare placeholders for skills such as: ERP Architecture Workflow Design Google Apps Script Google Sheets JavaScript HTML CSS API Integration MIS Dashboards Automation Gemini API GitHub CLASP NAVIGATION Create a premium sticky navigation. Sections: Home Projects Experience About Resume Contact If possible, add a command palette using: CMD + K or CTRL + K The command palette should allow quick navigation to projects and sections. MOTION Use premium microinteractions such as: - scroll reveals - smooth section transitions - card hover effects - architecture flow animations - subtle mouse-responsive effects - animated lines between system modules - button interactions - project transitions Animations must remain lightweight and professional. Respect prefers-reduced-motion. RESPONSIVENESS The website must be fully responsive for: Desktop Laptop Tablet Mobile Mobile should feel intentionally designed. TECHNICAL STRUCTURE Use reusable components. Examples: Navbar Hero ProjectCard ProjectGrid ExperienceTimeline ArchitectureDiagram WorkflowDiagram CapabilityCard ContactCTA Footer ProjectCaseStudy Do not duplicate content unnecessarily. PROJECT DATA ARCHITECTURE Create a centralized project data source. For example: projects.js or projects.json Each project should support fields such as: slug title description category role technologies problem solution modules features architecture impact learnings screenshots status Project pages should read from this centralized data wherever possible. QUALITY REQUIREMENTS The website should be: - responsive - fast - accessible - SEO-friendly - cleanly structured - easy to maintain - visually impressive - production-quality Use semantic HTML. Add basic: - page titles - meta descriptions - OpenGraph structure - accessibility labels - keyboard navigation - focus states IMPORTANT For this first build, prioritize: 1. visual design 2. overall architecture 3. reusable components 4. navigation 5. project data system 6. project template 7. responsiveness 8. animation foundation Do NOT spend time inventing detailed project content. We will populate and refine each section with separate prompts after this foundation is built. FINAL OBJECTIVE The website should make someone think: "This person understands how businesses actually operate and can design the systems that run them." Build the foundation now so individual sections can be expanded later without redesigning the whole site.