Skip to content

Organizational guidance #4

@eah13

Description

@eah13

Repo needs and overall guidance as to what goes where. I'm thinking for now a folder for each source text? e.g. /manual for the Pi manual, /think_python for that text.

But then the repo becomes just an agglomeration of resources that can't stand on their own. See also Issue #5 on scope

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions