1
1
# Contributing
2
2
3
- Your patches to ` perl6 /doc` are very welcome, and if you want to
3
+ Your patches to ` Raku /doc` are very welcome, and if you want to
4
4
help,
5
5
[ please read this guide] ( https://dev.to/jj/squashing-perl-6-documentation-bugs-one-at-a-time-4ojn ) as
6
6
well as the detailed instructions below.
@@ -28,6 +28,7 @@ in the [#raku IRC channel](https://raku.org/community/irc).
28
28
- [ Broken links] ( #broken-links )
29
29
- [ Heading numbering] ( #heading-numbering )
30
30
- [ Reporting bugs] ( #reporting-bugs )
31
+ - [ Contributing pull requests] ( #contributing-pull-requests )
31
32
- [ Building the documentation] ( #building-the-documentation )
32
33
- [ Dependency installation] ( #dependency-installation )
33
34
- [ Rakudo] ( #rakudo )
@@ -68,7 +69,7 @@ available when writing code examples in the documentation.
68
69
## Adding a new Language document
69
70
70
71
We suggest you discuss proposing a new Language document on the #raku
71
- channel and/or the [ issues for this repository] ( https://github.com/perl6 /doc/issues )
72
+ channel and/or the [ issues for this repository] ( https://github.com/Raku /doc/issues )
72
73
before you proceed further. After you get consensus on a title, subtitle,
73
74
section, and filename, you can add the document by following these steps:
74
75
@@ -82,8 +83,8 @@ section, and filename, you can add the document by following these steps:
82
83
83
84
## Documenting types
84
85
85
- The Pod 6 documentation of types is located in the ` doc/Type ` directory and
86
- subdirectories of this repository. For example the Pod 6 file of ` X::Bind::Slice `
86
+ The Pod6 documentation of types is located in the ` doc/Type ` directory and
87
+ subdirectories of this repository. For example the Pod6 file of ` X::Bind::Slice `
87
88
lives in ` doc/Type/X/Bind/Slice.pod6 ` .
88
89
89
90
To start contributing, fork and checkout the repository, find the document
@@ -162,9 +163,9 @@ See [Writing and Testing Examples](writing-docs/EXAMPLES.md)
162
163
## Testing method completeness
163
164
164
165
To get a list of methods that are found via introspection but not found in any
165
- Pod 6 file under ` doc/Type/ ` , use ` util/list-missing-methods.p6 ` . It takes a
166
+ Pod6 file under ` doc/Type/ ` , use ` util/list-missing-methods.p6 ` . It takes a
166
167
directory or filepath as argument and limits the listing to the given file or
167
- any Pod 6- files found. All methods listed in ` util/ignored-methods.txt ` are
168
+ any Pod6 files found. All methods listed in ` util/ignored-methods.txt ` are
168
169
ignored.
169
170
170
171
## Debug mode
@@ -192,36 +193,39 @@ to display heading numbers.
192
193
193
194
## Reporting bugs
194
195
195
- Report issues at https://github.com/perl6 /doc/issues . You can
196
+ Report issues at https://github.com/Raku /doc/issues . You can
196
197
use
197
- [ labels when tagging tickets] ( https://github.com/perl6 /doc/labels ) ,
198
+ [ labels when tagging tickets] ( https://github.com/Raku /doc/labels ) ,
198
199
among which these are probably the most common:
199
200
200
- * [ ` docs ` ] ( https://github.com/perl6 /doc/labels/docs ) - missing or
201
+ * [ ` docs ` ] ( https://github.com/Raku /doc/labels/docs ) - missing or
201
202
incorrect documentation;
202
- use [ ` NOTSPECCED ` ] ( https://github.com/perl6 /doc/labels/NOTSPECCED )
203
+ use [ ` NOTSPECCED ` ] ( https://github.com/Raku /doc/labels/NOTSPECCED )
203
204
instead, if this is for a feature present in a compiler, but not in
204
205
the Raku test suite.
205
- * [ ` search ` ] ( https://github.com/perl6 /doc/labels/search ) - the search
206
+ * [ ` search ` ] ( https://github.com/Raku /doc/labels/search ) - the search
206
207
component, either for items that are on the site but not searchable,
207
208
or for the search functionality itself.
208
209
210
+ ## Contributing pull requests
211
+
209
212
If you would like to contribute documentation or other bug fixes, please use
210
- [ GitHub's pull requests] ( https://github.com/perl6/doc/pulls ) .
213
+ [ GitHub's pull requests (PRs)] ( https://github.com/Raku/doc/pulls ) . For a complete
214
+ recipe for a new PR contributor, check [ this PR guide] ( https://github.com/tbrowder/tidbits/blob/master/Contributing-PRs.md ) .
211
215
212
216
## Building the documentation
213
217
214
218
Assuming that you have already forked and cloned the
215
- [ perl6 /doc] ( https://github.com/perl6 /doc ) repository, one of the first things
219
+ [ Raku /doc] ( https://github.com/Raku /doc ) repository, one of the first things
216
220
you probably want to do is to build the documentation on your local
217
221
computer. To do this you will need:
218
222
219
223
- Raku (e.g., the Rakudo Raku implementation)
220
224
- zef (the installer for third party Raku modules)
221
- - ` Pod::To::HTML ` (Raku module for converting Pod 6 objects to HTML)
225
+ - ` Pod::To::HTML ` (Raku module for converting Pod6 objects to HTML)
222
226
- [ graphviz] ( http://www.graphviz.org/ ) (` sudo apt-get install graphviz ` on Debian/Ubuntu)
223
227
- [ Mojolicious] ( https://metacpan.org/pod/Mojolicious )
224
- (optional; a Perl 5 web framework; it allows you to run a web
228
+ (optional; a Perl web framework; it allows you to run a web
225
229
app locally to display the docs)
226
230
- [ SASS] ( http://sass-lang.com/ ) Compiler
227
231
- [ highlights] ( https://github.com/perl6/atom-language-perl6 ) (optional; requires
@@ -250,7 +254,7 @@ use any other module installer for the modules needed (see below).
250
254
#### Building the documentation
251
255
252
256
The program that builds the HTML version of the documentation
253
- (` htmlify.p6 ` ) uses ` Pod::To::HTML ` to convert Pod 6 structures into HTML.
257
+ (` htmlify.p6 ` ) uses ` Pod::To::HTML ` to convert Pod6 structures into HTML.
254
258
You'll also need ` Pod::To::BigPage ` and ` Perl6::TypeGraph ` . Install these modules like so:
255
259
256
260
$ zef install Pod::To::HTML Pod::To::BigPage Perl6::TypeGraph
@@ -263,15 +267,15 @@ you're good to go.
263
267
264
268
#### Mojolicious / Web Server
265
269
266
- This is a Perl 5 web framework which is used to run the included
270
+ This is a Perl web framework which is used to run the included
267
271
web application that displays the HTML documentation in a web browser. It's
268
272
no required for development, as the site is static and you can serve it using
269
273
any other webserver.
270
274
271
275
The app * does* automatically convert the SASS file to CSS, so it's handy to
272
276
use for that as well.
273
277
274
- Mojolicious is written in Perl 5 , so assuming that you use
278
+ Mojolicious is written in Perl, so assuming that you use
275
279
[ ` cpanm ` ] ( https://metacpan.org/pod/App::cpanminus ) ,
276
280
install this now:
277
281
@@ -284,7 +288,7 @@ the `sass` command
284
288
285
289
$ sudo apt-get install ruby-sass
286
290
287
- or the [ CSS::Sass Perl 5 module] ( https://modules.raku.org/repo/CSS::Sass )
291
+ or the [ CSS::Sass Perl module] ( https://modules.raku.org/repo/CSS::Sass )
288
292
289
293
$ cpanm -vn CSS::Sass Mojolicious::Plugin::AssetPack
290
294
@@ -318,12 +322,12 @@ You can skip all the above and just build and view documentation with these
318
322
simple commands (if you have docker already installed):
319
323
320
324
$ docker build -t perl6-doc .
321
- $ docker run -p 3000:3000 -it -v `pwd`:/perl6 /doc perl6-doc
325
+ $ docker run -p 3000:3000 -it -v `pwd`:/Raku /doc perl6-doc
322
326
323
327
This will build the documentation for you by default and it will take some time,
324
328
but for subsequent use you may want to skip build part if nothing has been changed:
325
329
326
- $ docker run -p 3000:3000 -it -v `pwd`:/perl6 /doc perl6-doc ./app-start
330
+ $ docker run -p 3000:3000 -it -v `pwd`:/Raku /doc perl6-doc ./app-start
327
331
328
332
Now point your web browser to http://localhost:3000 to view the documentation.
329
333
0 commit comments