Adding tech stack documentation to allow anyone to easily see what is being used in this repo without digging through config files. Two files are being added: techstack.yml and techstack.md. techstack.yml contains data on all the technologies being used in this repo. techstack.md is a visualization of the YML file and displays the tech stack data in a pretty Markdown file.
š” Protip: techstack.md contains a comment at the top of the file that the following README snippet (with and without the logos) at the top of the file as a comment:
<--- Readme.md Snippet without images Start --->
Tech Stack
Clivern/Imap is built on the following main stack:
## Tech Stack
Clivern/Imap is built on the following main stack:
- [PHP](http://www.php.net/) ā Languages
- [PHPUnit](https://phpunit.de/) ā Testing Frameworks
- [Travis CI](http://travis-ci.com/) ā Continuous Integration
Full tech stack [here](/techstack.md)
<--- Readme.md Snippet with images Start --->
Tech Stack
Clivern/Imap is built on the following main stack:
Adding tech stack documentation to allow anyone to easily see what is being used in this repo without digging through config files. Two files are being added:
techstack.yml
andtechstack.md
.techstack.yml
contains data on all the technologies being used in this repo.techstack.md
is a visualization of the YML file and displays the tech stack data in a pretty Markdown file.š” Protip:
techstack.md
contains a comment at the top of the file that the following README snippet (with and without the logos) at the top of the file as a comment:<--- Readme.md Snippet without images Start --->
Tech Stack
Clivern/Imap is built on the following main stack:
Full tech stack here
<--- Readme.md Snippet without images End --->
Get the code:
<--- Readme.md Snippet with images Start --->
Tech Stack
Clivern/Imap is built on the following main stack:
Full tech stack here
<--- Readme.md Snippet with images End --->
Get the code: