From 696f0f3d73e3201294c94935dcf7cc84ab01b011 Mon Sep 17 00:00:00 2001 From: Exelo Date: Sat, 10 Jan 2026 14:15:13 +0100 Subject: [PATCH 1/5] docs: add contribution resources --- .../CODE_OF_CONDUCT.md | 0 .github/COMMIT_CONVENTION.md | 201 ++++++++++++++++++ .github/CONTRIBUTING.md | 15 ++ .github/FUNDING.md | 1 + .../ISSUE_TEMPLATE/01-command_bug_report.yml | 75 +++++++ .github/ISSUE_TEMPLATE/02-feature_request.yml | 44 ++++ .../ISSUE_TEMPLATE/03-documentation_issue.yml | 27 +++ .github/ISSUE_TEMPLATE/config.yml | 5 + .github/PULL_REQUEST_TEMPLATE.md | 3 + .github/issue-labeler.yml | 11 + .github/labeler.yml | 17 ++ .github/labels.yml | 67 ++++++ .github/logo.png | Bin 0 -> 20534 bytes .github/workflows/issue-triage.yml | 15 ++ .github/workflows/label-sync.yml | 26 +++ .github/workflows/pr-triage.yml | 38 ++++ LICENSE | 2 +- README.md | 55 ++++- apps/client/LICENSE | 2 +- apps/client/README.md | 56 +++++ apps/server/LICENSE | 2 +- apps/server/README.md | 56 +++++ apps/website/LICENSE | 2 +- apps/website/README.md | 56 +++++ 24 files changed, 771 insertions(+), 5 deletions(-) rename CODE_OF_CONDUCT.md => .github/CODE_OF_CONDUCT.md (100%) create mode 100644 .github/COMMIT_CONVENTION.md create mode 100644 .github/CONTRIBUTING.md create mode 100644 .github/FUNDING.md create mode 100644 .github/ISSUE_TEMPLATE/01-command_bug_report.yml create mode 100644 .github/ISSUE_TEMPLATE/02-feature_request.yml create mode 100644 .github/ISSUE_TEMPLATE/03-documentation_issue.yml create mode 100644 .github/ISSUE_TEMPLATE/config.yml create mode 100644 .github/PULL_REQUEST_TEMPLATE.md create mode 100644 .github/issue-labeler.yml create mode 100644 .github/labeler.yml create mode 100644 .github/labels.yml create mode 100644 .github/logo.png create mode 100644 .github/workflows/issue-triage.yml create mode 100644 .github/workflows/label-sync.yml create mode 100644 .github/workflows/pr-triage.yml create mode 100644 apps/client/README.md create mode 100644 apps/server/README.md create mode 100644 apps/website/README.md diff --git a/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md similarity index 100% rename from CODE_OF_CONDUCT.md rename to .github/CODE_OF_CONDUCT.md diff --git a/.github/COMMIT_CONVENTION.md b/.github/COMMIT_CONVENTION.md new file mode 100644 index 0000000..49d7d50 --- /dev/null +++ b/.github/COMMIT_CONVENTION.md @@ -0,0 +1,201 @@ +# Git Commit Message Convention + +> This is adapted from [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) + +## Summary + +The Conventional Commits specification is a lightweight convention on top of commit messages. +It provides an easy set of rules for creating an explicit commit history; +which makes it easier to write automated tools on top of. +This convention dovetails with [SemVer](http://semver.org), +by describing the features, fixes, and breaking changes made in commit messages. + +The commit message should be structured as follows: + +--- + +``` +[optional scope]: + +[optional body] + +[optional footer(s)] +``` + +--- + +
+The commit contains the following structural elements, to communicate intent to the +consumers of your library: + +1. **fix:** a commit of the _type_ `fix` patches a bug in your codebase (this correlates with [`PATCH`](http://semver.org/#summary) in Semantic Versioning). +1. **feat:** a commit of the _type_ `feat` introduces a new feature to the codebase (this correlates with [`MINOR`](http://semver.org/#summary) in Semantic Versioning). +1. **BREAKING CHANGE:** a commit that has a footer `BREAKING CHANGE:`, or appends a `!` after the type/scope, introduces a breaking API change (correlating with [`MAJOR`](http://semver.org/#summary) in Semantic Versioning). + A BREAKING CHANGE can be part of commits of any _type_. +1. _types_ other than `fix:` and `feat:` are allowed, for example [@commitlint/config-conventional](https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional) (based on the [Angular convention](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines)) recommends `build:`, `chore:`, + `ci:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`, and others. +1. _footers_ other than `BREAKING CHANGE: ` may be provided and follow a convention similar to + [git trailer format](https://git-scm.com/docs/git-interpret-trailers). + +Additional types are not mandated by the Conventional Commits specification, and have no implicit effect in Semantic Versioning (unless they include a BREAKING CHANGE). +

+A scope may be provided to a commit's type, to provide additional contextual information and is contained within parenthesis, e.g., `feat(parser): add ability to parse arrays`. + +## Examples + +### Commit message with description and breaking change footer + +``` +feat: allow provided config object to extend other configs + +BREAKING CHANGE: `extends` key in config file is now used for extending other config files +``` + +### Commit message with `!` to draw attention to breaking change + +``` +feat!: send an email to the customer when a product is shipped +``` + +### Commit message with scope and `!` to draw attention to breaking change + +``` +feat(api)!: send an email to the customer when a product is shipped +``` + +### Commit message with both `!` and BREAKING CHANGE footer + +``` +chore!: drop support for Node 6 + +BREAKING CHANGE: use JavaScript features not available in Node 6. +``` + +### Commit message with no body + +``` +docs: correct spelling of CHANGELOG +``` + +### Commit message with scope + +``` +feat(lang): add Polish language +``` + +### Commit message with multi-paragraph body and multiple footers + +``` +fix: prevent racing of requests + +Introduce a request id and a reference to latest request. Dismiss +incoming responses other than from latest request. + +Remove timeouts which were used to mitigate the racing issue but are +obsolete now. + +Reviewed-by: Z +Refs: #123 +``` + +## Specification + +The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt). + +1. Commits MUST be prefixed with a type, which consists of a noun, `feat`, `fix`, etc., followed + by the OPTIONAL scope, OPTIONAL `!`, and REQUIRED terminal colon and space. +1. The type `feat` MUST be used when a commit adds a new feature to your application or library. +1. The type `fix` MUST be used when a commit represents a bug fix for your application. +1. A scope MAY be provided after a type. A scope MUST consist of a noun describing a + section of the codebase surrounded by parenthesis, e.g., `fix(parser):` +1. A description MUST immediately follow the colon and space after the type/scope prefix. + The description is a short summary of the code changes, e.g., _fix: array parsing issue when multiple spaces were contained in string_. +1. A longer commit body MAY be provided after the short description, providing additional contextual information about the code changes. The body MUST begin one blank line after the description. +1. A commit body is free-form and MAY consist of any number of newline separated paragraphs. +1. One or more footers MAY be provided one blank line after the body. Each footer MUST consist of + a word token, followed by either a `:` or `#` separator, followed by a string value (this is inspired by the + [git trailer convention](https://git-scm.com/docs/git-interpret-trailers)). +1. A footer's token MUST use `-` in place of whitespace characters, e.g., `Acked-by` (this helps differentiate + the footer section from a multi-paragraph body). An exception is made for `BREAKING CHANGE`, which MAY also be used as a token. +1. A footer's value MAY contain spaces and newlines, and parsing MUST terminate when the next valid footer + token/separator pair is observed. +1. Breaking changes MUST be indicated in the type/scope prefix of a commit, or as an entry in the + footer. +1. If included as a footer, a breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by a colon, space, and description, e.g., + _BREAKING CHANGE: environment variables now take precedence over config files_. +1. If included in the type/scope prefix, breaking changes MUST be indicated by a + `!` immediately before the `:`. If `!` is used, `BREAKING CHANGE:` MAY be omitted from the footer section, + and the commit description SHALL be used to describe the breaking change. +1. Types other than `feat` and `fix` MAY be used in your commit messages, e.g., _docs: update ref docs._ +1. The units of information that make up Conventional Commits MUST NOT be treated as case sensitive by implementors, with the exception of BREAKING CHANGE which MUST be uppercase. +1. BREAKING-CHANGE MUST be synonymous with BREAKING CHANGE, when used as a token in a footer. + +## Why Use Conventional Commits + +- Automatically generating CHANGELOGs. +- Automatically determining a semantic version bump (based on the types of commits landed). +- Communicating the nature of changes to teammates, the public, and other stakeholders. +- Triggering build and publish processes. +- Making it easier for people to contribute to your projects, by allowing them to explore + a more structured commit history. + +## FAQ + +### How should I deal with commit messages in the initial development phase? + +We recommend that you proceed as if you've already released the product. Typically _somebody_, even if it's your fellow software developers, is using your software. They'll want to know what's fixed, what breaks etc. + +### Are the types in the commit title uppercase or lowercase? + +Any casing may be used, but it's best to be consistent. + +### What do I do if the commit conforms to more than one of the commit types? + +Go back and make multiple commits whenever possible. Part of the benefit of Conventional Commits is its ability to drive us to make more organized commits and PRs. + +### Doesn’t this discourage rapid development and fast iteration? + +It discourages moving fast in a disorganized way. It helps you be able to move fast long term across multiple projects with varied contributors. + +### Might Conventional Commits lead developers to limit the type of commits they make because they'll be thinking in the types provided? + +Conventional Commits encourages us to make more of certain types of commits such as fixes. Other than that, the flexibility of Conventional Commits allows your team to come up with their own types and change those types over time. + +### How does this relate to SemVer? + +`fix` type commits should be translated to `PATCH` releases. `feat` type commits should be translated to `MINOR` releases. Commits with `BREAKING CHANGE` in the commits, regardless of type, should be translated to `MAJOR` releases. + +### How should I version my extensions to the Conventional Commits Specification, e.g. `@jameswomack/conventional-commit-spec`? + +We recommend using SemVer to release your own extensions to this specification (and +encourage you to make these extensions!) + +### What do I do if I accidentally use the wrong commit type? + +#### When you used a type that's of the spec but not the correct type, e.g. `fix` instead of `feat` + +Prior to merging or releasing the mistake, we recommend using `git rebase -i` to edit the commit history. After release, the cleanup will be different according to what tools and processes you use. + +#### When you used a type _not_ of the spec, e.g. `feet` instead of `feat` + +In a worst case scenario, it's not the end of the world if a commit lands that does not meet the Conventional Commits specification. It simply means that commit will be missed by tools that are based on the spec. + +### Do all my contributors need to use the Conventional Commits specification? + +No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers. +A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge. + +### How does Conventional Commits handle revert commits? + +Reverting code can be complicated: are you reverting multiple commits? if you revert a feature, should the next release instead be a patch? + +Conventional Commits does not make an explicit effort to define revert behavior. Instead we leave it to tooling +authors to use the flexibility of _types_ and _footers_ to develop their logic for handling reverts. + +One recommendation is to use the `revert` type, and a footer that references the commit SHAs that are being reverted: + +``` +revert: let us never again speak of the noodle incident + +Refs: 676104e, a215868 +``` diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md new file mode 100644 index 0000000..5034119 --- /dev/null +++ b/.github/CONTRIBUTING.md @@ -0,0 +1,15 @@ +# Contributing + +If you wish to contribute to the NanoForge project, fork the repository and submit a pull request. Please mind following the pre-commit hooks to keep the codebase as clean as possible. + +## Setup + +To get ready to work on the codebase, please do the following: + +1. Fork & clone the repository, and make sure you're on the **main** branch +2. Run `pnpm install --frozen-lockfile` ([install](https://pnpm.io/installation)) +3. Clone the cli and make the cli depend on your loader (put the version of loaders in package.json to `file:relative_path_to_loader_part`) +4. Make your changes +5. Test with the CLI +6. Run `pnpm format && pnpm build` to run ESLint/Prettier, build and tests +7. [Submit a pull request](https://github.com/NanoForge-dev/Loader/compare) (Make sure you follow the [conventional commit format](https://github.com/NanoForge-dev/Loader/blob/main/.github/COMMIT_CONVENTION.md)) diff --git a/.github/FUNDING.md b/.github/FUNDING.md new file mode 100644 index 0000000..2018228 --- /dev/null +++ b/.github/FUNDING.md @@ -0,0 +1 @@ +github: [Exeloo, MartinFillon, Tchips46, bill-h4rper] diff --git a/.github/ISSUE_TEMPLATE/01-command_bug_report.yml b/.github/ISSUE_TEMPLATE/01-command_bug_report.yml new file mode 100644 index 0000000..69c8ca3 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/01-command_bug_report.yml @@ -0,0 +1,75 @@ +name: Bug report +description: Report an issue with Nanoforge Loader. +labels: [bug] +body: + - type: markdown + attributes: + value: | + Thank you for filing an issue! If you are here to ask a question, don't hesitate to open a discussion instead: https://github.com/NanoForge-dev/Loader/discussions. + + This issue form is for Nanoforge Loader. + - type: dropdown + id: application + attributes: + label: Which app is this bug report for? + options: + - client + - server + - website + - other + validations: + required: true + - type: textarea + id: description + attributes: + label: Issue description + description: Describe the issue in as much detail as possible. + placeholder: | + Steps to reproduce with below code sample: + 1. Do thing + 2. Observe behavior + 3. See error logs below + validations: + required: true + - type: textarea + id: code_sample + attributes: + label: Code sample + description: | + Your code sample should be: + 1. Minimal - Use as little code as possible that still produces the same problem (and is understandable) + 2. Complete - Provide all parts someone else needs to reproduce your problem + 3. Reproducible - Test the code you're about to provide to make sure it reproduces the problem + + This will be automatically formatted into code, so no need for backticks. + render: typescript + - type: textarea + id: versions + attributes: + label: Versions + description: List necessary versions here. This includes your package version, runtime version, operating system etc. + placeholder: | + - @nanoforge-dev/loader-client 1.0.0 (`npm ls @nanoforge-dev/loader-client`) + - Node.js 24.11.0 (`node --version`) + - TypeScript 5.9.3 (`npm ls typescript` if you use it) + - macOS Ventura 13.3.1 + validations: + required: true + - type: dropdown + id: priority + attributes: + label: Issue priority + description: Please be realistic. If you need to elaborate on your reasoning, please use the issue description field above. + options: + - Low (slightly annoying) + - Medium (should be fixed soon) + - High (immediate attention needed) + validations: + required: true + - type: input + id: dev_release + attributes: + label: I have tested this issue on a development release + placeholder: d23280c (commit hash) + description: | + The issue might already be fixed in a development main. This is not required, but helps us greatly. diff --git a/.github/ISSUE_TEMPLATE/02-feature_request.yml b/.github/ISSUE_TEMPLATE/02-feature_request.yml new file mode 100644 index 0000000..0941b73 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/02-feature_request.yml @@ -0,0 +1,44 @@ +name: Feature request +description: Request a new feature +labels: [enhancement request] +body: + - type: markdown + attributes: + value: | + Thank you for submitting an idea ! + - type: dropdown + id: application + attributes: + label: Which app is this feature request for? + options: + - client + - server + - website + - other + validations: + required: true + - type: textarea + id: description + attributes: + label: Feature + description: A clear and concise description of what the problem is, or what feature you want to be implemented. + placeholder: I'm always frustrated when..., A good addition would be... + validations: + required: true + - type: textarea + id: solution + attributes: + label: Ideal solution or implementation + description: A clear and concise description of what you want to happen. + validations: + required: true + - type: textarea + id: alternatives + attributes: + label: Alternative solutions or implementations + description: A clear and concise description of any alternative solutions or features you have considered. + - type: textarea + id: additional_context + attributes: + label: Other context + description: Any other context, screenshots, or file uploads that help us understand your feature request. diff --git a/.github/ISSUE_TEMPLATE/03-documentation_issue.yml b/.github/ISSUE_TEMPLATE/03-documentation_issue.yml new file mode 100644 index 0000000..f9542ee --- /dev/null +++ b/.github/ISSUE_TEMPLATE/03-documentation_issue.yml @@ -0,0 +1,27 @@ +name: 📗 Documentation Issue +description: Tell us if there is missing or incorrect documentation +labels: [documentation] +body: + - type: markdown + attributes: + value: | + Thank you for submitting a documentation request ! + - type: dropdown + attributes: + label: What is the type of issue? + multiple: true + options: + - Documentation is missing + - Documentation is incorrect + - Documentation is confusing + - Example code is not working + - Something else + - type: textarea + attributes: + label: What is the issue? + validations: + required: true + - type: textarea + attributes: + label: Where did you find it? + description: If possible, please provide the URL(s) where you found this issue. diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000..d1e46de --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,5 @@ +blank_issues_enabled: true +contact_links: + - name: 💬 Ask a Question + url: https://github.com/NanoForge-dev/Loader/discussions + about: Please ask questions in the discussion tab. diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md new file mode 100644 index 0000000..ff045d1 --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1,3 @@ +## What does this PR do? + +## How do you test this PR? diff --git a/.github/issue-labeler.yml b/.github/issue-labeler.yml new file mode 100644 index 0000000..be5b15f --- /dev/null +++ b/.github/issue-labeler.yml @@ -0,0 +1,11 @@ +app:client: + - "### Which app is this (bug + report|feature request) for\\?\\n\\nclient\\n" + +app:server: + - "### Which app is this (bug + report|feature request) for\\?\\n\\nserver\\n" + +app:website: + - "### Which app is this (bug + report|feature request) for\\?\\n\\nwebsite\\n" diff --git a/.github/labeler.yml b/.github/labeler.yml new file mode 100644 index 0000000..e4a5583 --- /dev/null +++ b/.github/labeler.yml @@ -0,0 +1,17 @@ +app:client: + - changed-files: + - any-glob-to-any-file: + - apps/client/* + - apps/client/**/* + +app:server: + - changed-files: + - any-glob-to-any-file: + - apps/server/* + - apps/server/**/* + +app:website: + - changed-files: + - any-glob-to-any-file: + - apps/website/* + - apps/website/**/* diff --git a/.github/labels.yml b/.github/labels.yml new file mode 100644 index 0000000..c5fc88e --- /dev/null +++ b/.github/labels.yml @@ -0,0 +1,67 @@ +- name: "blocked" + description: "This is blocked" + color: "e92f1d" + +- name: "bug" + description: "Something isn't working" + color: "d73a4a" + +- name: "chore" + description: "Changes that don't affect the codebase (eg. CI, docs)" + color: "eba8cc" + +- name: "ci" + description: "Changes to our CI configuration files and scripts" + color: "721cdb" + +- name: "documentation" + description: "Improvements or additions to documentation" + color: "0075ca" + +- name: "duplicate" + description: "This issue or pull request already exists" + color: "cfd3d7" + +- name: "enhancement" + description: "New feature or request" + color: "a2eeef" + +- name: "good first issue" + description: "Good for newcomers" + color: "7057ff" + +- name: "help wanted" + description: "Extra attention is needed" + color: "008672" + +- name: "invalid" + description: "This doesn't seem right" + color: "e4e669" + +- name: "app:client" + description: "Related to client app" + color: "aaa3dc" + +- name: "app:server" + description: "Related to server app" + color: "aaa3dc" + +- name: "app:website" + description: "Related to website app" + color: "aaa3dc" + +- name: "question" + description: "Further information is requested" + color: "d876e3" + +- name: "refactor" + description: "Code change that neither fixes a bug nor adds a feature" + color: "a3f2e8" + +- name: "tests" + description: "Adding missing tests or correcting existing tests" + color: "7f8f92" + +- name: "wontfix" + description: "This will not be worked on" + color: "ffffff" diff --git a/.github/logo.png b/.github/logo.png new file mode 100644 index 0000000000000000000000000000000000000000..35b9d5be6b36f66aa9fef62c73ab51a2331c2d22 GIT binary patch literal 20534 zcmeFYcTkki@-Mt(B}xVfB8W)NX-O(cGLkbau)qRKTyhj8hys#x77&n}Ge}a9AUWrp za|YjM{ho7v-&6Niy>;HY_x_GX0ZIpThgpC??o)78ef)Mh-0O7` zk(WlQPSo{0Fu{pK@>dB{@HmGV9sbApEol)5D!P~_9);2hC~vOu>5WY~=yPnUx=%MyF?GCT>)S{||(<@;iEN{c?FCzeHrp>x;0AsoEXRjssJ zXWF4D{^C27A*Qx2b#Tp|4B!9mNV36_Nx6kMbLb1C_Q_C>jTH{s;O)Np+aLU zB$+S2km|W`)twL|@jYSY2oJDnYfJAec>AHE7{54x?gDLzLx{Ql)%$tIKr-$*$C-Ao z`D>?h8ah4}#fthR|J-Q{aN>iCI?b|m(iiVw_$Dtc;<%aQm@mRhywERv$(MEST>QdI zlWHg)Jb1tSlMB9tx0I+fz0jya4Pn$}6lbCp+zjZ5FwhqDT{b}IE+i82MyD}_Klspz zuLVwsRSa`a5-P9;uj1%NX!h%;RLO@`?fo#O=-FoNHOS)+ctTc&exIIXL{$buz_fDv zv(Bqwk8j-)J6DWO%quK!Bh64Wtv(q_Ts*qjE7D9zI*EFDKjXU7QC#Ltnqh{nTgtv! zH!Ka*X1O45e_e=Yau$8!ssDi%<#xKY(?wtX%)gh$WaGytrODWU%6BhO+$FN@dr;oi zJfBY*uNf0oe&mmP%Ho1XO^s?M-D7m_;bw0+e^&%M-Ny4HQ9V3blmUiP7&jw9wPR%*E)n`IWeo93-Ju zuveZ=P<2mb4Kq(0GhuUj32|&ucQ8Nz4n;ud+~Kx%&R};j`ag8Rz%#O#lb-HR6NHTz zy^fM9ous`Jl#Y*skAsU{+8yS~Lobd^C+cKw0alZe`3DK$pBTLr0^tDW~_u!ND_b1kb*j!Il&wdFnc>XBu$8^y$eE& zo*t;D`{(%J4oXV@B5&vX4=w=w;B<#LaB_2Sal+x8e}BUnA?*qf`Nx3%w{JLW0Na#P z4eD&~;$#Muc7@s@82(Pe-0WZPJGeO6{+W)s87I^h3J01x1HE$pTbHtON~-^Q1IYqQ z7~J8{TL82Ft);`?c=c~X11bQry#Ll10kilY&i-3#WX+$s|9#XzU;i4!zqS4+qy97o zS}7@krR>dIkaLlf5~D{B7Hn>B1~Ui$c@!4lF*O%5<6}276&7IU6X4}zhd_k6+0A)P zO@#${%=v^&&HhG8&dwPDu``1rNdd$;U;rI+eh9ZI6e`4SAtYqV&SwsgFy-SiXSaYt zOnFWDEx34ux&B5%#R&$8FvRxnqe7B02T1YpLoCd>EV$YE1i5(G`FKnr?81T;rtGGs zJP<*1Gl;2>kiZ{O=4N0SdnY&qSbG>8VhQDRu(SMAfm|K%3spHWdLE9ydi_(PY70SF z056EqE5htt-2bPk1`G~WM?jF=_m%xj1cyYzR`&0iu7(f%$E?zJ5g_{2vCqV13Dl;pH zoh1}Fe*PiC|15|7Z^Q$_&n3viD`3uUYHn`E&L;%nXBRey2(ohtoAH}MxS>pmyJ^QnG%>Uln%?gTK8GvEzTs-VNLK*5=6gJ}%h6q})n+rmDfGG+JvYSFox!Addc+9yV{K8yj!b1N(=>P9i~!3J^=J$G2f07}|C635=ifW~tL5Kx0PxCRWq@u0R2ApHbk#ow zgVYND7eD`y^#6-J0Hpuh$$!M(|FY}9?D~&5@E(*wGg%5HlGURlfbvrsZ7&K9l*Uc?LSSD6K+>y(V4h{}>ZJKa- zWceTi4YRUhuPxUE?(^%m>NxASj`|}!t$ytHklO1gHTfSKs>+!4Lzj1ZCoN}gIlhkT zDsgL+cp!gRnX}n=Q(xFJOL_$f2U~iD#&N!56|(Fj1*rAi?&Qevb3g6SP_Xn>gPQd~ zZWL+qZC+->KJ(&As4zj)KWI>7 zvrg$(sW~cw)ILXPspnX@iqJeS4&b$%iGY3zL~CoMNNu5CbfU!X;s>4N+EbLt9{Myh zqb=`4{P8JjLzGl%W^XP_24=O@XrE9dIF z>~DSZane<&zRPqz75v?t8ENH@ipwtg+e+bfytySKnqaCOr<_uuT6CEEcgeodj5NS^ znHQqx4$hO~ex(kgL^%iFym*)u1jJ^Iyt^afKZjsGYfa$Jmok$6a5=~ENjXVPgXl@T z={Ft5xA!Tj`dM;FI?3I&D~0IfnfV1$R&5kBKxSJme4Vjs^0C^1_b?q$Ry7~Lmd_vK z<;La)NHw;5VY)uc8M$G!CBJVFF5Rmj&76b3PdR~U!bRZ z#5F&g`O|Aga`UF`o<6L7K!(4-Kvb5(!U092GubN6Z;Xix{$7)T))iQlF7i7iehEjh zD5^Z;S&qi_q|iX{3zROui6h19qB!WW?sJnQb{#GHIA~#fx^)A<8fL->sx6hmt)zQz zKo%1w_IlQ9WRY)~TMv?MOHRbE5;@0arJtO{C?`cJ>zS_Y9{VM1&9-O(PYJLo1`8v+ zkP!3$86~=fLTq#&=$nkkZ!%O+-?;szK9Z~a&e>Q~RDw2rP1|s(;Jo*gh{VMGxv6Mg zXs>&}NOVk*xj7x{?d;~nbGIvFEYG2q=3^#>V=(nJuOX~8i2_q9|<8nUNh%wTvFA>b&tO`rG_U?NkHwA`*LYhu# z#lueh-tW}tuvU4ECwKf z$5IW`XBCbxQGv6->E;#(Cc?zVzJbd5dTV%Rcwn!>W)zcEsUQQtb2d7jL+EJ)pSFIS z5{_eH5EhU1b&#^wyMa$MRN(!Gl;61yIHIAG*2p8}BQ@B>s(3TivC7s|1GfeBv}2|1f*b{n8)RMvR7m%I7&tq_&ri*cP}1zImw$PPFv* zd#!`4}1efssxs9lRbxC8mWhTA%+Tf-;=Fam0 zu^9u4>FV_l_O^UXoOjjmLNp!IN zz2L~H(l8lU6uw6#`t4OKR?}(Mpz!qBS)p6^83C>36VR}Eso?IWWdqeCd)=OAt(}br z?!7}A-x>x&vAl*5?fBm+(1Ks(DU!awYH}O?6&;u4;mu1*EI1ggR)$e*>=WS120vCynp#CArtW8rt$ZS-P5W{sBulx` zW{PrX@k@cR{Uk=JAvmQk>*Gm>TDyqVxb=etx8T2itKu?x2BM~n<)Gsi3o#&p5AngeU+fr`Nh@6D`l2~_K&WnpRj-Oz_rQdz5C-%BPwImy%#k|M%WA|(V&YfbJ*mYe82PwQ4uJDXq|r6A887-lXUxuYIRFVPBaRF5JS)i@Qk5 zh+SGC($$!g;!B(#6BVCkrQhVPDGW5j{h%F7#VI!F8a8a{hn$WxiaaCz;69`CrqYb=59Hst!jAoTitxq9?EC6k#9a0q|mrp zpg`s~8yDPT#`ZG6pp$JUcXk%pqO zQas|S#gy2qM`GNX8SuCzvR7~A6*d>qvaqbrxL_&|BlUe%Zxk#XSyUM?44jV^ci|pR zuZWTcF0wQ&sAbzoSXN?GWM;7#MzrFE$_L2sq`Cb(jElj@*;V|AY}Yu;={DbD<&kd| zE+~)`y`&b(x$u+``j|m{FNMC*!6SbMseJlp7%gz`wRH-^evNLZY86;iv|%o2DNpl% zkk&=CYO}>xQLB4*2QfGMPiu}!eJsml6OKXMv7=FPB*hhG5G^Z9(df^*Ks8bo7BTIR zNj)@N1Oy1E4duePID%jLT*t3-GCOvZ>*Yl2|~uOf}Fmo?_lzCVs*Pd2ZSQWn}>h;0|5{6f!@0VsNakw$MlDs-!K2U$Zt5XL0JHfyXSaeS8W zwXryAkGwTT=yvRjo+CW4x_f;TFGzG8#Z7>zlB2oo7j-94tLI^uGnUT9hbswACQeHZ zJu}D}_gIXDGaq72Y+|>blq%|9^7*puRAK0*ZTSx~H`P4PzCb;23YY6}O4|w$Q}=hX z-DqSb8a+>)7j!+5koE*|&EoIVPJG=iBaO#|_VVu5c&-|_=PsAC>2F?r^!w|~+Vn;F z8Pb+knZ(bO1uNDfI{0pz!316a`~vIIstXqV*WM^Uzf3x32bG_u?4DlZT}F4ieRm?w zDMMOB&OxA`mB>?MTv*U4$RMMTKXVskBhKGXho;KK9=1HS)?LlZJ-#kGuHv)h$rOv! zS?CF#n5wFimH97|d}F$HOBm~}C>?Ay<{5W^1<_l{`qEtYefL_bp&k^kgV3@uO)xi?%0p3IiE$P&T;%xJSd6E8e{7DEbGhBjLub^ zBg4_;q@Fc{Dm65SMtB5cV=$nzl1kEu)|nql^2@(|jcidBgw~CqY;24~My?cWvsSUX zZhp?+#Y3ejMXNU+t_)nld2U%~|Aj?BNxxw^lnl#Y5~E=+{N?!GxQ+28XkqZ_T3hY{ zjf7FwYz@xr1V%#v+E~@~uC<(#CYr-L5x;W260?3MGxD8+hWj)P#yK$;-rg1u{3|A^ zixA1R&idp#N%$9+vie&tJHBpB6UXWtP>^!A*`5=!M&$h;op8d^npnyBi{7;nbwP2{ z+(S-bR3-IyGYEI5AKg^u1_hEMhs7c>`ETS2Xil&h}WG)vyrm zYTVqcPIj3#**cXtyA4nv@z-y<>ozKKN*S>KjuTPCk%N{7NsP(=_F7_=6Xaft<9gIZ z9lq=D!qQAnUjpB|6^?%js$WRVnZ^$(-uE9!rPfv`VHsWzAJibaH*|}dfy42xqPyF? zvnn>cw=I0P^Yx$0KvvF3?ocXl;W(-Pd zHE&#Y8p3Xs$jfh5fw(#H=!zjxiiO??mS@>aizD_hHuXSJ1RW3a2qpVLIRm&~o8 z1C+~@9Ml(Lp5Q!1Ns%nHvCYZ-MX|Rkj`=A5&2?qIj`wK}G=6Pfa(*ZQ`5WxM$FHpr z&g{ESvo+ulh~kgtWG<_2a9zY)#n}p0lGyhxYe-PQ1##GpLUzu z`C`#Qnx)#{s=@1?F-W@O3+iO zc-V&RRMe~2&wHth;aFc44xua=2oglHoBjC%eZcFLH+%y+mGxxhPh?* zs#n>=xJOINH6lRVK#ew%$k?!>ZexLBgF!LW@z<*K9%3jaD~b+aZZXmc0*($$K~#G2 zbl<+1IQ7B$ckeeXK@Pt7P}*Z23+Kk(7xjt{dg=uOMGhaCB z8c7B6B4?iuOLU$k%AfAuOasDJe`)Bgf3$e|_ZJvn2f^aob^ zUE4>R$K+Z({uW=lypQ)EDy#Z)nv70`E`zCMZTY%ibzWUeh6ZwO@Lw7+3%sro8792fs|Rkj*Ks`=Pa%0ITrP)!={}!9{7h&X?ns#ax_u!(NBa@S}qDbe!tXf4c62O zY|+&td-@*jHF-*!uFsmF0|vn+`}YkNO7dF|uD z)#pfKIR(G_*KCrxM(yBQSl&K+Nr*S|gQGsuM4hJxmmjT^;D-f)c(Le2!bSejfc1%&m_~m!^)UU4+8Bvd!k1C~JG`cqI#bee2#a_-e6APG1$q z>~7hor-8wq=Z!&2vN%4}tm9fU4D@;=Ch&5?{r5^guPo>4To#wgv3?jl5=lD>qTnga zwHlrAfC38b9yT9MA-x#`Y_chPciZoFb~M@0*Dz|GxwW68)qZbV$f;fFxcIzmvmKhE zlDQo?W~(nJJDtGCmhW`?oN++iUm{LjTw-FLT${g&(VV08uyZ`_uKC^1RPDX@4N`{U zDqj>(#!N|1`oj#*w;ZU$WV_F{#r@O0SBkb&LprzpqoEZZoBJPnGX?9zJ##KXLjX@; z?n}EP(h?!3IcP{y31g)(`sCVkJRg4cn&0mQhAysyRD9u+)P4nUV!Q^J(=3~Ebe8b< zBjek`)wCJ==fRWxaa{>)x`r22kJzrjkTT-|uPp8*7zvxIk0r{*R$Km2V&AHt9 zUfrBF^4shByktsF<3zQjZCiB;(F&d+oUA5lc`FVb9^(7D#`$&7;+zY#{$cMxRUSOu zoqSbK{QD|w|EuT6FWy4qQ}V$-WN0iznOpa__T?33Z|G&kKET8Uzml;RlW0kz1)Awr zn-Aq8T*7;MM)?gs#`jdsGHdb*%A=4~XL%dTs(U97hkN`ex6aP9N!jIngBsGwbF_9B zp8dvu{uwhK70G<>&#HAI#m;Rte*)WmFSX$3fXC<8{+_8cPh>7(K>wq;$wTIx4nFw% zP9CQ%sg|3)vgPC6-t4YCiG~BrEM9K*u(A?>^T53c^Tl``wr_VA_69S>s|NiV-y`)? z8V^bSUs*FN>qgBS^#gY-i~6xV_JzP;>z zlLxzR?$DV?Yu_34N5$nrJPzx+?6n721fDhX>iQEC5MyAMhJ>8B<@hb;&R4j@s(y{} zuq1iAqYs8cCx_V=_Q>D(teX(*27yZrQ@B&B0TQpC;Cjg^G)rWRM(PKWXnr7U{*p0R1 zS=;W=W+TGoqk_%wM2q)kHB^F$-g9U%8~44Ak$kV@92+3xC}Fr3IrUGM-ou#Zh=Y<- z{UQVzEL8~7FGl)siXYQ^Qqg|@QZN}fARU;3a(ctE@unCt$J%mwY^-y0n;q;dwHySqjtEl3=?&A(AT2>Vu*B<2=~aAA~5<# zg45o~r+SNBYT9^+o`y!SJ$WQC;1(&c1{g1mY;W%G)p1mNDixKj23ELrbZrK`rtoQU zd@u7Bvy*%{|1+CvsYR&?TEkZ!gjpt9iLJPr1NVHr^Xb)5=$FH*z3RS3-j9iVLZ3bf zJNN2@EI5Hz7Rq}D+0$5Cef<_oip;;QVAtZNUw;TH!9w-TK1@ZC%RBNmyg%Gk9eZ-t z@j16TW@#H`QgLy<@g6#kV4GU$Z>MJl7rHsNN#k};O;1OwWL`Udw}L&4G^g)Y)=QXL zvSHrbe*Yt!y{IB2NbobCRRFf`2kbLr{CC*K{>L8J-(z*^z2gqM$p?JSI`n1eiBhhX?3^Fbg@pU-8t4dGM z7O!cZnK+f-j+oYyVT^~$Khpm6j$I$~in!d(Qnvm4_g#_<{Zb}XNh2mkt$)=Q2lc^+ zwmw!vC@SymZ%%uHsp2#!lLgXldw#Xg-fn87Wh@-o1;80^eeO>-*HvBE@7Gs{g}Cpp z6%PIxKW!=gfIs|0r&U05ZjAe5o4nY*R!#nf-gUdnI8+)W<)N=>`aXb z{NDHTHVn0LF9q3fVeAr+6r3oz&N`0(^q)I(5x?eCebnXw}I1h=E_M+ z#4CYTeK5@%b7y#A<(U3JQMat1iwn2i{VYFPu(7UWc@R)Jz-688JpwiP&n=uB(?)iX zw|Eg1aC-@W{LM;U9lFJsn_uPHmyns0xp{lj5SZG2qRxTp(E9NeLwKdyY>n<@_8$#xI{&Qa-{NVPK6JfYd1mhoC=>w(pgBz zi0A3KS3QU-XwVe4wY}crd3+ad?|VKm{egw0y~gL@H!=1#xt4}>v#tTP!PTOlQL03X zn%cv-q$#5N!IvGTnSg3WYRV~>)RJF@je-E|ORl zOG4p^!(;GHNJ1~^UZH3jN9&8+3~ssk%Q?+ye433b{&|^ZhjWp^^apd7o!w+6cyo)K zE3OHFUYNEXUc`2_-Q+FRJC;R#3|S;pB0j3Nq6|#)4{xv|Tf2XmDlAbC_~T@KdFLa< z#jo7R?=DN9#_(XDk$*UDZtueD(JF}JnV!MLz)<id|10(DMj=GU=5QqQ~l%aSj&M z_U{gIrlRn5h>mRgIV@+SKs2ot#ktU!>0H`<3gsVj+SB_N0@vbiA7)r$;nr4M zAD_uv0hId^ULImRYXw;(KzS(%0RN=D;`dkw2_F}frj-4XnzhXlh72*Sol>|rgU0(J z?&b}!TSs0o9y=WswKcp)=g6_JTM@@D?H=uCy^`g?P@KeAJ#_0Guy2Lb@De@W%K;f* zaeNi;(H`YyO!K;0>8r3HCA{Z9Q|O1H+;N0K@O<^_18r20JJ&f`Jtk=-hyam?im%XhJ<`i{UGr2L~Pu=oWAd+V*?W*$Y5!-vpq{Hq*Hk1S`jJN8sT~4V&Y8<0Kr`vu~AN zI7t*{NK2Uy->8;V@lseV_X6Q_HK zCx82G$d8_AFcH}Tqqa~uzq6rro7UD;L0<8Dq@eI5Q6)dw`!VwBn&70Rp61d z0P=+a@3K8vaLS($?!r*(s^`soI3*6b=15Tcj9w#qg5I9mw=D)P&I+qa zX&92c^&`|`*avkT1Ay09gO8hPYPGaHgE($nm+$?CZi@PC(Vxv&*rpHZ7sgsWkEfpY z1mCH%Tc9C?xxs85@=Qw1EcbcH!y>HgXQhW%K|88y(SjhA21tgJn- zLBmx_6E45EjfSA080_7r_40b{XKXOax!^O;x_W;7Ik#BKXnM9j*6NcPaG!FUN{GGR z=R+e~eBF_#sGzUO<;luJoUD>t~2l0+)&gHMd zlA@do8tkso7Mrv|7&58ke*?0$0>af(9&et{Y+f&Vs(Vcg0IY zM*K*ZI1M=)-jb&tzqY7Ys=gQHMTCjvC@5AY*^NRxUosP>N5HH~w)Uviows}M zckuN9o{be%ER@y4In^Ts&YB}>F}lgk@S#-P$tmOwc~kl7Ov#j<4B$%8kz7S6UmW_0 zbdk#1ow5~SmvS^j?@W%|f+X9i(mYpow*cS6rPr9F-X4NhLfJ>sGS761)3Zud!&#$C zv+L_s1H`)@X4moBN3hU*j4=0*Sw%svx-d_QMm3z3M43KK6U)eEzB>d_GGV3sq0Dt{ z_jQp|gBFbg01~o62!)r+lg-yo_EJ6Ee@G*juYXs*7#yo9y@O_C(#iO^ZgcHYkl>_y zbl=a*o0QNoeF$4jyvBFy`vgzwQkLP`q8PVgUQNW=N*r4ue)%_DiRzpukw1G9)g_e# zeLe4Z=$B|$T(AIN7zwM1epXv}FjZYttSb_{RLGn@|Eat@#GoqIV)M|fNnn<%Ze+J| z`zYvoxS$~Sz&N=K=>kd^mcG3`Ycp#rEKYW@?kvz%Q0S%q`VFDc{UmB2acEB9X|MKC zeN;3M_qs$2ln8t)2Fp*>mcsHrY{-f98(S2*L3xUmvQ=eRlsqRqm)CqM$m%ROBV-TL z7495&Onvj12ph{B@R|Y5U#QM>HTuXHe5@kX<$-tx+{f-yQ{GzkcR^=wx896LrmXL5 zzJTghn?foYCaTr)&6W9^c{9?k&TDKaH~UL1)z8uDKR#x+=W`K#X6ULY*QLbFynOsl zxztOxm$z{I=be#@3t+jw z5gQ)75^=LoWjE4e7k`xZgVk35a}F$o0BprZ*vo2YLFh6&{$e^9I$4?1>BxmwBypyA zNY9v5T=>SKjyILBDlD=ZZz#*GdsaA3)t37;^QiJ7%5=B)^Dl-K0V8acrE84{*IH1b`g`* zm>7)vs33!?Ah)U~mBMi~^AzB2hZl=ral+nm#`KCOZjlm4!U}93?9&1aJeq@^ zRE5Wm)iB%dY;ZQ;rV+8z*8<3{90R?C@NWe%L>}i51<|xvz=jT+rTOtYGp48I{CBU# z*R}oITmG>4>wTX)g8iAZ#our{pTk?5v9TG7u*Qb*ddE9m7MqEMF#};gx%Xq)`qv67 zdF&k*QkiKfCl8~blTmWXQHpC%XnW&4RJMC=B=>87WFjs~@hRu~ zj>`ZMo*3)KLtY%MZ71*aI~5%JtA+WN%FM%JV0@wv*|Ftex>DaDEf=?Jq;0F~ui)0Q zmh#u`Fh6Khb5)H_yjh|q)gtzASs~xX$BmhaL~jCr|v?7!OviJ3K9Fst{sOf0dUX zHenSfV&9hno-ARrSmIOIRjt3sn%Xk+XLbtv(|@?xEbh z;(t|7t>CAvx3xwdnVvUPADk45sBgEHAkV|WT<`$G;Pu8eZmsn6z`>vTP^I1kglM@U z5d&gw)F+x`vPI9pj#i(Q@|J~<)v-g& zXkfV3kmLTy6H|{cDJVxe?yS1798fvRMg)@LD1`C_uBE!sAUer6J$j4AE3zq>AZ}ud7eRJD}LD@H6)mT`NoEDs9uWS3vfr0QRg^|^_-xyyky&cw!Jl0HL~SL! zam%^)`Q(}HI?rr4Gs#)+T%TCW3J>N2AJQ_AuL0sP`Km zHuma}Qui}6Un)&T#%-IAM)b0=a{(oz$$M_7;=RY0y6^BZ*VT$28uTSuohZBEg@+qf z)~9%yikYCnp-Eyh>&em8DVq4{wA<$H^{y9{n{K;$WObV3+GLLJ(FS9~JGG?@biECy zQMP9=8cvn*LBh^pKnwwGQO9F>H3LpSusZ>vE9yCs(%@bie-8Y8nu%;PKsLt7jJ1)% zpDjtL`I=^o_n?sq_c<}R`IwcSM<6A(N0$(r3(dxQl_&09wypa8j8epm-4JV7=)msV z!dnA_-eqj*n;~!O6zymbi6Vf(hJPq2uA|Z(#Ms^frmRDWXVO*V_qk4Qedar*)BAQL zf&%=VZP+3MCBd;8YNPMnRIWP8J3yy2tmWI1CgGML!d`VMElPmN#Q-3;3oMK@1`JYb z7%7gt=pS7*@+=tXj$dLJMic=RXDvh5&tNF6h(9nn!w)4P-`6a`T3!H9pGo( zo9Cq#MgfGN()xPgArRu%3=)mT!oy4#w^evAv5JR9;>n}bNqAKto*269t;7gFP-RTTX$BG zPSK{9$6nmbCEp%{*%@bgQEgfvAfDImwBxSL|XHdkfZ z*H_yv^TsjHx4gaEKB<_R36nul5=tj@l&_b(-1irhInx;i+_e9SjgECs49CTI;4vb; zfjAW0Y+m*mYJ5HA25>&r^YA>hw8xS3w-Wb-++LTZfWc7=MWEUk000(MPi{<`^e&aNH8aw3&Df)pTOwRi(Ss<49t5+%W_es

ToNp^p|~>{X9Ei9kp3$J`jVDD@?wz7fzvJP4@2_rCIvGDIr| z4>(4XboB9V#4sQHKBk8(#X-IIoZ1`zyQY!9V2LYi*aw}$P!^{6vM1Dd4)`b$Jr;_j z*w-|UUlqmtNYn?(OMQIC&r=;zGDD1`4n>E5`D5j%_cJ$7r|sT=EkEL4l%G~Ij-&*3 zh6{~Jv2o_CKJI5+AbfuaK&zd*a0r`rJ$GiV^X}g2^ez0&g zAeT-Q(-!+yt#Y>0u6jwYWzX?w7k@&g@Xm5$iQ#`V5y9Yi_=+%9814A| z{H?@J5t?M4ke9#j9GDBy^In)S)m&tTwX^+5u9Qt**sY3fh<;Rhc`m7ysrcR_*veCy}<${u!W4bz{zzYvb$edJGz}^LvHG(;cNhW zSX*fQElN2_kp=}LMmaH@y%|8z`l4Arz;JWW{{3`SwYq5JIHG#Qne0vC@l7`SDZatR zP4nA^D?vxH%rIxBu9#>V389%Ey6Cy{hi}_cmHSBn6fd{4fOJAj`pdUXF#bZ0rHSQ7 zlt1NN@CE|kZ1RYHdaa3{>O@9Jxz+o9NBFf9I);u45VQdxP}E*GxiE!K`);V}9O*S0 zbPF?3LGKmlR@pt9PyikjW-#WobBKj14q*Sql09h`Y*C|YEY%0lrF)qE3Rgn2I9NrB%Sg26F<-<5*wgCI>UcK!4FXlUMeitTI=YpUCg&} zXp@*|J50H~lThX`lN0JW4}235t(43{awu}=c3?Q4*hX@qh(5`PCQNdOlTL#szO~WZ z#vsqEO=2v#$_6&^J}4gI=Pb2U%a!_|OM3rvvTAX-dyg_m3&7cZ(;dfomPpY585xvTN~vu9=ll z@`k+%_-g%<%`}NI*o1%=xE#ZpaeEY_q))`W6w4@N{1jT?FtT4i4^6B_pEys&pXdeR zppZ5A_-(Pn$qlQ5qz{Y?))ooa5c15cJxj?*KqoerloS%u*{4%{10Ss-1lBIDiz1LB zd~k?D9auO&fdf+@d*mCTMc%VkcjG4yxd4=yjh}IQj~dVviQ;yu&df&svgBw0h2wW! z7dl4tI~G_5I>wgrb*b>_Ex<-@S+teJLIUf<;M2t|dsp>pKVPE6J6#pMUd5=Eek}6_ zrv&P?q$hGa_6z_E8(bT2dTDsPgHQg+S`ymMI8bf^&Xcs2uV}=Thh=fnJ(6s_TF5gv ziZ^1j)XjN-lbwLnC@01f30)F8zFLAb0x0$(Z(1+21pr)g$1kWg?s&$n%Y=`2Zg~5n zK#%j*Vp?s9ptKDWgF>A?l~42Y_x-y0zO%U6qq1m?Dvs&8EhqD#IH^hWZbEmwACCcp z#H>_sxo+N2u;o>Z8Vlt>A$hu$Vf!lpYLAS&A$Uq+)Y90RC4DFX*svi0tQIX6{aFn^ z9eb0h{t^A=(uEr_gHu9e__OTxZ8zopRzCf66ZOIEA2Q52OUuGlNaz>tIzLNu&5rS0XwIDYYj;LNe77A0fWiwL-StBaXEnefV*Mz?Y$B`b~ z+(DhL1a9Ch`ZDSt4K2>_3MD8`?_sxQyZo4$!ACf=u$!qtk%9h?*-*@f5n)rk<1tj? zTRqZMY2iOi$AoLK?|+Aqm9Pj3h>wAdna_-VPrTR{H1BjF?ZVPlKYksOSb@Z!JTho% zJgUbI-IsorvjSkKsh%|>S{**U0q~Y$OfTu4ektK)%nSc`ciwWNb^H6t!|3xZ9K+x6 z)6>}B#^ym(u~W@p-1~vkLGww-~K{)AhVDNAFbcc{FrLU zS=avf6l_xaoIXw+U?VCw2AhH$fXtuj@9?{=E9tvUj5j;H8k?JE(=&3~2ejyt&dmoJOG$k;hOtnP-0 z?#t?AiW**EQ(#bVkW=;M4>{E@Qtl=x=?7g`@C+u?((d%%Y@66$`OP9D{WRfl;O@I^ z(mCrlmzUj2b5h-}sjaEf3$(8TDRPI0fJrxas^-6VAGslpoQ;!#Yp9nho1d9CV;C*^ z$$0HQzzUB2`dPV;U4QcJ67rT{N=c!<$bS0ZKocXNx%~Oyr{{xAZ(1At@UNce?ZjJg z>&I=qVvcM|_PV>2@H3m^3;{L??eKW48jzfbj+y|u1rF~*PI@daiep7uZEa)oKUpi) zonGy&ilvH-Kn@B#<01gX|2$QMJ2%eAP?^pjHiU38h%3sc+Ydnfh(kryUvO0L;0-AE z`#)?O{Ts^Mj6*_XLdCLK(Q#j+5|_Um*KxJ2cVpF?B^6;WcT+H+0l+UY>+lAPG&FXgJ8SH9-q7vVa5|ndwQPHh+f7 z)UXf8q#$wbXtAk9U`m$+|{3uh7~@VodnPQ@?NLPb;Q z9l$0T%<`kI@VkNevl^UpB4844VC9SR`quV$YH(u!y%ewr@kwQ#Y-#elbKCnXVG$EM zV^>j;-M~nmPBi1z)`0A=n8U!|veh9_df)B@LJ@Qb5X`$UD)ahGl-pRA{X74>pRYc0t;7Y3P@7IZJBqwGh7BH3|M0iNcwP3 zE$94X$M?^H{INk4G>-G3=%VowJ$;YQ5NJMnz)VCxI*=2zy;;jgOVzYk;ydCH69NKB zNv$B&9OaG@t76!jy%a(eHi7c(R;}NcoTl z2}q_!#NP)2rRKwrf +
+

+ NanoForge +

+
+

+ Tests status + Last commit + Contributors +

+ + +## About + +This repository contains the Loader of NanoForge. Check [releases][github-releases] to see versions of the Loader. Nanoforge is a powerful game engine for web browser. + +## Usage + +To use Nanoforge Loader, please refer to the [CLI documentation][cli-source] ! + +First, install the CLI : + +```bash +npm install -g @nanoforge-dev/cli +``` + +Create a new project : + +```bash +nf new +``` + +And then build and start it : + +```bash +cd +nf build +nf start +``` + +## Contributing + +Please read through our [contribution guidelines][contributing] before starting a pull request. We welcome contributions of all kinds, not just code! If you're stuck for ideas, look for the [good first issue][good-first-issue] label on issues in the repository. If you have any questions about the project, feel free to ask them on [Discussions][discussions]. Before creating your own issue or pull request, always check to see if one already exists! Don't rush contributions, take your time and ensure you're doing it correctly. + +## Help + +If you don't understand something in the documentation, you are experiencing problems, or you just need a gentle nudge in the right direction, please ask on [Discussions][discussions]. + +[contributing]: https://github.com/NanoForge-dev/Loader/blob/main/.github/CONTRIBUTING.md +[discussions]: https://github.com/NanoForge-dev/Loader/discussions +[cli-source]: https://github.com/NanoForge-dev/CLI +[github-releases]: https://github.com/NanoForge-dev/Loader/releases +[good-first-issue]: https://github.com/NanoForge-dev/Loader/contribute diff --git a/apps/client/LICENSE b/apps/client/LICENSE index 62c6400..4672486 100644 --- a/apps/client/LICENSE +++ b/apps/client/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright © 2025 NanoForge +Copyright © 2026 NanoForge Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/apps/client/README.md b/apps/client/README.md new file mode 100644 index 0000000..16dec19 --- /dev/null +++ b/apps/client/README.md @@ -0,0 +1,56 @@ +
+
+

+ NanoForge +

+
+

+ npm version + npm downloads + Tests status + Last commit + Contributors +

+
+ +## About + +This repository contains the Loader Client of NanoForge. Check [releases][github-releases] to see versions of the Loader. Nanoforge is a powerful game engine for web browser. + +## Usage + +To use Nanoforge Loader, please refer to the [CLI documentation][cli-source] ! + +First, install the CLI : + +```bash +npm install -g @nanoforge-dev/cli +``` + +Create a new project : + +```bash +nf new +``` + +And then build and start it : + +```bash +cd +nf build +nf start +``` + +## Contributing + +Please read through our [contribution guidelines][contributing] before starting a pull request. We welcome contributions of all kinds, not just code! If you're stuck for ideas, look for the [good first issue][good-first-issue] label on issues in the repository. If you have any questions about the project, feel free to ask them on [Discussions][discussions]. Before creating your own issue or pull request, always check to see if one already exists! Don't rush contributions, take your time and ensure you're doing it correctly. + +## Help + +If you don't understand something in the documentation, you are experiencing problems, or you just need a gentle nudge in the right direction, please ask on [Discussions][discussions]. + +[contributing]: https://github.com/NanoForge-dev/Loader/blob/main/.github/CONTRIBUTING.md +[discussions]: https://github.com/NanoForge-dev/Loader/discussions +[cli-source]: https://github.com/NanoForge-dev/CLI +[github-releases]: https://github.com/NanoForge-dev/Loader/releases +[good-first-issue]: https://github.com/NanoForge-dev/Loader/contribute diff --git a/apps/server/LICENSE b/apps/server/LICENSE index 62c6400..4672486 100644 --- a/apps/server/LICENSE +++ b/apps/server/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright © 2025 NanoForge +Copyright © 2026 NanoForge Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/apps/server/README.md b/apps/server/README.md new file mode 100644 index 0000000..b55d6cb --- /dev/null +++ b/apps/server/README.md @@ -0,0 +1,56 @@ +
+
+

+ NanoForge +

+
+

+ npm version + npm downloads + Tests status + Last commit + Contributors +

+
+ +## About + +This repository contains the Loader Server of NanoForge. Check [releases][github-releases] to see versions of the Loader. Nanoforge is a powerful game engine for web browser. + +## Usage + +To use Nanoforge Loader, please refer to the [CLI documentation][cli-source] ! + +First, install the CLI : + +```bash +npm install -g @nanoforge-dev/cli +``` + +Create a new project : + +```bash +nf new +``` + +And then build and start it : + +```bash +cd +nf build +nf start +``` + +## Contributing + +Please read through our [contribution guidelines][contributing] before starting a pull request. We welcome contributions of all kinds, not just code! If you're stuck for ideas, look for the [good first issue][good-first-issue] label on issues in the repository. If you have any questions about the project, feel free to ask them on [Discussions][discussions]. Before creating your own issue or pull request, always check to see if one already exists! Don't rush contributions, take your time and ensure you're doing it correctly. + +## Help + +If you don't understand something in the documentation, you are experiencing problems, or you just need a gentle nudge in the right direction, please ask on [Discussions][discussions]. + +[contributing]: https://github.com/NanoForge-dev/Loader/blob/main/.github/CONTRIBUTING.md +[discussions]: https://github.com/NanoForge-dev/Loader/discussions +[cli-source]: https://github.com/NanoForge-dev/CLI +[github-releases]: https://github.com/NanoForge-dev/Loader/releases +[good-first-issue]: https://github.com/NanoForge-dev/Loader/contribute diff --git a/apps/website/LICENSE b/apps/website/LICENSE index 62c6400..4672486 100644 --- a/apps/website/LICENSE +++ b/apps/website/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright © 2025 NanoForge +Copyright © 2026 NanoForge Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/apps/website/README.md b/apps/website/README.md new file mode 100644 index 0000000..24d0689 --- /dev/null +++ b/apps/website/README.md @@ -0,0 +1,56 @@ +
+
+

+ NanoForge +

+
+

+ npm version + npm downloads + Tests status + Last commit + Contributors +

+
+ +## About + +This repository contains the Loader Website of NanoForge. Check [releases][github-releases] to see versions of the Loader. Nanoforge is a powerful game engine for web browser. + +## Usage + +To use Nanoforge Loader, please refer to the [CLI documentation][cli-source] ! + +First, install the CLI : + +```bash +npm install -g @nanoforge-dev/cli +``` + +Create a new project : + +```bash +nf new +``` + +And then build and start it : + +```bash +cd +nf build +nf start +``` + +## Contributing + +Please read through our [contribution guidelines][contributing] before starting a pull request. We welcome contributions of all kinds, not just code! If you're stuck for ideas, look for the [good first issue][good-first-issue] label on issues in the repository. If you have any questions about the project, feel free to ask them on [Discussions][discussions]. Before creating your own issue or pull request, always check to see if one already exists! Don't rush contributions, take your time and ensure you're doing it correctly. + +## Help + +If you don't understand something in the documentation, you are experiencing problems, or you just need a gentle nudge in the right direction, please ask on [Discussions][discussions]. + +[contributing]: https://github.com/NanoForge-dev/Loader/blob/main/.github/CONTRIBUTING.md +[discussions]: https://github.com/NanoForge-dev/Loader/discussions +[cli-source]: https://github.com/NanoForge-dev/CLI +[github-releases]: https://github.com/NanoForge-dev/Loader/releases +[good-first-issue]: https://github.com/NanoForge-dev/Loader/contribute From 472799718c07e5629cbaac0471f3cdbf37b78234 Mon Sep 17 00:00:00 2001 From: Exelo Date: Sat, 10 Jan 2026 16:26:12 +0100 Subject: [PATCH 2/5] docs: add documentation to labeler --- .github/issue-labeler.yml | 3 +++ .github/labeler.yml | 6 ++++++ 2 files changed, 9 insertions(+) diff --git a/.github/issue-labeler.yml b/.github/issue-labeler.yml index be5b15f..7e2d152 100644 --- a/.github/issue-labeler.yml +++ b/.github/issue-labeler.yml @@ -9,3 +9,6 @@ app:server: app:website: - "### Which app is this (bug report|feature request) for\\?\\n\\nwebsite\\n" + +documentation: + - "### What is the type of issue?\\n" diff --git a/.github/labeler.yml b/.github/labeler.yml index e4a5583..e366525 100644 --- a/.github/labeler.yml +++ b/.github/labeler.yml @@ -15,3 +15,9 @@ app:website: - any-glob-to-any-file: - apps/website/* - apps/website/**/* + +documentation: + - changed-files: + - any-glob-to-any-file: + - docs/* + - docs/**/* From a20cb87040459d093648c8c6fb05404add3d8049 Mon Sep 17 00:00:00 2001 From: Exelo Date: Sat, 10 Jan 2026 17:53:01 +0100 Subject: [PATCH 3/5] docs: fix labeler --- .github/ISSUE_TEMPLATE/02-feature_request.yml | 2 +- .github/issue-labeler.yml | 3 --- .github/labeler.yml | 6 ------ 3 files changed, 1 insertion(+), 10 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/02-feature_request.yml b/.github/ISSUE_TEMPLATE/02-feature_request.yml index 0941b73..1ecd080 100644 --- a/.github/ISSUE_TEMPLATE/02-feature_request.yml +++ b/.github/ISSUE_TEMPLATE/02-feature_request.yml @@ -1,6 +1,6 @@ name: Feature request description: Request a new feature -labels: [enhancement request] +labels: [enhancement] body: - type: markdown attributes: diff --git a/.github/issue-labeler.yml b/.github/issue-labeler.yml index 7e2d152..be5b15f 100644 --- a/.github/issue-labeler.yml +++ b/.github/issue-labeler.yml @@ -9,6 +9,3 @@ app:server: app:website: - "### Which app is this (bug report|feature request) for\\?\\n\\nwebsite\\n" - -documentation: - - "### What is the type of issue?\\n" diff --git a/.github/labeler.yml b/.github/labeler.yml index e366525..e4a5583 100644 --- a/.github/labeler.yml +++ b/.github/labeler.yml @@ -15,9 +15,3 @@ app:website: - any-glob-to-any-file: - apps/website/* - apps/website/**/* - -documentation: - - changed-files: - - any-glob-to-any-file: - - docs/* - - docs/**/* From 9588fc95900995d33dd227ebdc3165efdf7d62b6 Mon Sep 17 00:00:00 2001 From: Exelo Date: Sat, 10 Jan 2026 18:18:48 +0100 Subject: [PATCH 4/5] docs: fix readme badges --- README.md | 5 +++-- apps/client/README.md | 3 ++- apps/server/README.md | 3 ++- apps/website/README.md | 3 ++- 4 files changed, 9 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 8160dea..85d655b 100644 --- a/README.md +++ b/README.md @@ -5,8 +5,9 @@


- Tests status - Last commit + Tests status + Documentation status + Last commit Contributors

diff --git a/apps/client/README.md b/apps/client/README.md index 16dec19..c70ef37 100644 --- a/apps/client/README.md +++ b/apps/client/README.md @@ -7,7 +7,8 @@

npm version npm downloads - Tests status + Tests status + Documentation status Last commit Contributors

diff --git a/apps/server/README.md b/apps/server/README.md index b55d6cb..f8cddd1 100644 --- a/apps/server/README.md +++ b/apps/server/README.md @@ -7,7 +7,8 @@

npm version npm downloads - Tests status + Tests status + Documentation status Last commit Contributors

diff --git a/apps/website/README.md b/apps/website/README.md index 24d0689..2935b6e 100644 --- a/apps/website/README.md +++ b/apps/website/README.md @@ -7,7 +7,8 @@

npm version npm downloads - Tests status + Tests status + Documentation status Last commit Contributors

From f9d0ec91dfd9c60d3fd90212358135cff8494c09 Mon Sep 17 00:00:00 2001 From: Exelo Date: Sat, 10 Jan 2026 18:56:10 +0100 Subject: [PATCH 5/5] docs: fix readme indentation --- README.md | 4 ++-- apps/client/README.md | 20 ++++++++++---------- apps/server/README.md | 20 ++++++++++---------- apps/website/README.md | 20 ++++++++++---------- 4 files changed, 32 insertions(+), 32 deletions(-) diff --git a/README.md b/README.md index 85d655b..eb26e0f 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@
-
-

+
+

NanoForge


diff --git a/apps/client/README.md b/apps/client/README.md index c70ef37..98052bd 100644 --- a/apps/client/README.md +++ b/apps/client/README.md @@ -1,17 +1,17 @@
-
-

- NanoForge -

-
-

+
+

+ NanoForge +

+
+

npm version - npm downloads - Tests status + npm downloads + Tests status Documentation status Last commit - Contributors -

+ Contributors +

## About diff --git a/apps/server/README.md b/apps/server/README.md index f8cddd1..e24a66f 100644 --- a/apps/server/README.md +++ b/apps/server/README.md @@ -1,17 +1,17 @@
-
-

- NanoForge -

-
-

+
+

+ NanoForge +

+
+

npm version - npm downloads - Tests status + npm downloads + Tests status Documentation status Last commit - Contributors -

+ Contributors +

## About diff --git a/apps/website/README.md b/apps/website/README.md index 2935b6e..3f57e2c 100644 --- a/apps/website/README.md +++ b/apps/website/README.md @@ -1,17 +1,17 @@
-
-

- NanoForge -

-
-

+
+

+ NanoForge +

+
+

npm version - npm downloads - Tests status + npm downloads + Tests status Documentation status Last commit - Contributors -

+ Contributors +

## About