#053
gdtest_extras_guide
OK
INIT
Full extras (license, citation, etc.) plus user guide
Full supporting pages (H1-H4) combined with a user guide (F1). Sidebar should show License, Citation, Contributing, Code of Conduct links AND a User Guide section with two pages. Reference page shows two functions (start, stop).
Build Mode
○ No great-docs.yml
This package has no pre-supplied config.
It tests the full great-docs init → great-docs build
pipeline from scratch, relying entirely on auto-detection of the package
layout, docstring style, and exports.
Dimensions
A1 B1 C1 D1 E6 F1 G1 H1 H2 H3 H4
A1Flat layoutlayout
B1Explicit __all__exports
C1Functions onlyobjects
D1NumPydocstrings
E6No directivesdirectives
F1Auto-discoveruser_guide
G1README.mdlanding
H1LICENSEextras
H2CITATION.cffextras
H3CONTRIBUTING.mdextras
H4CODE_OF_CONDUCT.mdextras
Source Files
gdtest_extras_guide/
__init__.py
"""Package with full extras and user guide."""
__version__ = "0.1.0"
__all__ = ["start", "stop"]
def start() -> None:
"""
Start the service.
Returns
-------
None
"""
pass
def stop() -> None:
"""
Stop the service.
Returns
-------
None
"""
passuser_guide/
01-intro.qmd
--- title: Introduction --- Welcome to the extras-guide package.
02-config.qmd
--- title: Configuration --- Configuration details for the extras-guide package.
CITATION.cff
cff-version: 1.2.0
title: gdtest-extras-guide
message: "Please cite this software."
authors:
- family-names: Author
given-names: TestCODE_OF_CONDUCT.md
# Code of Conduct Be kind and respectful.
CONTRIBUTING.md
# Contributing Thank you for contributing! ## How to contribute 1. Fork the repository 2. Create a branch 3. Submit a pull request
LICENSE
MIT License Copyright (c) 2024 Test Author
README.md
# gdtest-extras-guide Tests all supporting pages combined with a user guide.
great-docs.yml generated
# Great Docs Configuration
# See https://posit-dev.github.io/great-docs/user-guide/configuration.html
# Module Name (optional)
# ----------------------
# Set this if your importable module name differs from the project name.
# Example: project 'py-yaml12' with module name 'yaml12'
# module: yaml12
# Docstring Parser
# ----------------
# The docstring format used in your package (numpy, google, or sphinx)
parser: numpy
# Dynamic Introspection
# ---------------------
# Use runtime introspection for more accurate documentation (default: true)
# Set to false if your package has cyclic alias issues (e.g., PyO3/Rust bindings)
dynamic: true
# API Discovery Settings
# ----------------------
# Exclude items from auto-documentation
# exclude:
# - InternalClass
# - helper_function
# Logo & Favicon
# ---------------
# Point to a single logo file (replaces the text title in the navbar):
# logo: assets/logo.svg
#
# For light/dark variants:
# logo:
# light: assets/logo-light.svg
# dark: assets/logo-dark.svg
#
# To show the text title alongside the logo, add: show_title: true
# Funding / Copyright Holder
# --------------------------
# Credit the organization that funds or holds copyright for this package.
# Displays in sidebar and footer. Homepage and ROR provide links.
# funding:
# name: "Posit Software, PBC"
# roles:
# - Copyright holder
# - funder
# homepage: https://posit.co
# ror: https://ror.org/03wc8by49
# API Reference Structure
# -----------------------
# Customize the sections below to organize your API documentation.
# - Reorder items within a section to change their display order
# - Move items between sections or create new sections
# - Use 'members: false' to exclude methods from documentation
# - Add 'desc:' to sections for descriptions
reference:
- title: Functions
desc: Utility functions
contents:
- start
- stop
# Site URL
# --------
# Canonical address of the deployed documentation site.
# Required for subdirectory deployments, skills page install commands,
# .well-known/ discovery, and sitemaps.
# site_url: "https://your-org.github.io/your-package/"
# Site Settings
# -------------
# site:
# theme: flatly # Quarto theme (default: flatly)
# toc: true # Show table of contents (default: true)
# toc-depth: 2 # TOC heading depth (default: 2)
# toc-title: On this page # TOC title (default: "On this page")
# Jupyter Kernel
# --------------
# Jupyter kernel to use for executing code cells in .qmd files.
# This is set at the project level so it applies to all pages, including
# auto-generated API reference pages. Can be overridden in individual .qmd
# file frontmatter if needed for special cases.
jupyter: python3
# CLI Documentation
# -----------------
# cli:
# enabled: true # Enable CLI documentation
# module: my_package.cli # Module containing Click commands
# name: cli # Name of the Click command object