Hi Elena,

such repos are good for documentation, but accessibility is rather limited and requiring PRs to add/change content will not exactly be an invitation to people wanting to help curate the content.

Our wiki provides very easy ways to edit content and we make access very easy as well. The level of entry is much lower than for a documentation repo such as the devguide (and I'm not even talking about the necessary CD to turn the repo into the actual content).

As mentioned, the tech is not really the problem. It's finding enough people to engage is curating the content, that is.

PS: I've tried lots of ways of making content editing easier for contributors in my day job as CTO, software architect and project lead. By far the easiest was creating a set of Google Docs, but even with those, it was hard to find and motivate people to provide and curate content. It's really a people problem, not a tech one.

Thanks,

--
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, Mar 01 2025)
Python Projects, Coaching and Support ...    https://www.egenix.com/
Python Product Development ...        https://consulting.egenix.com/
________________________________________________________________________

::: We implement business ideas - efficiently in both time and costs :::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               https://www.egenix.com/company/contact/
                     https://www.malemburg.com/


On 01.03.2025 18:22, Elena Williams via pydotorg-www wrote:
Hello Mats,

Not using the "wiki" part of a github repo -- I agree this is awful! Upon exploring this and another upfront fatal flaw is that file trees are not at all supported.

Perhaps more following the pattern established here:
https://github.com/python/devguide
https://devguide.python.org/


---
Elena Williams
Github: elena <http://github.com/elena/>


On Sun, 2 Mar 2025 at 04:10, Mats Wichmann <m...@wichmann.us> wrote:

    On 3/1/25 10:01, Elena Williams via pydotorg-www wrote:
    > Dear Marc-Andre,
    >
    > Thank you for your prompt and detailed response!
    >
    > Would it be an option to consider moving the wiki to github? It's
    > unambiguously demonstrated that these days that content of the
    scope of
    > the wiki is well within what they are accustomed to.
    There's an absolutely fatal flaw with github-hosted wikis, even more
    than that it's an absolutely terrible wiki implementation: content is
    not made available to search engines for indexing. If we think
    it's too
    hard for people to find stuff via the wiki now, it would get that
    much
    harder. On a project I'm involved in, we're actively looking for
    someplace else to put ours, but we're not a funded project so haven't
    found a solution yet.



_______________________________________________
pydotorg-www mailing list
pydotorg-www@python.org
https://mail.python.org/mailman/listinfo/pydotorg-www
_______________________________________________
pydotorg-www mailing list
pydotorg-www@python.org
https://mail.python.org/mailman/listinfo/pydotorg-www

Reply via email to