Found 307 repositories(showing 30)
pashpashpash
OP Vault ChatGPT: Give ChatGPT long-term memory using the OP Stack (OpenAI + Pinecone Vector Database). Upload your own custom knowledge base files (PDF, txt, epub, etc) using a simple React frontend.
imweb
WEB前端知识库,Frontend Knowledge Base
AndrewNgo-ini
A fully custom chatbot built with Agentic RAG (Retrieval-Augmented Generation), combining Gemini models with a local knowledge base for accurate, context-aware, and explainable responses. Features a lightweight, dependency-free frontend and a streamlined FastAPI backend for complete control and simplicity.
PurpleSchool
PurpleSchool Knowledge Base - единая база знаний по стеку JavaScript для frontend, backend и мобильной разработки, а так же DevOps.
upupmake
A RAG (Retrieval-Augmented Generation) knowledge base system with Vue.js frontend, Spring Boot backend, and FastAPI LLM service.
kaoengine
📗 Form Zero to One: Kao.Engineer
bhuyanamit986
# Frontend Mentor - Stats preview card component solution This is a solution to the [Stats preview card component challenge on Frontend Mentor](https://www.frontendmentor.io/challenges/stats-preview-card-component-8JqbgoU62). Frontend Mentor challenges help you improve your coding skills by building realistic projects. ## Table of contents - [Overview](#overview) - [The challenge](#the-challenge) - [Screenshot](#screenshot) - [Links](#links) - [My process](#my-process) - [Built with](#built-with) - [What I learned](#what-i-learned) - [Continued development](#continued-development) - [Useful resources](#useful-resources) - [Author](#author) - [Acknowledgments](#acknowledgments) **Note: Delete this note and update the table of contents based on what sections you keep.** ## Overview ### The challenge Users should be able to: - View the optimal layout depending on their device's screen size ### Screenshot  Add a screenshot of your solution. The easiest way to do this is to use Firefox to view your project, right-click the page and select "Take a Screenshot". You can choose either a full-height screenshot or a cropped one based on how long the page is. If it's very long, it might be best to crop it. Alternatively, you can use a tool like [FireShot](https://getfireshot.com/) to take the screenshot. FireShot has a free option, so you don't need to purchase it. Then crop/optimize/edit your image however you like, add it to your project, and update the file path in the image above. **Note: Delete this note and the paragraphs above when you add your screenshot. If you prefer not to add a screenshot, feel free to remove this entire section.** ### Links - Solution URL: [Add solution URL here](https://your-solution-url.com) - Live Site URL: [Add live site URL here](https://your-live-site-url.com) ## My process ### Built with - Semantic HTML5 markup - CSS custom properties - Flexbox - CSS Grid - Mobile-first workflow - [React](https://reactjs.org/) - JS library - [Next.js](https://nextjs.org/) - React framework - [Styled Components](https://styled-components.com/) - For styles **Note: These are just examples. Delete this note and replace the list above with your own choices** ### What I learned Use this section to recap over some of your major learnings while working through this project. Writing these out and providing code samples of areas you want to highlight is a great way to reinforce your own knowledge. To see how you can add code snippets, see below: ```html <h1>Some HTML code I'm proud of</h1> ``` ```css .proud-of-this-css { color: papayawhip; } ``` ```js const proudOfThisFunc = () => { console.log('🎉') } ``` If you want more help with writing markdown, we'd recommend checking out [The Markdown Guide](https://www.markdownguide.org/) to learn more. **Note: Delete this note and the content within this section and replace with your own learnings.** ### Continued development Use this section to outline areas that you want to continue focusing on in future projects. These could be concepts you're still not completely comfortable with or techniques you found useful that you want to refine and perfect. **Note: Delete this note and the content within this section and replace with your own plans for continued development.** ### Useful resources - [Example resource 1](https://www.example.com) - This helped me for XYZ reason. I really liked this pattern and will use it going forward. - [Example resource 2](https://www.example.com) - This is an amazing article which helped me finally understand XYZ. I'd recommend it to anyone still learning this concept. **Note: Delete this note and replace the list above with resources that helped you during the challenge. These could come in handy for anyone viewing your solution or for yourself when you look back on this project in the future.** ## Author - Website - [Add your name here](https://www.your-site.com) - Frontend Mentor - [@yourusername](https://www.frontendmentor.io/profile/yourusername) - Twitter - [@yourusername](https://www.twitter.com/yourusername) **Note: Delete this note and add/remove/edit lines above based on what links you'd like to share.** ## Acknowledgments This is where you can give a hat tip to anyone who helped you out on this project. Perhaps you worked in a team or got some inspiration from someone else's solution. This is the perfect place to give them some credit. **Note: Delete this note and edit this section's content as necessary. If you completed this challenge by yourself, feel free to delete this section entirely.**
Aycom366
# Frontend Mentor - Todo app solution This is a solution to the [Todo app challenge on Frontend Mentor](https://www.frontendmentor.io/challenges/todo-app-Su1_KokOW). Frontend Mentor challenges help you improve your coding skills by building realistic projects. ## Table of contents - [Overview](#overview) - [The challenge](#the-challenge) - [Screenshot](#screenshot) - [Links](#links) - [My process](#my-process) - [Built with](#built-with) - [What I learned](#what-i-learned) - [Continued development](#continued-development) - [Useful resources](#useful-resources) - [Author](#author) - [Acknowledgments](#acknowledgments) **Note: Delete this note and update the table of contents based on what sections you keep.** ## Overview ### The challenge Users should be able to: - View the optimal layout for the app depending on their device's screen size - See hover states for all interactive elements on the page - Add new todos to the list - Mark todos as complete - Delete todos from the list - Filter by all/active/complete todos - Clear all completed todos - Toggle light and dark mode - **Bonus**: Drag and drop to reorder items on the list ### Screenshot  Add a screenshot of your solution. The easiest way to do this is to use Firefox to view your project, right-click the page and select "Take a Screenshot". You can choose either a full-height screenshot or a cropped one based on how long the page is. If it's very long, it might be best to crop it. Alternatively, you can use a tool like [FireShot](https://getfireshot.com/) to take the screenshot. FireShot has a free option, so you don't need to purchase it. Then crop/optimize/edit your image however you like, add it to your project, and update the file path in the image above. **Note: Delete this note and the paragraphs above when you add your screenshot. If you prefer not to add a screenshot, feel free to remove this entire section.** ### Links - Solution URL: [Add solution URL here](https://your-solution-url.com) - Live Site URL: [Add live site URL here](https://your-live-site-url.com) ## My process ### Built with - Semantic HTML5 markup - CSS custom properties - Flexbox - CSS Grid - Mobile-first workflow - [React](https://reactjs.org/) - JS library - [Next.js](https://nextjs.org/) - React framework - [Styled Components](https://styled-components.com/) - For styles **Note: These are just examples. Delete this note and replace the list above with your own choices** ### What I learned Use this section to recap over some of your major learnings while working through this project. Writing these out and providing code samples of areas you want to highlight is a great way to reinforce your own knowledge. To see how you can add code snippets, see below: ```html <h1>Some HTML code I'm proud of</h1> ``` ```css .proud-of-this-css { color: papayawhip; } ``` ```js const proudOfThisFunc = () => { console.log('🎉') } ``` If you want more help with writing markdown, we'd recommend checking out [The Markdown Guide](https://www.markdownguide.org/) to learn more. **Note: Delete this note and the content within this section and replace with your own learnings.** ### Continued development Use this section to outline areas that you want to continue focusing on in future projects. These could be concepts you're still not completely comfortable with or techniques you found useful that you want to refine and perfect. **Note: Delete this note and the content within this section and replace with your own plans for continued development.** ### Useful resources - [Example resource 1](https://www.example.com) - This helped me for XYZ reason. I really liked this pattern and will use it going forward. - [Example resource 2](https://www.example.com) - This is an amazing article which helped me finally understand XYZ. I'd recommend it to anyone still learning this concept. **Note: Delete this note and replace the list above with resources that helped you during the challenge. These could come in handy for anyone viewing your solution or for yourself when you look back on this project in the future.** ## Author - Website - [Add your name here](https://www.your-site.com) - Frontend Mentor - [@yourusername](https://www.frontendmentor.io/profile/yourusername) - Twitter - [@yourusername](https://www.twitter.com/yourusername) **Note: Delete this note and add/remove/edit lines above based on what links you'd like to share.** ## Acknowledgments This is where you can give a hat tip to anyone who helped you out on this project. Perhaps you worked in a team or got some inspiration from someone else's solution. This is the perfect place to give them some credit. **Note: Delete this note and edit this section's content as necessary. If you completed this challenge by yourself, feel free to delete this section entirely.**
Ritahchanger
A comprehensive, structured, and practical knowledge base for mastering system design concepts, microservices, and real-world architectures with tutorials, patterns, and case studies for frontend, backend, and distributed systems.
MagicMooc
frontend-knowledge-base
jinjun1994
【前端学习+面试指南】 涵盖前端工程师必需的核心知识库
romanyn36
AI-powered agent leveraging RAG (Retrieval-Augmented Generation) with tool integration capabilities. Built with langchain, OpenAI, FastAPI, React frontend, it combines document-based knowledge with real-time data access and calculation tools to provide context-aware responses.
FangzhouSu
利用Vuepress部署到线上的前端知识库——构建自己的前端知识体系!站在前端er的角度上总结数据结构与算法的内容。
jiusanzhou
Agent-friendly knowledge base editor. Pure frontend. Your data, your control. 🌐 https://motion.wencai.app
yongzhenzh
A full-stack chatbot platform that utilizes dual-path Retrieval-Augmented Generation (RAG) for personalized medical Q&A. Built with a FastAPI backend, with both local and online LLM support and a modern Vite-based frontend (Vue). Uses FAISS and BGE embeddings for semantic search over mock user health records and a medical knowledge base.
ihimanshu29
An enterprise-grade, full-stack AI travel planner which provides data-driven itineraries for Lucknow, India and showcases production-ready architecture, combining a FastAPI backend with a Streamlit frontend. It leverages an advanced agentic RAG system, context-aware responses by integrating a local knowledge base with live, external APIs.
rajdeepk012
Company knowledge base RAG app - PDF ingestion, ChromaDB vector store, hybrid retrieval, FastAPI backend, Streamlit frontend.
zhengliu92
This project implements a lightweight Retrieval-Augmented Generation (RAG) system using a microservices architecture. It includes embedding, file storage, main RAG, document parsing, API gateway, and frontend services. Suitable for knowledge base, intelligent Q&A, and similar scenarios.
govuk-one-login
Frontend for the Knowledge Based Verification Credential Issuer
shubhranshu-sahu
CampusAssist-AI is an AI-powered campus helpdesk using Retrieval-Augmented Generation (RAG) to answer student queries on college processes, notices, and faculty info. It features a decoupled frontend-backend architecture, role-based access, and an admin-managed knowledge base built with free Google technologies.
NavodyaDhanushka
This full-stack RAG (Retrieve, Augment, Generate) application features a React frontend and Python backend. It enables users to ask questions, get concise answers powered by GPT-4, and view relevant documents. Additionally, users can index websites, enriching the knowledge base. LangChain enhances information retrieval and content generation.
jeezy05
Math Agent is an agentic Retrieval-Augmented Generation (RAG) system designed to replicate a mathematical professor. It answers math questions with step-by-step solutions, using a knowledge base, web search (MCP), guardrails, and a human-in-the-loop feedback mechanism. The system is built with FastAPI (backend), React (frontend), Qdrant (vector DB)
ForeverGreenDam
这是一个前后端分离RAG知识库项目,主要使用的AI框架是LangChain4j,使用的向量数据库为Redis。目前项目正在开发初期。This is a frontend-backend separated RAG knowledge base project, primarily utilizing the LangChain4j AI framework and Redis as the vector database. The project is currently in the early stages of development.
A java software aimed to be a plugin in Web Applications that parses structured languages and invokes defined functions to consume the parsed data. The parsing is defined as seperate input languages allowing the system to catter for multiple languages concurrently. A queriable semantic network is also available common to all input languages that catters for the dynamic portions of the system's knowledge. Currently, the input languages are defined as XML files, and made available to the system at startup. The semantic network is also defined as an XML file which is re-loaded by the system whenever the system detects any changes made, hence allowing the semantic network to be updated on-the-fly. It is hoped that in future, the language definitions and semantic network will be changed to database-based instead of file-based storage, with a GUI frontend to edit. The system currently doesn't support parsing recursive structured languages, like SQL SELECT statements containing other SQL SELECT statements. It is hoped that this too will change in the future.
rebornstar1
No description available
qqingzheng
No description available
No description available
apteles
Base de Conhecimento (Frontend) 🚀
jjipper
삐약 개발자의 프론트엔드 지식 수집소
基于Element-Plus-X的AI知识库网站