Sources for the Haxe Code Cookbook site, a community driven resource website for learning Haxe in practise.
The repository contains a static website generator, which converts markdown articles into a website. The project is being developed here on GitHub, feel free to contribute Haxe related code snippets and tutorials.
- The actual articles are in assets/content/cookbook, organized per folder.
- The html template files are in assets/content/.
- The static files (css, js, images) files are in assets/includes/.
- The Haxe source files of the generator are in src/.
- The website-generated content will output in
output/(excluded from git).
To contribute a change, you have to make a pull request. This can be done using the GitHub website or by fork/cloning the project.
This is the easiest way of doing small changes:
- Navigate to an article on https://code.haxe.org and press the edit button on any page:
- You are redirected to GitHub. Once you have an account and are logged in, you can make the change in the online editor.
- Set the description / what you changed and press the Request change button:
- A pull request will be created. GitHub makes a fork for you automatically.
This would also allow to test/see the changes before submitting which is also useful when you want to add new pages.
- Make a fork (on GitHub) of the project.
- Checkout your repo on your machine, create a new branch for the pull request.
- Make the changes in that new branch.
- Push the commits (they go to your fork).
- On GitHub, you make a pull request from your fork's branch to the original repo.
Please add/edit the articles (markdown files) in the assets folder and do a pull request. The scope of the cookbook includes the core language, the standard library, and also any libraries maintained by the Haxe Foundation.
It would be nice if you keep the formatting of the code in the same style as used already:
- Braces on same line.
- Two-space indentation.
- No type-hints for local variables and function return unless it's instructive.
- Type-hints for fields.
- Type-hints for function arguments unless it's very obvious.
- Judicious use of extra line-breaks to avoid ugly automatic breaks (check the output).
- The first heading is used in the navigation. Keep this title short.
- The first paragraph is used as description. Describe what the content of the article is about.
- Use
> Author: [Name](https://github.com/username)to mark yourself as author of the article. The other contributors are inferred from git commits. - Tag the article using
[tags]: / "tag1,tag2"(no spaces). Try to use an existing tag. - Mention the author / sources at the bottom of the page.
- If you want to include a try.haxe.org code snippet use
[tryhaxe](https://try.haxe.org/embed/76f24). - If you want to include a YouTube video use
[youtube](https://www.youtube.com/watch?v=dQw4w9WgXcQ). - If possible, link to related pages in the Haxe Manual / API documentation.
- If you want to use images or other includes, create a folder called assets in the same directory as the article and link to that.
This would be a typical template to use. Use ```haxe for syntax highlighting:
[tags]: / "class,array,json,building-fields"
# Title of the page
Description and explanation of the code.
## Implementation
```haxe
class Main {
// Code here
}
```
## Usage
Description of how to use/test the code.
```haxe
class Test {
// Code here
}
```
> More on this topic:
>
> * [Class field in Haxe Manual](https://haxe.org/manual/class-field.html)
>
> Author: [Name](https://github.com/username)
To run the project you can use Neko:
Call neko CodeCookBook.n to re-generate the output files.
You need Haxe 3.4.2+ installed.
The static site generator source depends on hxtemplo and haxe-markdown.
Install the libraries using haxelib, run the following command in the root of the project:
haxelib install all
The CSS files are compressed using less. Install from npm:
npm install -g less
npm install -g less-plugin-clean-css
