Add a link to site source from the bottom

[techtonik]

Site needs a link to source code. Right now there is no way people can see it is open source. It can be made with icon and include icons for other channels used for site development.

? how can I add easy-pickling label to the issue, or who does that

[nedbat]

A colophon page laying out the technologies used to make the site would be great, and the link to the source code could go on that page. No need to link from the bottom of each page.

[techtonik]

I think that is a bad UX decision. When user sees an error, that user should click the link and go to the page where the user can edit the file and send a pull request. YMMV, but dedicated pages with vast texts are outdated. tl;dr revolution came somewhere in the middle of old and new python.org design. I personally don't like to search for pages that enable this primary feature for community operated site.

? still who can add easy-pickling labels here

[merwok]

I agree with Ned. An edit link on each page makes sense when each page can be edited (e.g. Sphinx documentation source), but for a website where some things are in templates, some things in PO or JSON files and most of the contents in the database, there isn’t such a 1:1 mapping. (A “report bugs” link on each page is valuable though.)

[birkenfeld]

I agree that there should be a link to this github repo.

[techtonik]

there isn’t such a 1:1 mapping

Not yet. I smb. wants python.org to be educational resource also, they should have this in mind. Cloud editors already allow to represent more than one file. Chrome provides list of all used resources, so having such mapping (along with DB content patch editor) is just a matter of time.

But for the scope of this issue I'd just put octocat to the basement and think about anything else later.

[nedbat]

These pages all have a lot of page-noise on them, and sending people directly to github means that we've lost the opportunity to explain the site to them first. Before we dump them into a pile of source code, let's give them a page where we get to explain how the site was made, why those technologies were chosen, etc.

The percentage of people who will want to modify the source is tiny: <0.5%. The number of people who will want to learn how the site was made is much larger: ~10% (these numbers are made up!)

[techtonik]

(these numbers are made up!)

That's the point. We won't reach the consensus until there is poll system running (or, ideally, statistics).

Now for the specific change. You don't explain Twitter icon, why do you want to explain Github? This button is for folks like me who get it. You're free to explain site source to those who are not able to get Github (and my guess that 95% of those won't be able to setup the site anyway), but it is a separate feature. Let's do things incrementally. If you feel it is important - it is better to open a separate enhancement request. There I will tell you that the site carries much less educational value than it could, because it carries the code that you won't reuse in your projects.

[nedbat]

I guess we see things differently, and it isn't our decision anyway. I'd add a link to the bottom the page that says "How we made this site" or something like that. It would link to a colophon page with details of all the tech, including a link to github. The people who understand github would find what they need.

[techtonik]

Source code should be one click away. That's important.

[malemburg]

On 28.02.2014 12:11, anatoly techtonik wrote:

Source code should be one click away. That's important.

Anatoly, use a bookmark, then it's one click away ;-)

Not everyone visiting the site wants to see the code running it.

I agree with the others that a colophon page would be a good place
to put such a link.

Marc-Andre Lemburg

[techtonik]

Not everyone visiting the site wants to see the code running it.

It is programming language site. Of course everybody wants to see the code. You want, so why do you think that everybody else is less smart?

[malemburg]

On 28.02.2014 12:17, anatoly techtonik wrote:

Not everyone visiting the site wants to see the code running it.

It is programming language site. Of course everybody wants to see the code. You want, so why do you think that everybody else is less smart?

The site is intended for a much larger audience than just developers:

http://pythonorg-redesign.readthedocs.org/en/latest/#audiences

It's good to have a link to the repository on the site, but it doesn't
have to be on every single page.

Marc-Andre Lemburg

[techtonik]

I am not asking for top level stripe "Fork me on GitHub". Among all stuff the link to repository is more useful than anything else in the footer. I'd move those from the bottom.

[CarlFK]

I found this page:

https://www.python.org/community/sigs/current/meta-sig/
which has a bunch of html tags rendering.

It bothers me that i don't know how to report it.
I looked to the bottom of the page, didn't see anything.
I opened About in a new tab, pfft.. huge wall of text. skim skim, didn't see anything.
So I searched my inbox for this email I seem to remember. found a link to this issue, so here I am.

I'll go post a proper issue now, but this one I think is way more important.

Please put a link to the repo on every page.

[merwok]

I found this page: https://www.python.org/community/sigs/current/meta-sig/
which has a bunch of html tags rendering.

Could you post a screenshot? The page looks fine for me. (I hope the site doesn’t use client-side markdown-to-html conversion like the PyCon website!)

It bothers me that i don't know how to report it.

Agreed. Half a dozen issues were opened about the contact form that was present at site launch; I’m sure consensus will be reached and a clear link will be added to the appropriate place.

I opened About in a new tab, pfft.. huge wall of text. skim skim, didn't see anything.

I think that page is “About Python”, not “About this website”.