👋 Hi @TheNova22,

I am your GitHub mentor for the GitHub Education, Community Exchange (CX) project. I'll be collaborating with you on preparing your repo for CX.

You mentioned in your submission that you wanted to submit a Learn + Collaborate repo. This means that you would like to teach students, step by step, how to build this project as well as invite other students to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for a Learn + Collaborate CX submission on June 1, 2022.

This issue will serve as a tracking issue to track all issues related to CX. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.

If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.

I look forward to working with you! :octocat:

CX Issues:

• [x] https://github.com/TheNova22/tkArt/issues/2
• [x] https://github.com/TheNova22/tkArt/issues/3
• [x] https://github.com/TheNova22/tkArt/issues/4
• [x] https://github.com/TheNova22/tkArt/issues/5
• [x] https://github.com/TheNova22/tkArt/issues/6
• [x] https://github.com/TheNova22/tkArt/issues/7
• [x] https://github.com/TheNova22/tkArt/issues/8

Is your feature request related to a problem? Please describe. Change color of the canvas and also inform the user on how to do it by adding it in Learn.md

Describe the solution you'd like Change the canvas colour and provide a set of options that seem to look good if possible as comment

As the maintainer of a Learn + Collaborate repo, keeping Issues up-to-date will help the student community understand what they can do to contribute. Issues should vary by the easy (update documentation) to the difficult (add a new feature). The more involved you are, the more opportunities there are to collaborate.

Recommendations:

• [ ] Add issues of varying difficulty to the repo often.
• [ ] Generate issues even if you plan on solving them, so the repository appears as active.
• [ ] Contribute/commit often to the repo so it does not go stale.

In order to submit your project into CX you will need at least one issue, but we recommend more so other students have an idea on where to start.

Is your feature related to something you want to see in this project? Please describe. A calming culmination of multiple rectangles in vertical and horizontal layers

Describe the solution you'd like Randomness + Vertical and Horizontal angled drops of constant values

Additional context

Issue templates are very helpful for a collaboration repo. When users identify a bug or want to add a new feature, you can provide templates so you can collect all the pertinent information you need to fix a bug or add a new feature.

We recommend creating a “Report Bug” and “Feature Request” issue template. Here's some documentation for a couple of ways to add templates.

Some suggested prompts/questions you can add to a “Report Bug” template are:

• Briefly describe the bug
• What is the expected behavior?
• Please provide step by step instructions on how to reproduce the bug

Some suggested prompts/questions you can add to a “Feature Request” issue template are:

• Briefly describe your feature request
• What problem is this feature trying to solve?
• How do we know when the feature is complete?

Other than GitHub Topics, your description will be the primary way of catching the users eyes. Your repo description should be clear and concise. Ask yourself:

• In one sentence, how do I convey what my repo does?
• What type of users am I interested in attracting to my repo?
• If I was a user, what words or phrases might spark my interest?

A README is often the first item a visitor will see when visiting your repository. I really like your README so far, especially how it showcases the created art and includes a section for Usage. ✨

We also recommend that your README includes information on:

• [x] How users can get started contributing to the project
  • Explain to users that there is a LEARN.md
• [x] Mention your code of conduct
• [x] Describe who maintains and who can contribute to the project

In Community Exchange, GitHub Topics will help the discoverability of your project. I recommend creating topics pertaining to:

• the tech stack you used on the project
• the subject matter of your repo
• the subject(s) covered in your LEARN.md

There is a limit of 20 topics you can add to your repo, but we recommend under 10 topics. You can add topics by following these instructions.

Learn repos should have a LEARN.md file to teach another student how you created your project step by step. You can explain how to build your project with text, code snippets, images, or even short (5 minute) long video lessons. As the maintainer of a Learn repo, the LEARN.md file requires you to think critically about how to explain the building of your project and how to also make it engaging. We don't expect you to be an expert teacher, but we would like you to reflect on how difficult it was to get to your level of knowledge, and then provide friendly guidance to help other students to learn.

If your project is very large, consider just teaching a certain tool or implementation that your project utilizes.

We recommend that every repo has a code of conduct. If you don’t feel comfortable creating your own Code of Conduct from scratch we highly recommend using one of the templates provided by GitHub. If you do use a template, please read through the template and ensure that you can and will abide by the Code of Conduct.

Please follow these instructions on how to add a Code of Conduct.

Is your feature related to something you want to see in this project? Please describe. A randomly generated two dimensional map that has patches of land all over the board while the rest is similar to water bodies

Describe the solution you'd like Generate lines and curves randomly in several regions of a canvas. This shall lead to creation of several land masses while the remaining parts of the canvas can be considered as a water body. A good example can be seen here.

Describe alternatives you've considered There is no need for the map to look similar or have any condition for water bodies.

Is your feature related to something you want to see in this project? Please describe. A neuron like design that originates from a node and continues to expand and also as it expands, it creates branches which also expands.

Describe the solution you'd like This shall start with a node(main) and then begin to increment and expand, as it shall expand, it shall generate new branches which in reality create new threads that shall run simultaneously to create a big neuron like structure. A good reference image can be found here.

Describe alternatives you've considered The figure has no necessity to look the same as long as there is random generation involved and threading is used.