Conversation
Resolves #1994
|
Simple POC. |
|
I am not sure we want to document the use of third party Docker images that did not receive any update (or Docker build) for almost two years now. I would at least use the Docker images built by Quarto: https://github.com/orgs/quarto-dev/packages?repo_name=quarto-cli EDIT: also, the "forge" does not keep versions. |
|
Sure, I can update the PR (later today) to use the official Docker images. I wasn't really sure about the status for "Quarto Forge". Any other things that you think should be updated / improved? Added: It seems the Forge Docker images are stuck on 1.4 and "Published 7 months ago": |
The images from Quarto Forge are not well-maintained.
|
Just for the record: The PR is updated / corrected - ref commits. |
cderv
left a comment
There was a problem hiding this comment.
Thanks for the suggestion.
We are at the limit of how we want to document things here. Quarto documentation aims to details what is directly supported by quarto publish.
Gitlab pages is not among this. This means it could be part of Other Services we document.
So I would be incline to move it here so that it is not confusing. Maybe we'll do a quarto publish gitlab-pages one day.
docs/publishing/_providers.md
Outdated
| |----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| | [Quarto Pub](/docs/publishing/quarto-pub.qmd) | Publishing service for Quarto documents, websites, and books. Use Quarto Pub when you want a free, easy to use service for publicly available content. | | ||
| | [GitHub Pages](/docs/publishing/github-pages.qmd) | Publish content based on source code managed within a GitHub repository. Use GitHub Pages when the source code for your document or site is hosted on GitHub. | | ||
| | [GitLab Pages](/docs/publishing/gitlab-pages.qmd) | Publish content based on source code managed within a GitLab repository. Use GitLab Pages when the source code for your document or site is hosted on GitLab. | |
There was a problem hiding this comment.
This tables is currently only listing what is available through quarto publish. Any other provider is supposed to be mentioned in Other services.
It could be confusing to put Gitlab pages at first level, as it is not directly supported in quarto publish gitlab-pages
|
|
||
| There s currently only one way to publish Quarto websites and documents to GitLab Pages: | ||
|
|
||
| 1. Use a [GitLab Pipeline] to automatically render your files (a single Quarto document or a Quarto project) and publish the resulting content whenever you push a source code change to your repository. |
There was a problem hiding this comment.
Is this missing an external link or aim is to reference the section below ?
For the later case, I think we should make the link explicit using an explicit id.
There was a problem hiding this comment.
I'm just using the same trick (?) that is used in github-pages.qmd: A link with no target pointing to an anchor for a heading on the same page.
Valid point. I had not fully understood the structure of the documentation. I'll clean up my PR. (Yes, |
|
I have updated the PR. PS! I can remove "GitLab Pages" form |
Resolves quarto-dev/quarto-cli#1994