Skip to content

Addition of FAQ section on the official website of hvPlot website #1060

Description

@DevanshRaizada

The FAQ section is missing on the hvPlot library website and the addition of the section would be of great help to all the users

Is your feature request related to a problem? Please describe.

Basic questions like ''What objects can I use hvPlot with?'' can be answered very easily

Describe the solution you'd like

A FAQ section covering all the fundamental question that comes to one's mind in the first place.

Additional context

An FAQ section is a vital section of any product website and is been missing on the hvPlot website.
If given a chance I would love to contribute on this issue.

Activity

  1. transferred this issue fromholoviz/holovizon Apr 19, 2023
  2. MarcSkovMadsen commented on Apr 19, 2023

    @MarcSkovMadsen
    Collaborator

    @droumis . Would a FAQ contribution be welcome?

  3. maximlt commented on Apr 21, 2023

    @maximlt
    Member

    Hi @DevanshRaizada,

    I'm not sure the documentation should have a FAQ. Some of the HoloViz websites have a FAQ and I'm not convinced about their usefulness, as they end up being just a grab bag of random stuff, that possibly wasn't well documented elsewhere, either because of the documentation structure or content.

    Panel's documentation is being reworked and structured following the Diataxis framework. hvPlot documentation will have a similar fate, we don't have yet a timeline for that. A FAQ section is not part of the framework.

    An FAQ section is a vital section of any product website

    I checked a few documentation sites, like from pandas, numpy, matplotlib, and saw no FAQ there. I guess there's a difference between more traditional product websites, and software documentation.

    What would you like to find in an hypothetical hvPlot's FAQ?

  4. droumis commented on Apr 24, 2023

    @droumis
    Member

    I agree that a standalone FAQ page will probably not be included in the changes coming to the hvPlot website, but the information that would go in there should be readily accessible in the docs. Being tuned in to various forums, devs should have a sense of what the frequently asked questions are.

    If there is some information that should be in the docs (or more clear/accessible), feel free to open an issue about it, even if you don't know where it should go. If you have a usage question that needs answering, the best place to ask is probably our Discord, where things get effectively upvoted as people find them more useful.

  5. locked and limited conversation to collaborators on May 12, 2025
  6. converted this issue into a discussion #1567 on May 12, 2025
  7. added
    [OLD] type: discussionOld labels for Discussion-type issues. Convert new Issues of this type to GitHub Discussions.
    on Sep 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    [OLD] type: discussionOld labels for Discussion-type issues. Convert new Issues of this type to GitHub Discussions.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions