diff --git a/README.md b/README.md index 595390d..8652b94 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,4 @@ +

Conway's Game of Life

A cellular automaton devised by British mathematician John Horton Conway in 1970.

@@ -46,8 +47,10 @@ --- -## Table of Contents +
+

:pushpin:Table of Contents:

 + 1. [What is it?](#what-is-it) 1. [The Universe](#the-universe) 2. [The Rules](#the-rules) @@ -68,8 +71,10 @@ 10. [Pentadecathlon](#pentadecathlon) 6. [Feedback](#feedback) 7. [Resources](#resources) + +
+
---- ## What is it? ✨ Conway's Game of Life, or simply "Life," is a cellular automaton devised by British mathematician John Horton Conway in 1970. It is a zero-player game, meaning its evolution is determined by its initial state, requiring no further input. Players interact with the game by creating an initial configuration and observing how it evolves. The game is Turing complete and can simulate a universal constructor or any other Turing machine. @@ -92,7 +97,11 @@ The first generation is created by applying the above rules simultaneously to ev --- -## The Game + +
+

🎮The Game

 + + ### The Canvas / Grid @@ -162,9 +171,12 @@ The first generation is created by applying the above rules simultaneously to ev Stores history of patterns that user has played with, up to 5 recent patterns. ---- +
+ +
-## The Presets +
+

✨The Presets

### Glider @@ -257,11 +269,12 @@ The Pentadecathlon is a period-15 oscillator that was found in 1970 by John Conw Pentadecathlon
- ### More Configurations Explore more patterns at [ConwayLife Patterns](https://conwaylife.com/wiki/Category:Patterns). + + --- ## Feedback - 💬 Now the page supports user feedback. Which redirects you to a Feedback.html page. @@ -293,6 +306,28 @@ Explore more patterns at [ConwayLife Patterns](https://conwaylife.com/wiki/Categ +
+ + + +
+

⚡Contribution Guidelines:

 + + + * **Checkout and make your changes for the develop branch only:** When working on your contributions, switch to the **develop** branch in your local repository. This ensures that you are working on the latest version of the codebase. + +* **Create pull requests only for the develop branch:** When you are ready to submit your changes, create a pull request (PR) targeting the **develop** branch. This allows the maintainers to review and merge your code into the main development branch. + +* **Format your commit message with the issue number:** When making commits related to an issue, follow the format **Fixes: #32 in your commit message. Replace 32 with the issue number you are addressing.** This helps track and manage issues more efficiently. + +* **Make your pull request descriptive and include examples:** When creating a pull request, provide a clear and descriptive explanation of the changes you made. This helps reviewers understand the purpose and significance of your contribution. Additionally, including at least one example that demonstrates the intended usage or effect of your changes can be beneficial. + +* **Rebase your commits and optimize file changes:** When submitting your pull request, consider rebasing your commits into one commit and optimizing your file changes. This helps keep the commit history clean and makes it easier for reviewers to understand your changes. + +Remember, following these guidelines will help ensure a smooth and efficient contribution process. Happy coding! + +
+
@@ -331,3 +366,14 @@ Thank you for contributing to our project! Your help is greatly appreciated in m + +
+
+

Support

+
+ +
+ Don't forget to leave a star for this project! +

+ +Go to Top