holoviz / panel

Panel: The powerful data exploration & web app framework for Python
https://panel.holoviz.org
BSD 3-Clause "New" or "Revised" License
4.78k stars 518 forks source link

In the website docs, include a link on every doc page to the Github .md source for that document #6494

Open Coderambling opened 8 months ago

Coderambling commented 8 months ago

Being able to go straight to the Github .md if an improvement or type is noticed in a doc would make the process more seamless. As it is now, a doc source needs to be located manually in Github.

HarshaDokula commented 7 months ago

hi @philippjfr ,

I am willing to work on this issue. Which branch is used for the docs and any additional things I should know about ?

Coderambling commented 7 months ago

Hi @HarshaDokula . That would be great! Quoting @MarcSkovMadsen "One challenge is that the reference guides are created from notebooks that are rendered during build and copied into the docs folder. But that challenge can probably be solved."

I think Sphinx is used for the build process, but I don't know further details.

Example of a webpage and associated Github notebook location:

Website page:

https://panel.holoviz.org/reference/panes/Alert.html

Notebook location on Github:

https://github.com/holoviz/panel/blob/main/examples/reference/panes/Alert.ipynb

So I guess if every Notebook would contain a (Github icon) with a hyperlink to its Github location, that would solve it. So how to add that (programmatically) in each Notebook?

The top of each page already contains an Open in Jupterlyte link, and download this Notebook link, but that one goes to the raw version: https://raw.githubusercontent.com/holoviz/panel/main/examples/reference/panes/Alert.ipynb

I don't know if those links are manually created.

But maybe the Notebook could include a var like (pseudocde)

Raw_url = var containing raw.githubuser... from the download link.

Github_url = replace the Raw _URL substring "https://raw.githubusercontent.com/" with "https://github.com/holoviz/panel/blob/main/examples/"

And then use that Github_url with icon / hyperlink text that says: Acces / fork in Github.

philippjfr commented 7 months ago

@HarshaDokula That would be fabulous! The majority of the documentation lives in /doc. The exception are the component reference docs which live as notebooks in /examples/reference.

HarshaDokula commented 7 months ago

@Coderambling, Thank you for the information.

@philippjfr , I have understood where the documentations are available.

installation_error.txt

Thank you.

Coderambling commented 7 months ago

Hi @HarshaDokula. Great find that extension! Hope it works in this context. No idea about the installation error :-)

Coderambling commented 7 months ago

Hi @HarshaDokula . Great find that extension! Hope it works in this context.

No idea about the installation error :-) What environment are you setting up in?

HarshaDokula commented 7 months ago

Hi @Coderambling , I have setup on a different environment now, It is working. Still have no idea what happened in the previous environment. Working on the issue now.

Coderambling commented 7 months ago

What environment are you using currently?

HarshaDokula commented 7 months ago

dev_details_previous.txt devENV_details_current.txt

Coderambling commented 7 months ago

Hey @HarshaDokula , are you aware of the Panel Discord channel? https://discord.com/invite/Hh8WPK63

HarshaDokula commented 7 months ago

@Coderambling , yes. Username : harshadokula