π» Code in any programming language using your native written βοΈlanguage.
Programming with Legesher's dev tools empowers any developer to create without losing the art of innovation π‘, creativity π¨, or collaboration π€ in translation.
legesher-dot-io π³ is the public facing website to showcase our developer tools for interchanging the written language within your code. This is currently in the beta version for the website, and currently looking to revamp for version 1.0.0 of Legesher.
β€οΈLegesher relies on the passionate members of its community (both developer and non-developer alike) to keep delivering impactful tools to people all over the world.
Before contributing, be sure to consult Legesher's contribution guidelines and language conventions. As a member of our community, you must abide by our Code Of Conduct.
1οΈβ£ Fork the legesher/legesher-dot-io repository
Follow these instructions on how to fork a repository
2οΈβ£ Cloning the repository
Once you have set up your fork of the legesher/legesher-dot-io repository, you'll want to clone it to your local machine. This is so you can make and test all of your personal edits before adding it to the master version of legesher/legesher-dot-io.
Navigate to the location on your computer where you want to host your code. Once in the appropriate folder, run the following command to clone the repository to your local machine.
git clone git@github.com:your-username/legesher-dot-io.git
3οΈβ£ Bootstrapping the repository
You'll then want to navigate within the folder that was just created that contains all of the content of the forked repository. There you'll want to run the installation script to get the updated version of all the dependencies.
cd legesher-dot-io
npm install
We love your desire to give back, and want to make the process as welcoming to newcomers and experts as possible. We're working on developing more intuitive tutorials for individuals of all skill levels and expertise, so if you think the community would value from being walked through the steps you're going through please share! β€οΈ
When you start making changes to the code on your local branch, you'll need to test those changes. Before your code can be accepted into the master branch, it will have to pass all of the tests within /spec/*. To check the updates made to the grammar, run the following commands:
1οΈβ£ Save Current Changes
When you get to a point when you want to test the functionality of the code, make sure all your changes are saved. βThey don't necessarily have to be committed changes in order to test them.
2οΈβ£ Test changes
To make sure that the application is properly updated, run the tests.
npm test
Our hosting client, Zeit, will go through the necessary CI checks to make sure the build is properly set up. We want to make sure the website is mobile friendly and cross-platform enhanced.
This repository is licensed under the GNU General Public License v3.0.
Meet our community (full of contributors, backers, sponsors, and supporters) that give a little piece of their heart to this project. Thank you so much. (emoji key)
This project follows the all-contributors specification. Contributions of any kind are welcome and recognized. β¨