|
| 1 | +# Hyperactive Documentation |
| 2 | + |
| 3 | +This directory contains the Sphinx-based documentation for Hyperactive. |
| 4 | + |
| 5 | +## Building the Documentation |
| 6 | + |
| 7 | +### Prerequisites |
| 8 | + |
| 9 | +Install the required dependencies: |
| 10 | + |
| 11 | +```bash |
| 12 | +pip install -r requirements.txt |
| 13 | +``` |
| 14 | + |
| 15 | +You'll also need to have Hyperactive installed: |
| 16 | + |
| 17 | +```bash |
| 18 | +pip install -e .. # Install Hyperactive in development mode from parent directory |
| 19 | +``` |
| 20 | + |
| 21 | +### Building HTML Documentation |
| 22 | + |
| 23 | +From the `source` directory: |
| 24 | + |
| 25 | +```bash |
| 26 | +cd source |
| 27 | +make clean # Clean previous builds |
| 28 | +make html # Build HTML documentation |
| 29 | +``` |
| 30 | + |
| 31 | +The built documentation will be in `build/html/`. Open `build/html/index.html` in your browser to view. |
| 32 | + |
| 33 | +### Live Preview with Auto-Rebuild |
| 34 | + |
| 35 | +For development, you can use auto-rebuild mode: |
| 36 | + |
| 37 | +```bash |
| 38 | +cd source |
| 39 | +make autobuild |
| 40 | +``` |
| 41 | + |
| 42 | +This will start a local server (typically at http://127.0.0.1:8000) that automatically rebuilds when you make changes to the documentation source files. |
| 43 | + |
| 44 | +## Documentation Structure |
| 45 | + |
| 46 | +- `source/` - Documentation source files |
| 47 | + - `conf.py` - Sphinx configuration |
| 48 | + - `index.rst` - Main landing page |
| 49 | + - `api_reference/` - API reference documentation (auto-generated) |
| 50 | + - `user_guide/` - User guide pages (currently stubs) |
| 51 | + - `examples/` - Example notebooks and galleries (currently stubs) |
| 52 | + - `get_involved/` - Contributing guidelines (currently stubs) |
| 53 | + - `about/` - About pages (currently stubs) |
| 54 | + - `_templates/` - Custom Sphinx templates |
| 55 | + - `_static/` - Static files (CSS, images, etc.) |
| 56 | +- `build/` - Built documentation (generated, not tracked in git) |
| 57 | + |
| 58 | +## Current Status |
| 59 | + |
| 60 | +The documentation is currently set up with: |
| 61 | + |
| 62 | +- ✅ Full API reference auto-generated from docstrings |
| 63 | +- ✅ Sphinx configuration following SK-Time's approach |
| 64 | +- ✅ pydata_sphinx_theme for consistent look with scientific Python ecosystem |
| 65 | +- ✅ Structural placeholders for future static content |
| 66 | + |
| 67 | +Static pages (User Guide, Examples, etc.) are currently placeholder stubs marked "under construction" that can be filled in later. |
| 68 | + |
| 69 | +## Adding New Content |
| 70 | + |
| 71 | +### API Reference |
| 72 | + |
| 73 | +The API reference is automatically generated from docstrings. To update: |
| 74 | + |
| 75 | +1. Ensure your class/function has proper NumPy-style docstrings |
| 76 | +2. Add the class/function to the appropriate `api_reference/*.rst` file using the `autosummary` directive |
| 77 | +3. Rebuild the documentation |
| 78 | + |
| 79 | +### Static Pages |
| 80 | + |
| 81 | +To add content to the placeholder pages: |
| 82 | + |
| 83 | +1. Edit the corresponding `.rst` or `.md` file in the appropriate directory |
| 84 | +2. Remove the "under construction" note |
| 85 | +3. Add your content using reStructuredText or Markdown syntax |
| 86 | +4. Rebuild to see your changes |
| 87 | + |
| 88 | +## Notes |
| 89 | + |
| 90 | +- All API documentation is 100% auto-generated from source code docstrings |
| 91 | +- The structure allows for easy addition of static content in the future |
| 92 | +- Build warnings about missing references are normal during early development |
0 commit comments