Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[doc] Refactor the online doc, simple the sidebar #267

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

NeoZhangJianyu
Copy link
Collaborator

Refactor the online doc structure.

Hope this is the new base of online doc, so that more improvement/refactor could be handled based it.

The reviewer could create comments or update the branch directly.

Here is my updated online doc demo: http://tgl-gen12-tce.sh.intel.com:8000/latest/index.html. All update will be shown in this demo web site. Please compare with current online doc: https://opea-project.github.io/latest/index.html.

Update list:

  • Update the structure of documents in online doc page. No any content is changed.

  • Reduce the navigator depth to 2 in sidebar.

  • Move GenAI* to first level directory: projects.

  • Short the first level directory's' name

  • Every first level directory has one entry page. All other pages in this directory should be linked in the entry page or sub linked pages.

  • Add first level directory:

    1. Tutorial. Content comes from the docs/examples.
    2. Repo link of OPEA.
  • Ignore some warnings which block online doc building.

  • This refactor make some documents can't be navigated in online doc website. If we need these documents, we must update the Entry page or sub linked pages to add link to them. When add link of missed pages, please check if the content is duplicated.

  • The building time of online doc is shorted from 2 mins to 10 seconds.

  • Rm the tailed space of lines.

@joshuayao joshuayao linked an issue Jan 6, 2025 that may be closed by this pull request
Copy link
Contributor

@louie-tsai louie-tsai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good. minor feedbacks

@@ -45,7 +45,7 @@ The ChatQnA example is designed to be a simple, yet powerful, demonstration of
the RAG architecture. It is a great starting point for developers looking to
build chatbots that can provide accurate and up-to-date information to users.

To facilitate sharing of individual services across multiple GenAI applications, use the GenAI Microservices Connector (GMC) to deploy your application. Apart from service sharing , it also supports specifying sequential, parallel, and alternative steps in a GenAI pipeline. In so doing, it supports dynamic switching between models used in any stage of a GenAI pipeline. For example, within the ChatQnA pipeline, using GMC one could switch the model used in the embedder, re-ranker, and/or the LLM.
To facilitate sharing of individual services across multiple GenAI applications, use the GenAI Microservices Connector (GMC) to deploy your application. Apart from service sharing , it also supports specifying sequential, parallel, and alternative steps in a GenAI pipeline. In so doing, it supports dynamic switching between models used in any stage of a GenAI pipeline. For example, within the ChatQnA pipeline, using GMC one could switch the model used in the embedder, re-ranker, and/or the LLM.
Upstream Vanilla Kubernetes or Red Hat OpenShift Container
Platform (RHOCP) can be used with or without GMC, while use with GMC provides additional features.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

chatqna_flow_chat.png might be duplicated with mermaid workflow chat. might be good to keep one.


Single Node
***********

.. toctree::
:maxdepth: 1
:glob:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -9,7 +9,7 @@ AgentQnA Sample Guide
Overview
********

This example showcases a hierarchical multi-agent system for question-answering applications.
This example showcases a hierarchical multi-agent system for question-answering applications.

Purpose
*******
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

possible to use same mermaid workflow from github readme?

@louie-tsai
Copy link
Contributor

@NeoZhangJianyu possible to address the feedbacks? hope to get merged into 1.2

@yinghu5 yinghu5 self-requested a review January 26, 2025 01:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] Duplicate subheadings in v1.1 documentation
3 participants