Skip to content

Commit

Permalink
docs(readme): add section with usage examples (#73)
Browse files Browse the repository at this point in the history
  • Loading branch information
princjef authored Jul 7, 2022
1 parent 1970099 commit 5c06b2c
Show file tree
Hide file tree
Showing 2 changed files with 19 additions and 0 deletions.
6 changes: 6 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -235,6 +235,12 @@ func main() {
}
```

### Examples

This project uses itself to generate the README files in github\.com/princjef/gomarkdoc and its subdirectories\. To see the commands that are run to generate documentation for this repository\, take a look at the Doc\(\) and DocVerify\(\) functions in magefile\.go and the \.gomarkdoc\.yml file in the root of this repository\. To run these commands in your own project\, simply replace \`go run \./cmd/gomarkdoc\` with \`gomarkdoc\`\.

Know of another project that is using gomarkdoc? Open an issue with a description of the project and link to the repository and it might be featured here\!

## Index

- [type Renderer](<#type-renderer>)
Expand Down
13 changes: 13 additions & 0 deletions doc.go
Original file line number Diff line number Diff line change
Expand Up @@ -258,4 +258,17 @@
// // Write the documentation out to console.
// fmt.Println(out.Package(pkg))
// }
//
// Examples
//
// This project uses itself to generate the README files in
// github.com/princjef/gomarkdoc and its subdirectories. To see the commands
// that are run to generate documentation for this repository, take a look at
// the Doc() and DocVerify() functions in magefile.go and the .gomarkdoc.yml
// file in the root of this repository. To run these commands in your own
// project, simply replace `go run ./cmd/gomarkdoc` with `gomarkdoc`.
//
// Know of another project that is using gomarkdoc? Open an issue with a
// description of the project and link to the repository and it might be
// featured here!
package gomarkdoc

0 comments on commit 5c06b2c

Please sign in to comment.