First of all, thanks for reviving this topic. 2025 is looking a lot
calmer than 2024, and hopefully this is the kind of stuff I can allocate
some time for.
On 12/21/24 4:45 PM, Pierre-Yves David wrote:
On 12/20/24 15:47, PIERRE AUGIER wrote:
----- Mail original -----
De: "Pierre-Yves David"<pierre-yves.da...@octobus.net>
À: "PIERRE AUGIER"<pierre.aug...@univ-grenoble-alpes.fr>, "Mercurial
Devel"<mercurial-de...@mercurial-scm.org>
Envoyé: Vendredi 20 Décembre 2024 15:34:33
Objet: Re: Urgency of updating Mercurial website and
initiatehttps://mercurial-scm.readthedocs.io ?
Why do you need a new repository for that? I think we can reuse the
existing website repository for the new version of the repository.
Because I was thinking that Mercurial maintainers want to
keephttps://www.mercurial-scm.org/ and that I could propose something else
hosted somewhere else.
I'd want to improve the website overall, it currently is basically
static, hosted on a VM we have control over.
Ifhttps://www.mercurial-scm.org can be static (I think it can), I can also
propose something to replace it. However, I have to admit that I don't know
anything about web things. I just know how to produce documentation websites
based on Sphinx, myst and Jupyter. It would make sense to use such tools
because there is a lot of content in Mercurial source in rst and Sphinx knows
how to render that. For a project with not so much man power, it could make
sense to go in this direction.
Just in case I misunderstand this, I'm -1 on having the website only be
a documentation website and using documentation tooling, but I think
you're only talking about the... well "docs" part of it. I have no
experience building Python documentation (insert rambling about how Rust
fixed that problem ;) ), but I can definitely review.
A good option for smaller iterative steps might be to start with this
documentation focused "section" and link to it from the main site.
Then update the rest of the main site. It would allow you to focus on
what you are familiar with for now.
+1 to this, you can start with building a better doc and we can link it
from the website.
I think the revamp of the website can only happen with someone with some
web experience, and although I do have a good amount of web experience
from a previous job, I don't know if I would trust myself with the
design itself. So let's start with contents first, as Pierre-Yves suggested.
As far as I understand, Raphaël is currently the one with most
interest and knowledge about website, so I'll let him chime in when he
is back from vacation.
I could reusehttps://foss.heptapod.net/mercurial/hg-website but there would be
first a big commit to remove everything :-) So it might make sense to start in
a new repo. I could also use a new name branch
inhttps://foss.heptapod.net/mercurial/hg-website. What do you think?
We can start in a topic there, and decide if we want it to be named
branch while it settle later.
--
Pierre-Yves David
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
