[pydotorg-www] UBY, BUG: Responsive wiki templates, ENH: MoinMoin git storage, DOC: Guidelines for citations, ENH: Custom search engine?
wes.turner at gmail.com
Fri Dec 6 10:39:22 EST 2019
The psf infrastructure team may have something to say about whether
upgrading moinmoin is a priority.
Creating a local instance for theme development should be pretty easy.
The first search result for "moinmoin responsive" appears to be based on
Bootstrap 3.2.0 from circa 5 years ago:
Bootstrap v3.3.7 is the latest 3.x, for which there are many free and paid
themes. That's a pretty much just a drop-in upgrade.
Would it be as simple as adding the logo SVG and links to the sidebar?
That Makefile I shared pushes to the master and wiki branches (and then
pushes the built HTML to the gh-pages branch). Pull requests against the
master branch could easily be merged to the restricted wiki branch
automatically or with severely diligent human review. Though, I'm sure
there are a number of folks who would be hesitant to abandon moinmoin
maintenance by converting from moin syntax to RestructuredText (or
Markdown) with moin2rst or pandoc and just hosting with e.g. ReadTheDocs.
Not a high priority for me personally, but there's definitely knowledge
that's not being captured to the wiki that could help everyone.
On Fri, Dec 6, 2019, 9:26 AM Mats Wichmann <mats at wichmann.us> wrote:
> On 12/2/19 6:04 PM, Wes Turner wrote:
> > UBY,BUG: Create responsive wiki templates
> > The wiki pages are not readable on mobile because the templates aren't
> > responsive.
> Sorry about that, I thought by sending you here it would draw some
> After having a brief poke around I don't think MoinMoin directly
> supports a "responsive" design, though some people appear to have tried
> to get there via themes. There appears to have been a Summer of Code
> project almost a decade ago now but I'm not finding evidence that went
> mainstream. At this point, I don't even know who "runs" the moinmoin
> instance... sigh. Projects run by voluteers, you gotta love em'!!! I
> *think* our version is fairly old, and I'm not recalling any real
> appetite for upgrading.
> I have some experience with github wikis, I find them horrid, really
> wouldn't want to go that way unless there's considerable extra stuff to
> soup them up (your hybrid wiki/sphinx might fit that bill). The PR
> mechanism doesn't extend to the wikis yet, afaik.
> -- mats
> > There are docs for the python.org <http://python.org> site and the
> > Jinja2 templates and CSS are on GitHub:
> > - https://pythondotorg.readthedocs.io/
> > - https://github.com/python/pythondotorg/blob/master/templates/base.html
> > Where are the MoinMoin Jinja2 (?) templates and CSS sources hosted?
> > Who owns these?
> > The site design team did a great job.
> > For the wiki, responsive breakpoints and minimal headers above the fold
> > would be great.
> > Would it be easier to adapt/fork/brand/recognize existing responsive
> > MoinMoin templates?
> > ...
> > ENH: MoinMoin git storage / backend?
> > A git backend with a repo in GitHub and evented bidirectional
> > synchronization might get the wiki the attention it needs.
> > -
> > People have moved to gh-pages, awesome lists (and hybrid GH wikis w/
> > Sphinx renders thereof [x]) for a multitude of reasons, I think. The
> > pull request workflow is very familiar to maintainers now.
> > - https://devguide.python.org/
> > - https://docs.python.org/
> > - https://discuss.python.org/
> > - https://duckduckgo.com/?q=awesome+python+site%3Agithub.com
> > - https://github.com/quobit/awesome-python-in-education
> > [x] https://github.com/westurner/wiki/issues/5
> > [y] https://github.com/westurner/wiki/blob/master/Makefile#L294
> > ...
> > DOC: Guidelines for citations
> > I'm sending this to this list per a discussion and request in
> > "[python-dev] Mixed Python/C debugging" regarding the wiki and also
> > whether it's appropriate to reference e.g. third-party libraries and
> > tools that I just found in: the devguide, the wiki, the mailing list(s),
> > discuss.python.org <http://discuss.python.org>, StackOverflow, GitHub?
> > ...
> > ENH: Custom search engine?
> > Maybe we don't even need a custom search engine because a
> > 'site:python.org <http://python.org>' search query is sufficient to
> > search the Python community(s) for tools and resources?
> > _______________________________________________
> > pydotorg-www mailing list
> > pydotorg-www at python.org
> > https://mail.python.org/mailman/listinfo/pydotorg-www
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pydotorg-www