How ayush-that/finveda works
Main Components
• Frontend:
• Two distinct front-end sections are visible:
• The modern single-page application (SPA) under Finveda/Finveda – which uses Vite, React components (e.g., App.jsx, main.jsx), and a public folder with assets.
• Numerous static HTML pages (index.html, blog.html, about.html, etc.), assets (CSS, fonts, images), and tools that serve as educational content and interactive financial tools.
• Backend:
• Node.js/Express server (located in the server directory) with controllers, models, and routes that handle operations like blog submissions, contact forms, newsletter subscriptions, and feedback.
• Python-powered microservice for the “news” feature (found in news/backend and Finveda/news/backend); this likely serves a separate news API integrated in the overall ecosystem.
• External Services & Integrations:
• AI-powered consultant (as per the README, “Arth Sathi”) which may interact with external APIs or internal logic.
• Email services (see server/utils/sendMail.js and sendNewsletter.js for handling communication).
• GitHub Actions workflows for CI/CD (under .github/workflows) are used to automate testing, pull request management, etc.
• Tools & Utility Modules:
• Several client-side JavaScript tool files (e.g., calculators, financial tools in the tools directory) exist as independent modules but are integrated into the overall user interface.
• Additional pages for games and quizzes.
Relationships and Interactions
• The Frontend interacts with:
• The Node.js server (via RESTful API calls) for operations like posting blog entries or sending contact form submissions.
• The Python “news” microservice for fetching the latest market news and trends.
• Integrated calculators and interactive tools that are executed on the client side.
• The Node.js server uses:
• Controllers (addBlogController, contactController, feedbackController, newsletterController) to manage business logic.
• Models (Newsletter, addBlog, etc.) for data representation and persistence.
• Utility modules (db.js, sendMail.js) to connect to databases or external emailing services.
• CI/CD pipelines automate tests and integrations so that frontend and backend deployments remain in sync.
Architectural Patterns and Design Principles
• Separation of Concerns: You have clear separation between presentation (frontend) and processing logic (backend controllers, services) which enhances maintainability.
• Modular Design: Distinct modules for controllers, routes, models, and tools ensure that features are loosely coupled.
• Potential Microservices: The news service appears to be a separate “microservice” (implemented in Python) that might scale or be maintained independently.
• Use of Modern Development Tools: Leveraging Vite/React for the SPA and GitHub Actions for CI/CD reinforces modern development practices.
Relevant Technologies
• Frontend: HTML5, CSS3 (and preprocessors like SASS), JavaScript (React/Vite).
• Backend: Node.js with Express, Python (for the news backend), and associated dependency management (npm for Node, requirements.txt for Python).
• Build/Deploy: Vite’s configuration file (vite.config.js) indicates bundling practices for the SPA; GitHub Actions workflows manage CI/CD.
• Communication: RESTful API calls between front-end and backend; potentially AJAX calls for interactive tools.