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

New main page now that docs reside in doc.pytest.org #1708

Closed
nicoddemus opened this issue Jul 8, 2016 · 13 comments
Closed

New main page now that docs reside in doc.pytest.org #1708

nicoddemus opened this issue Jul 8, 2016 · 13 comments
Labels
type: docs documentation improvement, missing or needing clarification

Comments

@nicoddemus
Copy link
Member

Now that http://doc.pytest.org is officially up, I propose we change our pytest.org landing page.

pytest.org currently is the same index page for the docs, but I see that other projects usually follow a different direction, containing a short project description, a short snippet right at the beginning and proper links to the rest of the documentation, contact, etc etc. I would say pretty much like our current README.

Examples:

In order to do that, we would probably move a few things in docs, but I propose to keep index.rst as the main docs page, and create another landing-page.rst or something like this (suggestions welcome), and only it would be uploaded to pytest.org, with proper links to http://doc.pytest.org.

I think it would be really nice to have this for 3.0.

cc @pfctdayelise @hackebrot

@nicoddemus nicoddemus added the type: docs documentation improvement, missing or needing clarification label Jul 8, 2016
@pfctdayelise
Copy link
Contributor

I think this is a great idea. Some pages like the list of talks/tutorials and the pages on adopt pytest month and the sprint, shouldn't really be part of the docs IMO. Maybe a page on the history of the project and philosophy too (eg prioritising backwards compat).

Should we try to preserve documentation links (eg http://pytest.org/latest/fixture.html#fixture goes to some page about fixtures) or do we accept a one-time mass breaking of links? I'm not sure if you're proposing that the docs are still accessible under pytest.org/ pages, or only docs.pytest.org/

@nicoddemus
Copy link
Member Author

or do we accept a one-time mass breaking of links?

I think so, unless someone has a solution to avoid this.

I'm not sure if you're proposing that the docs are still accessible under pytest.org/ pages, or only docs.pytest.org/

Only through doc.pytest.org, I think.

Any chance of someone tackling this before 3.0? 😁

@The-Compiler
Copy link
Member

I think we really should try having some kind of forward rules in pytest.org's webserver config. Breaking links is really frustrating for people, and we have a lot of pages linking to pytest docs I'd imagine.

@nicoddemus
Copy link
Member Author

That would be neat... we could redirect every pytest.org/latest/* to doc.pytest.org/latest/*. Do you know how to do it @The-Compiler? I'm sure @hpk42 would give you access to configure this. 😁

@hackebrot
Copy link
Member

I think this is a great idea and goes well with our overall concept for the documentation.

I'd prefer if we refer to the documentation as http://docs.pytest.org/ rather than doc. Seems to be the more common term (and I like it better than doc). 😄

That's also how I will refer to it during my talk and both docs and doc already work from a technical standpoint.

@hackebrot
Copy link
Member

FYI: I personally won't be able to contribute much to the docs reorganization at this point, as I am busy with my presentation. 😿

@nicoddemus
Copy link
Member Author

Oh I didn't know both doc and docs worked... I agree, personally I also like "docs" better.

@The-Compiler
Copy link
Member

That would be neat... we could redirect every pytest.org/latest/* to doc.pytest.org/latest/*. Do you know how to do it @The-Compiler? I'm sure @hpk42 would give you access to configure this. 😁

Depends on the webserver used (Apache, I think?). For Apache I did it some years ago, I guess I could figure it out.

@nicoddemus
Copy link
Member Author

It should be simple for someone who has done it before. Would you mind ask @hpk42 to give you access on signal or by email? I'm not sure Holger is getting notifications from GH.

@The-Compiler
Copy link
Member

The-Compiler commented Jul 11, 2016

done (the asking, that is - not the redirect)

@nicoddemus
Copy link
Member Author

Thanks! Just a note: the redirect must be from http://pytest.org/latest to http://docs.pytest.org/en/latest.

@The-Compiler
Copy link
Member

@hpk42 added the redirect, seems to work fine! 👍

@nicoddemus
Copy link
Member Author

Awesome! 😁

nicoddemus added a commit that referenced this issue Aug 23, 2016
* Changed "index" to be more similar to the README (#1708).
* Fixes numerous issues like missing documents, syntax errors, etc (#1829, #432).
* Mention all docs in "contents.rst" so it's easier for users to locate (#1112).
* Add doc generation and checking to Travis and AppVeyor, to avoid re-introducing errors.

Fixes #432, Fixes #1112, Fixes #1708, Fixes #1829
nicoddemus added a commit that referenced this issue Aug 23, 2016
* Changed "index" to be more similar to the README (#1708).
* Fixes numerous issues like missing documents, syntax errors, etc (#1829, #432).
* Mention all docs in "contents.rst" so it's easier for users to locate (#1112).
* Add doc generation and checking to Travis and AppVeyor, to avoid re-introducing errors.

Fixes #432, Fixes #1112, Fixes #1708, Fixes #1829
nicoddemus added a commit to nicoddemus/pytest that referenced this issue Aug 23, 2016
* Changed "index" to be more similar to the README (pytest-dev#1708).
* Fixes numerous issues like missing documents, syntax errors, etc (pytest-dev#1829, pytest-dev#432).
* Mention all docs in "contents.rst" so it's easier for users to locate (pytest-dev#1112).
* Add doc generation and checking to Travis and AppVeyor, to avoid re-introducing errors.

Fixes pytest-dev#432, Fixes pytest-dev#1112, Fixes pytest-dev#1708, Fixes pytest-dev#1829
nicoddemus added a commit that referenced this issue Aug 23, 2016
* Changed "index" to be more similar to the README (#1708).
* Fixes numerous issues like missing documents, syntax errors, etc (#1829, #432).
* Mention all docs in "contents.rst" so it's easier for users to locate (#1112).
* Add doc generation and checking to Travis and AppVeyor, to avoid re-introducing errors.

Fixes #432, Fixes #1112, Fixes #1708, Fixes #1829
nicoddemus added a commit that referenced this issue Aug 26, 2016
* Changed "index" to be more similar to the README (#1708).
* Fixes numerous issues like missing documents, syntax errors, etc (#1829, #432).
* Mention all docs in "contents.rst" so it's easier for users to locate (#1112).
* Add doc generation and checking to Travis and AppVeyor, to avoid re-introducing errors.

Fixes #432, Fixes #1112, Fixes #1708, Fixes #1829
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: docs documentation improvement, missing or needing clarification
Projects
None yet
Development

No branches or pull requests

4 participants