Repository navigation
Move docs/fits to docs/io/fits - #245
Conversation
|
Okay. Should be fine. |
|
@iguananaut - at the same time, could you reorder the front page of the io.fits docs according to the layout in #218, like @mdboom did in #219? |
|
@iguananaut - will you be able to move |
|
Sure, I can do that. The only holdup right now is that I have a bunch of doc updates for pyfits that I need to merge into Astropy before I start moving things around. I figure it'll be easier that way. |
… I will want to backport much of these changes to PyFITS--otherwise documentaiton merges will be a nightmare. I like where this new organization is going though.
…and re-added the existing API docs to the main index. automodapi did a pretty decent job, but I still think I prefer the existing organization of the API docs.
|
Pretty much reorganized all the astropy.io.fits docs. This is a fairly significant reorg that I will probably want to backport to pyfits sooner rather than later. I tried automodapi and the output was pretty acceptable. That said, I still prefer the existing organization of pyfits' API docs so I kept that as is. Otherwise, I made docs/io/fits/index look more like the indexes of the other sub-packages' docs. This involved moving the old "tutorial" section into the "Getting Started" section, which worked out fine. Barring any further comments I'll go ahead an merge this soon. |
|
This looks fine to me for 0.1. For 0.2 (or possibly later, because this isn't a big deal) @iguananaut , can you see about deciding what needs to be in |
|
Looks good - feel free to merge! |
Move `docs/fits` to `docs/io/fits`
Move `docs/fits` to `docs/io/fits`
Since some new doc infrastructure (See #217) is now assumes that the code structure is parallel to the docs structure,
docs/fitsshould be moved todocs/io/fits.