Skip to content

Mark documentation stable again #73

@Pennycook

Description

@Pennycook

Feature/behavior summary

#72 marks the documentation unstable. Before releasing 1.0.0, we should make sure to remove this notice.

Request attributes

  • Would this be a refactor of existing code?
  • Does this proposal require new package dependencies?
  • Would this change break backwards compatibility?

Related issues

No response

Solution description

Revert #72.

Additional notes

It would be even better if we could find a way to store two copies of the documentation on the website, so that we could show the documentation for the latest release and the unstable documentation together. But I have no idea how to achieve that with Sphinx.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions