├── .cutedoc.yml
├── .gitignore
├── LICENSE.txt
├── README.md
├── cmd
└── cutedoc
│ └── main.go
├── doc.go
├── docs
├── docs
│ ├── index.html
│ └── static
│ │ ├── css
│ │ └── main.css
│ │ ├── img
│ │ ├── icon.png
│ │ └── logo.png
│ │ └── js
│ │ └── main.js
├── index.html
├── sources
│ ├── about.md
│ ├── building.md
│ ├── installation.md
│ └── manifest.md
└── static
│ ├── css
│ └── main.css
│ └── img
│ ├── background.svg
│ ├── icon.png
│ └── logo.png
├── tasks.go
└── template
├── bundle.go
└── minimal
├── index.html.tmpl
├── main.css.tmpl
└── main.js.tmpl
/.cutedoc.yml:
--------------------------------------------------------------------------------
1 | build:
2 | dir: docs/docs
3 | meta:
4 | title: Cutedoc
5 | author: NickTheDev
6 | description: Cutedoc's documentation.
7 | branding:
8 | icon: docs/static/img/icon.png
9 | logo: docs/static/img/logo.png
10 | articles:
11 | Introduction:
12 | Intro: docs/sources/about.md
13 | Installing: docs/sources/installation.md
14 | Projects:
15 | Manifests: docs/sources/manifest.md
16 | Building: docs/sources/building.md
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # Project files.
2 | .idea/*
--------------------------------------------------------------------------------
/LICENSE.txt:
--------------------------------------------------------------------------------
1 | Apache License
2 | Version 2.0, January 2004
3 | http://www.apache.org/licenses/
4 |
5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6 |
7 | 1. Definitions.
8 |
9 | "License" shall mean the terms and conditions for use, reproduction,
10 | and distribution as defined by Sections 1 through 9 of this document.
11 |
12 | "Licensor" shall mean the copyright owner or entity authorized by
13 | the copyright owner that is granting the License.
14 |
15 | "Legal Entity" shall mean the union of the acting entity and all
16 | other entities that control, are controlled by, or are under common
17 | control with that entity. For the purposes of this definition,
18 | "control" means (i) the power, direct or indirect, to cause the
19 | direction or management of such entity, whether by contract or
20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the
21 | outstanding shares, or (iii) beneficial ownership of such entity.
22 |
23 | "You" (or "Your") shall mean an individual or Legal Entity
24 | exercising permissions granted by this License.
25 |
26 | "Source" form shall mean the preferred form for making modifications,
27 | including but not limited to software source code, documentation
28 | source, and configuration files.
29 |
30 | "Object" form shall mean any form resulting from mechanical
31 | transformation or translation of a Source form, including but
32 | not limited to compiled object code, generated documentation,
33 | and conversions to other media types.
34 |
35 | "Work" shall mean the work of authorship, whether in Source or
36 | Object form, made available under the License, as indicated by a
37 | copyright notice that is included in or attached to the work
38 | (an example is provided in the Appendix below).
39 |
40 | "Derivative Works" shall mean any work, whether in Source or Object
41 | form, that is based on (or derived from) the Work and for which the
42 | editorial revisions, annotations, elaborations, or other modifications
43 | represent, as a whole, an original work of authorship. For the purposes
44 | of this License, Derivative Works shall not include works that remain
45 | separable from, or merely link (or bind by name) to the interfaces of,
46 | the Work and Derivative Works thereof.
47 |
48 | "Contribution" shall mean any work of authorship, including
49 | the original version of the Work and any modifications or additions
50 | to that Work or Derivative Works thereof, that is intentionally
51 | submitted to Licensor for inclusion in the Work by the copyright owner
52 | or by an individual or Legal Entity authorized to submit on behalf of
53 | the copyright owner. For the purposes of this definition, "submitted"
54 | means any form of electronic, verbal, or written communication sent
55 | to the Licensor or its representatives, including but not limited to
56 | communication on electronic mailing lists, source code control systems,
57 | and issue tracking systems that are managed by, or on behalf of, the
58 | Licensor for the purpose of discussing and improving the Work, but
59 | excluding communication that is conspicuously marked or otherwise
60 | designated in writing by the copyright owner as "Not a Contribution."
61 |
62 | "Contributor" shall mean Licensor and any individual or Legal Entity
63 | on behalf of whom a Contribution has been received by Licensor and
64 | subsequently incorporated within the Work.
65 |
66 | 2. Grant of Copyright License. Subject to the terms and conditions of
67 | this License, each Contributor hereby grants to You a perpetual,
68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69 | copyright license to reproduce, prepare Derivative Works of,
70 | publicly display, publicly perform, sublicense, and distribute the
71 | Work and such Derivative Works in Source or Object form.
72 |
73 | 3. Grant of Patent License. Subject to the terms and conditions of
74 | this License, each Contributor hereby grants to You a perpetual,
75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76 | (except as stated in this section) patent license to make, have made,
77 | use, offer to sell, sell, import, and otherwise transfer the Work,
78 | where such license applies only to those patent claims licensable
79 | by such Contributor that are necessarily infringed by their
80 | Contribution(s) alone or by combination of their Contribution(s)
81 | with the Work to which such Contribution(s) was submitted. If You
82 | institute patent litigation against any entity (including a
83 | cross-claim or counterclaim in a lawsuit) alleging that the Work
84 | or a Contribution incorporated within the Work constitutes direct
85 | or contributory patent infringement, then any patent licenses
86 | granted to You under this License for that Work shall terminate
87 | as of the date such litigation is filed.
88 |
89 | 4. Redistribution. You may reproduce and distribute copies of the
90 | Work or Derivative Works thereof in any medium, with or without
91 | modifications, and in Source or Object form, provided that You
92 | meet the following conditions:
93 |
94 | (a) You must give any other recipients of the Work or
95 | Derivative Works a copy of this License; and
96 |
97 | (b) You must cause any modified files to carry prominent notices
98 | stating that You changed the files; and
99 |
100 | (c) You must retain, in the Source form of any Derivative Works
101 | that You distribute, all copyright, patent, trademark, and
102 | attribution notices from the Source form of the Work,
103 | excluding those notices that do not pertain to any part of
104 | the Derivative Works; and
105 |
106 | (d) If the Work includes a "NOTICE" text file as part of its
107 | distribution, then any Derivative Works that You distribute must
108 | include a readable copy of the attribution notices contained
109 | within such NOTICE file, excluding those notices that do not
110 | pertain to any part of the Derivative Works, in at least one
111 | of the following places: within a NOTICE text file distributed
112 | as part of the Derivative Works; within the Source form or
113 | documentation, if provided along with the Derivative Works; or,
114 | within a display generated by the Derivative Works, if and
115 | wherever such third-party notices normally appear. The contents
116 | of the NOTICE file are for informational purposes only and
117 | do not modify the License. You may add Your own attribution
118 | notices within Derivative Works that You distribute, alongside
119 | or as an addendum to the NOTICE text from the Work, provided
120 | that such additional attribution notices cannot be construed
121 | as modifying the License.
122 |
123 | You may add Your own copyright statement to Your modifications and
124 | may provide additional or different license terms and conditions
125 | for use, reproduction, or distribution of Your modifications, or
126 | for any such Derivative Works as a whole, provided Your use,
127 | reproduction, and distribution of the Work otherwise complies with
128 | the conditions stated in this License.
129 |
130 | 5. Submission of Contributions. Unless You explicitly state otherwise,
131 | any Contribution intentionally submitted for inclusion in the Work
132 | by You to the Licensor shall be under the terms and conditions of
133 | this License, without any additional terms or conditions.
134 | Notwithstanding the above, nothing herein shall supersede or modify
135 | the terms of any separate license agreement you may have executed
136 | with Licensor regarding such Contributions.
137 |
138 | 6. Trademarks. This License does not grant permission to use the trade
139 | names, trademarks, service marks, or product names of the Licensor,
140 | except as required for reasonable and customary use in describing the
141 | origin of the Work and reproducing the content of the NOTICE file.
142 |
143 | 7. Disclaimer of Warranty. Unless required by applicable law or
144 | agreed to in writing, Licensor provides the Work (and each
145 | Contributor provides its Contributions) on an "AS IS" BASIS,
146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147 | implied, including, without limitation, any warranties or conditions
148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149 | PARTICULAR PURPOSE. You are solely responsible for determining the
150 | appropriateness of using or redistributing the Work and assume any
151 | risks associated with Your exercise of permissions under this License.
152 |
153 | 8. Limitation of Liability. In no event and under no legal theory,
154 | whether in tort (including negligence), contract, or otherwise,
155 | unless required by applicable law (such as deliberate and grossly
156 | negligent acts) or agreed to in writing, shall any Contributor be
157 | liable to You for damages, including any direct, indirect, special,
158 | incidental, or consequential damages of any character arising as a
159 | result of this License or out of the use or inability to use the
160 | Work (including but not limited to damages for loss of goodwill,
161 | work stoppage, computer failure or malfunction, or any and all
162 | other commercial damages or losses), even if such Contributor
163 | has been advised of the possibility of such damages.
164 |
165 | 9. Accepting Warranty or Additional Liability. While redistributing
166 | the Work or Derivative Works thereof, You may choose to offer,
167 | and charge a fee for, acceptance of support, warranty, indemnity,
168 | or other liability obligations and/or rights consistent with this
169 | License. However, in accepting such obligations, You may act only
170 | on Your own behalf and on Your sole responsibility, not on behalf
171 | of any other Contributor, and only if You agree to indemnify,
172 | defend, and hold each Contributor harmless for any liability
173 | incurred by, or claims asserted against, such Contributor by reason
174 | of your accepting any such warranty or additional liability.
175 |
176 | END OF TERMS AND CONDITIONS
177 |
178 | APPENDIX: How to apply the Apache License to your work.
179 |
180 | To apply the Apache License to your work, attach the following
181 | boilerplate notice, with the fields enclosed by brackets "[]"
182 | replaced with your own identifying information. (Don't include
183 | the brackets!) The text should be enclosed in the appropriate
184 | comment syntax for the file format. We also recommend that a
185 | file or class name and description of purpose be included on the
186 | same "printed page" as the copyright notice for easier
187 | identification within third-party archives.
188 |
189 | Copyright [yyyy] [name of copyright owner]
190 |
191 | Licensed under the Apache License, Version 2.0 (the "License");
192 | you may not use this file except in compliance with the License.
193 | You may obtain a copy of the License at
194 |
195 | http://www.apache.org/licenses/LICENSE-2.0
196 |
197 | Unless required by applicable law or agreed to in writing, software
198 | distributed under the License is distributed on an "AS IS" BASIS,
199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200 | See the License for the specific language governing permissions and
201 | limitations under the License.
202 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | 
2 |
3 | # cutedoc
4 | Cutedoc is a simple command line tool that allows you to generate beautiful static documentation using simple markdown files.
5 | You can learn more about the project at https://nickthedev.github.io/cutedoc.
6 |
7 | # Getting Started
8 | If you already have Go installed, you can easily grab the latest version of Cutedoc by using the go get command in the console.
9 | If your GOPATH/bin env variable is set, the cutedoc command will be accessible without having to specify the executable path.
10 |
11 | ```
12 | $ go get github.com/NickTheDev/cutedoc/cmd/cutedoc
13 | ```
14 | If you do not have or wish to install Go, you can grab a pre-built binary from Github. However, with this method you will have to
15 | optionally add the executable to your env variables yourself.
16 |
17 | # Demo
18 | Cutedoc's documentation was created with Cutedoc, and can be found at https://nickthedev.github.io/cutedoc/docs.
19 |
20 |
--------------------------------------------------------------------------------
/cmd/cutedoc/main.go:
--------------------------------------------------------------------------------
1 | package main
2 |
3 | import (
4 | "github.com/nickthedev/cutedoc"
5 | "log"
6 | "os"
7 | )
8 |
9 | // main loads the documentation config in either the current directory or a specified one and generates documentation using it.
10 | func main() {
11 | log.SetFlags(0)
12 | log.SetOutput(os.Stdout)
13 |
14 | if doc, err := cutedoc.New(); err == nil {
15 | if err = cutedoc.Run(doc); err != nil {
16 | log.Fatalf("An error occured generating documentation: \n\t%v.", err)
17 | }
18 | } else {
19 | log.Fatalf("An error occurred loading the documentation config: \n\t%v.", err)
20 | }
21 | }
22 |
--------------------------------------------------------------------------------
/doc.go:
--------------------------------------------------------------------------------
1 | package cutedoc
2 |
3 | import (
4 | "gopkg.in/yaml.v2"
5 | "io/ioutil"
6 | )
7 |
8 | // config represents the default name of the cutedoc config file.
9 | const config = ".cutedoc.yml"
10 |
11 | // Doc represents the current model of the documentation being created.
12 | type Doc struct {
13 | Build Build
14 | Meta Meta
15 | Theme Theme
16 | Articles yaml.MapSlice
17 | }
18 |
19 | // Build represents options used during the build process.
20 | type Build struct {
21 | Dir string
22 | Minify bool
23 | }
24 |
25 | // Meta holds metadata of the documentation.
26 | type Meta struct {
27 | Title string
28 | Author string
29 | Description string
30 | Branding Branding
31 | }
32 |
33 | // Represents theme of the documentation.
34 | type Theme struct {
35 | Template string
36 | Colors Colors
37 | }
38 |
39 | // Represents color scheme of the documentation.
40 | type Colors struct {
41 | Primary string
42 | Secondary string
43 | Text string
44 | Nav string
45 | Background string
46 | }
47 |
48 | // Branding holds the paths to the branding of the documentation.
49 | type Branding struct {
50 | Logo string
51 | Icon string
52 | }
53 |
54 | // New reads the doc config in the current directory and creates a doc model based on it.
55 | func New() (*Doc, error) {
56 | bytes, err := ioutil.ReadFile(config)
57 |
58 | if err != nil {
59 | return nil, err
60 | }
61 |
62 | doc := &Doc{Build{"docs", true},
63 | Meta{"Docs", "", "Documentation page.", Branding{}},
64 | Theme{"minimal", Colors{"3e4669", "c3c6de", "3e4669", "fff", "f6f7fb"}},
65 | yaml.MapSlice{}}
66 |
67 | return doc, yaml.Unmarshal(bytes, doc)
68 | }
69 |
--------------------------------------------------------------------------------
/docs/docs/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
We've all been there, just finishing up our awesome project, whether it be a design framework
75 | or front-end library, and finding ourselves wondering how to create documentation for the project.
76 | We find ourselves envying the beautiful documentation of companies like Stripe, but instead opting
77 | out of creating custom documentation due to the amount of work it would require. Cutedoc is a simple
78 | command line tool that can be used to solve this problem.
79 |
80 |
Using technologies that you already know and love, like github flavored markdown, you can create beautiful documentation sites
81 | by simply creating markdown files and then stitching them together using a simple manifest file. Cutedoc leverages a high level
82 | of customization through the manifest file and allows you to specify the template theme and color scheme, the logo and icon of
83 | used, project metadata, and more.
84 |
85 |
86 |
87 |
88 |
89 |
90 |
91 |
Installing
92 |
93 |
If you already have Go installed, you can easily grab the latest version of
94 | Cutedoc by using the go get command in the console. If your GOPATH/bin env variable is set, the
95 | cutedoc command will be accessible without having to specify the executable path.
96 |
97 |
$ go get github.com/NickTheDev/cutedoc/cmd/cutedoc
98 |
99 |
100 |
If you do not have or wish to install Go, you can grab a pre-built binary from
101 | Github. However, with this method you will have
102 | to optionally add the executable to your env variables yourself.
103 |
104 |
105 |
106 |
107 |
108 |
Projects
109 |
110 |
111 |
Manifests
112 |
113 |
To create your project, start by creating a .cutedoc.yml file in a directory of your choice, usually
114 | the in the root of your project. This is the general structure of a manifest file:
To describe basic characteristics of the project, you can define a meta section in the manifest
131 | file. In this section you may define meta such as the title, author, and description and the
132 | project branding.
133 |
134 |
# Project metadata.
135 | meta:
136 | # Html header metadata title. Default is blank.
137 | title: Cutedoc
138 |
139 | # Html header metadata author. Default is blank.
140 | author: NickTheDev
141 |
142 | # Html header metadata description. Default is blank.
143 | description: Cool documentation.
144 |
145 | # Project branding.
146 | branding:
147 | # Html header favicon, preferably 16 x 16. Default is null.
148 | icon: path/to/icon.png
149 |
150 | # Logo of the project, preferably 200 x 100. Default is null.
151 | logo: path/to/logo.png
152 |
153 |
154 | Build
155 |
156 |
To configure the build of your project, you can define a build section in the manifest file. In this section you may
157 | specify the output directory of the build and whether to minify the production assets or not.
158 |
159 |
# Build config.
160 | build:
161 | # Output directory of the documentation. Default is 'docs'.
162 | dir: docs
163 |
164 | # Whether or not to minify the build assets (css, js). Default is true.
165 | minify: true
166 |
167 |
168 | Articles
169 |
170 |
To link markdown files in your project, you can define an articles section in the manifest file.
171 | In this section you may define article groups, and then place the links in them.
172 |
173 |
# Project articles.
174 | articles:
175 | # Article group name.
176 | Introduction:
177 | # Path to article markdown file, may use github flavored markdown.
178 | Intro: docs/sources/about.md
179 |
180 |
181 | Theme
182 |
183 |
To configure the theme of your project, you can define a theme section in the manifest file.
184 | You may specify the template name, the only one currently being the minimal theme (The
185 | documentation you are reading right now uses the minimal theme). You can also
186 | define the color scheme of the template, namely the primary, secondary, text, nav, and
187 | background colors.
188 |
189 |
# Project theme.
190 | theme:
191 | # Theme template, currently the only supported template is 'minimal'. Default is 'minimal'.
192 | template: minimal
193 |
194 | # Template color scheme.
195 | colors:
196 | # Primary color used for headers and navigation group text colors. Default is 3e4669.
197 | primary: 3e4669
198 |
199 | # Secondary color used an accent in the navigation and the body headers. Default is c3c6de.
200 | secondary: c3c6de
201 |
202 | # Body text color used in the documentation. Default is 3e4669.
203 | text: 3e4669
204 |
205 | # Navigation background color. Default is fff.
206 | nav: fff
207 |
208 | # Background color. Default is f6f7fb.
209 | background: f6f7fb
210 |
211 |
212 |
213 |
214 |
215 |
216 |
217 |
218 |
Building
219 |
220 |
To build a project, simply execute the cutedoc command in a directory containing a .cutedoc.yml manifest file.
221 |
222 |
$ cutedoc
223 |
224 |
225 |
Cutedoc will create documentation in the manifest's specified output directory the contents will look like this: