├── .github ├── FUNDING.yml ├── ISSUE_TEMPLATE │ ├── custom.md │ ├── feature_request.md │ └── bug_report.md └── workflows │ └── blog-post-workflow.yml ├── assets └── logo.png ├── LICENSE ├── profile └── README.md ├── README.md └── CODE_OF_CONDUCT.md /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | github: matyo91 2 | -------------------------------------------------------------------------------- /assets/logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/darkwood-com/.github/main/assets/logo.png -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/custom.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Custom issue template 3 | about: Describe this issue template's purpose here. 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | 11 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Is your feature request related to a problem? Please describe.** 11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 12 | 13 | **Describe the solution you'd like** 14 | A clear and concise description of what you want to happen. 15 | 16 | **Describe alternatives you've considered** 17 | A clear and concise description of any alternative solutions or features you've considered. 18 | 19 | **Additional context** 20 | Add any other context or screenshots about the feature request here. 21 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **To Reproduce** 14 | Steps to reproduce the behavior: 15 | 1. Go to '...' 16 | 2. Click on '....' 17 | 3. Scroll down to '....' 18 | 4. See error 19 | 20 | **Expected behavior** 21 | A clear and concise description of what you expected to happen. 22 | 23 | **Screenshots** 24 | If applicable, add screenshots to help explain your problem. 25 | 26 | **Desktop (please complete the following information):** 27 | - OS: [e.g. iOS] 28 | - Browser [e.g. chrome, safari] 29 | - Version [e.g. 22] 30 | 31 | **Smartphone (please complete the following information):** 32 | - Device: [e.g. iPhone6] 33 | - OS: [e.g. iOS8.1] 34 | - Browser [e.g. stock browser, safari] 35 | - Version [e.g. 22] 36 | 37 | **Additional context** 38 | Add any other context about the problem here. 39 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2021 Darkwood 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /.github/workflows/blog-post-workflow.yml: -------------------------------------------------------------------------------- 1 | name: Latest blog post workflow 2 | on: 3 | schedule: # Run workflow automatically 4 | - cron: '0 1 * * *' # Runs every day at 01:00 5 | workflow_dispatch: # Run workflow manually (without waiting for the cron to be called), through the Github Actions Workflow page directly 6 | 7 | jobs: 8 | update-readme-with-blog: 9 | name: Update this repo's README with latest blog posts 10 | runs-on: ubuntu-latest 11 | steps: 12 | - uses: actions/checkout@v2 13 | - uses: gautamkrishnar/blog-post-workflow@1.4.0 14 | with: 15 | comment_tag_name: "BLOG-POST-LIST" 16 | readme_path: "./README.md" 17 | commit_message: ":memo: Updated README with the latest Feedburner blog post" 18 | feed_list: 'https://feeds.feedburner.com/darkwood-fr/blog,https://feeds.feedburner.com/uniflow-io/blog' 19 | - uses: gautamkrishnar/blog-post-workflow@1.4.0 20 | with: 21 | comment_tag_name: "BLOG-POST-LIST" 22 | readme_path: "./profile/README.md" 23 | commit_message: ":memo: Updated README with the latest Feedburner blog post" 24 | feed_list: 'https://feeds.feedburner.com/darkwood-fr/blog,https://feeds.feedburner.com/uniflow-io/blog' 25 | -------------------------------------------------------------------------------- /profile/README.md: -------------------------------------------------------------------------------- 1 |

2 | 3 | Darkwood 4 | 5 |

6 | 7 | # Darkwood 8 | 9 | At Darkwood we like Computer 💻 and Internet 🌎 that bring knowledge 💡 and creation 🚀 for relatively no cost 💶 or energy ⚡️. 10 | 11 | What we can contribute is about exploring Tiny Design Mechanics ⚙️ as Processing, Generating, Rendering, Filtering, Solving things that are more relevant to Web 🌐, Music 🎛 and Games 🎮. 12 | 13 | We can see how working together and bring our expertise on [Symfony](https://symfony.com) for back-end, [React.js](https://reactjs.org) for front-end and [Flow](https://github.com/darkwood-com/flow) for automation. 14 | We are sensitive to the quality of the code, the use of good practices and to its maintainability. 15 | 16 | Keys skills : 17 | - Backend : [PHP](https://www.php.net), [Symfony](https://symfony.com), [API-Platform](https://api-platform.com) 18 | - Frontend : [Symfony UX](https://ux.symfony.com), [React.js](https://reactjs.org), [Typescript](https://www.typescriptlang.org), [Bootstrap](https://getbootstrap.com) 19 | - Automation : [Flow](https://github.com/darkwood-com/flow) 20 | - CMS : [Sulu](https://sulu.io) 21 | - Ecommerce : [Sylius](https://sylius.com), [Stripe](https://stripe.com) 22 | - Dev stack : [Git](https://git-scm.com), [Docker](https://www.docker.com) 23 | - Quality : Continus integration, unit testing, code review 24 | - Agility methods : Scrum, Kanban 25 | 26 | ## Blog 27 | 28 | 29 | - [⭐️ Meetup AFUP Paris Décembre 2025](https://blog.darkwood.com/article/meetup-afup-paris-decembre-2025) 30 | - [🏛️ Open Source Experience 2025: an ecosystem that is organizing itself, asserting itself and accelerating](https://blog.darkwood.com/article/open-source-experience-2025-an-ecosystem-that-is-organizing-itself-asserting-itself-and-accelerating) 31 | - [🚀 IA Pulse](https://blog.darkwood.com/article/ia-pulse) 32 | - [🧩 Meetup AFUP Paris – Novembre 2025](https://blog.darkwood.com/article/meetup-afup-paris-novembre-2025) 33 | - [🤖 AI Café Club #12: Creation, business, cinema… AI in all its forms at the Monnaie de Paris](https://blog.darkwood.com/article/ai-cafe-club-12-creation-business-cinema-ai-in-all-its-forms-at-the-monnaie-de-paris) 34 | 35 | 36 | ## Links 37 | 38 |

39 | darkwood 40 | email 41 | twitter 42 | linkedin 43 | discord 44 |

45 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 |

2 | 3 | Darkwood 4 | 5 |

6 | 7 | # Darkwood 8 | 9 | At Darkwood we like Computer 💻 and Internet 🌎 that bring knowledge 💡 and creation 🚀 for relatively no cost 💶 or energy ⚡️. 10 | 11 | What we can contribute is about exploring Tiny Design Mechanics ⚙️ as Processing, Generating, Rendering, Filtering, Solving things that are more relevant to Web 🌐, Music 🎛 and Games 🎮. 12 | 13 | We can see how working together and bring our expertise on [Symfony](https://symfony.com) for back-end, [React.js](https://reactjs.org) for front-end and [n8n](https://n8n.io) for automation. 14 | We are sensitive to the quality of the code, the use of good practices and to its maintainability. 15 | 16 | Keys skills : 17 | - Backend : [PHP](https://www.php.net), [Symfony](https://symfony.com), [API-Platform](https://api-platform.com), [Node.js](https://nodejs.org/) 18 | - Frontend : [Typescript](https://www.typescriptlang.org), [React.js](https://fr.reactjs.org), [Bootstrap](https://getbootstrap.com), [Next.js](https://nextjs.org) 19 | - Automation : [Flow](https://github.com/darkwood-fr/flow), [Uniflow](https://uniflow.io), [n8n](https://n8n.io) 20 | - CMS : [Sulu](https://sulu.io) 21 | - Dev stack : [Git](https://git-scm.com), [Docker](https://www.docker.com) 22 | - Usages : Designs patterns, DDD, TDD, Architecture hexagonal, Clean architecture. 23 | - Quality : Continus integration, unit testing, code review 24 | - Agility methods : Scrum, Kanban 25 | 26 | ## Blog 27 | 28 | 29 | - [⭐️ Meetup AFUP Paris Décembre 2025](https://blog.darkwood.com/article/meetup-afup-paris-decembre-2025) 30 | - [🏛️ Open Source Experience 2025: an ecosystem that is organizing itself, asserting itself and accelerating](https://blog.darkwood.com/article/open-source-experience-2025-an-ecosystem-that-is-organizing-itself-asserting-itself-and-accelerating) 31 | - [🚀 IA Pulse](https://blog.darkwood.com/article/ia-pulse) 32 | - [🧩 Meetup AFUP Paris – Novembre 2025](https://blog.darkwood.com/article/meetup-afup-paris-novembre-2025) 33 | - [🤖 AI Café Club #12: Creation, business, cinema… AI in all its forms at the Monnaie de Paris](https://blog.darkwood.com/article/ai-cafe-club-12-creation-business-cinema-ai-in-all-its-forms-at-the-monnaie-de-paris) 34 | 35 | 36 | ## Links 37 | 38 |

39 | darkwood 40 | email 41 | twitter 42 | linkedin 43 | discord 44 |

45 | 46 |

47 | visitor badge 48 |

49 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, caste, color, religion, or sexual identity 10 | and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or 31 | advances of any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email 35 | address, without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | mathieu@darkwood.fr. 64 | All complaints will be reviewed and investigated promptly and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Enforcement Guidelines 70 | 71 | Community leaders will follow these Community Impact Guidelines in determining 72 | the consequences for any action they deem in violation of this Code of Conduct: 73 | 74 | ### 1. Correction 75 | 76 | **Community Impact**: Use of inappropriate language or other behavior deemed 77 | unprofessional or unwelcome in the community. 78 | 79 | **Consequence**: A private, written warning from community leaders, providing 80 | clarity around the nature of the violation and an explanation of why the 81 | behavior was inappropriate. A public apology may be requested. 82 | 83 | ### 2. Warning 84 | 85 | **Community Impact**: A violation through a single incident or series 86 | of actions. 87 | 88 | **Consequence**: A warning with consequences for continued behavior. No 89 | interaction with the people involved, including unsolicited interaction with 90 | those enforcing the Code of Conduct, for a specified period of time. This 91 | includes avoiding interactions in community spaces as well as external channels 92 | like social media. Violating these terms may lead to a temporary or 93 | permanent ban. 94 | 95 | ### 3. Temporary Ban 96 | 97 | **Community Impact**: A serious violation of community standards, including 98 | sustained inappropriate behavior. 99 | 100 | **Consequence**: A temporary ban from any sort of interaction or public 101 | communication with the community for a specified period of time. No public or 102 | private interaction with the people involved, including unsolicited interaction 103 | with those enforcing the Code of Conduct, is allowed during this period. 104 | Violating these terms may lead to a permanent ban. 105 | 106 | ### 4. Permanent Ban 107 | 108 | **Community Impact**: Demonstrating a pattern of violation of community 109 | standards, including sustained inappropriate behavior, harassment of an 110 | individual, or aggression toward or disparagement of classes of individuals. 111 | 112 | **Consequence**: A permanent ban from any sort of public interaction within 113 | the community. 114 | 115 | ## Attribution 116 | 117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 118 | version 2.1, available at 119 | [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. 120 | 121 | Community Impact Guidelines were inspired by 122 | [Mozilla's code of conduct enforcement ladder][Mozilla CoC]. 123 | 124 | For answers to common questions about this code of conduct, see the FAQ at 125 | [https://www.contributor-covenant.org/faq][FAQ]. Translations are available 126 | at [https://www.contributor-covenant.org/translations][translations]. 127 | 128 | [homepage]: https://www.contributor-covenant.org 129 | [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html 130 | [Mozilla CoC]: https://github.com/mozilla/diversity 131 | [FAQ]: https://www.contributor-covenant.org/faq 132 | [translations]: https://www.contributor-covenant.org/translations 133 | --------------------------------------------------------------------------------