Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE: Add the ability to republish pages from wiki.python.org as part of the main site #608

Open
ncoghlan opened this issue Mar 8, 2015 · 1 comment
Labels
backend Relates to the backend of the app enhancement This is an improvement to existing code or configuration

Comments

@ncoghlan
Copy link

ncoghlan commented Mar 8, 2015

The Python and PSF wikis are existing collaborative editing solutions provided for use by the community. However, as a consumer of that information, it is often difficult to tell the difference between non-authoritative pages (which may be out of date or otherwise unreliable), and those which are being actively maintained and accurately represent either official PSF policy, or else the best current collective knowledge of the community.

It would be potentially beneficial if there were a way of easily and selectively importing such pages into the main web site, such that the official version was hosted under the main python.org site, rather than only being available on wiki.python.org.

This would require the ability to:
a) extract the content from the MoinMoin wiki
b) process it into a format suitable for inclusion in the main site
c) actually push it live

Ideally, such a feature would be built on the same infrastructure being considered for adding both native CMS capabilities and offline version-controlled editing support.

I don't know if there's currently a public open issue for either of those, but I'm aware from various conversations that the possibility of integrating Django Mezzanine has at least been discussed, and support for Mercurial based offline editing was a goal of the original website redesign RFP. It may be beneficial to consider including a general purpose content aggregation and republication capability, such as that offered by Dexy, as part of that architecture, rather than writing entirely custom integration code that can't be readily adapted to handle new information sources.

@brainwane brainwane added enhancement This is an improvement to existing code or configuration backend Relates to the backend of the app labels Aug 12, 2019
@brainwane
Copy link

I'd like this, and it would help with #161.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Relates to the backend of the app enhancement This is an improvement to existing code or configuration
Projects
None yet
Development

No branches or pull requests

2 participants