-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
add FAQ to standard documentation #8464
Comments
Changed keywords from none to FAQ |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:5
I don't know if this is ready for review yet, but here are a few comments:
|
comment:6
Replying to @jhpalmieri:
This is a work in progress.
Thank you.
The docbuild target "faq" is automatically added. The index.html page of the website has been changed to include the FAQ.
The FAQ on the Sage wiki is a mess. The current ticket is an attempt to pull together information from the FAQ on the wiki and other sources. The resulting information is then to be organized following the model of the Django FAQ. |
reviewer patch |
This comment has been minimized.
This comment has been minimized.
comment:7
Attachment: trac_8464-ref.patch.gz |
Author: Minh Van Nguyen |
Sage 4.3.5, One more question added to the FAQ |
comment:8
Attachment: trac_8464-faq-general.2.patch.gz CalTech is using Sage. See http://www.its.caltech.edu/~awalker/sage.html. Update the FAQ with that institutional user. |
comment:9
The documents build without error and they look good, in both html and pdf. I have a few comments about the content:
I don't know if it's worth mentioning these alternatives. In the same part, I would suggest changing the path to the documentation: replace "sage-main" by "sage". Also in the same part, in the spirit of #21 and standard GNU-style command line options, how about changing
|
comment:10
The following institutions are using Sage:
|
comment:11
I tested all 5 patches including the general2 patch and everything builds fine. On the documentation homepage there is a big white space in between constructions and reference manual. It would be nice to bring reference manual up in line with the new FAQ section. |
comment:12
Just letting people know that when you patch with 8465 it adds a new section to where the white space was, so don't worry about that. I think we're good now. |
This comment has been minimized.
This comment has been minimized.
comment:13
Attachment: trac_8464-faq.patch.gz Needs a final review before we can merge the new FAQ into the standard documentation of Sage. |
comment:14
For a list of FAQs, they are very difficult to find. Maybe I'm missing an obvious FAQ link but, how is a first time user supposed to find them? |
Reviewer: pang |
comment:15
If I hit the "index" button on the top right, a page appears with a link to "Full index on one page (can be huge)", which then yields a blank page. It also happens in the thematic tutorials, as they don't add words from the faq to the index. That's perfectly normal, so I give a positive review. |
Changed reviewer from pang to Pablo Angulo |
Changed reviewer from Pablo Angulo to Jose Guzman, Pablo Angulo |
Changed reviewer from Jose Guzman, Pablo Angulo to John Palmieri, Mark Jordan, Jose Guzman, Pablo Angulo |
comment:19
Attachment: trac_8464-doctest.patch.gz After applying all three patches to Sage 4.4.2.rc0, running doctests resulted in the following failure:
I have attached a patch to resolve this. Anyone care for another trivial review? |
This comment has been minimized.
This comment has been minimized.
Merged: sage-4.4.4.alpha1 |
Add the FAQ on the Sage wiki to the Sage standard documentation. The original proposal can be found on sage-devel and sage-combinat-devel.
Notes: The current ticket needs to be coordinated with #8470.
Prerequisites: #8480
Apply in this order:
CC: @jhpalmieri
Component: documentation
Keywords: FAQ
Author: Minh Van Nguyen
Reviewer: John Palmieri, Mark Jordan, Jose Guzman, Pablo Angulo
Merged: sage-4.4.4.alpha1
Issue created by migration from https://trac.sagemath.org/ticket/8464
The text was updated successfully, but these errors were encountered: