fix: Update personalized files and correct bug on cookiecutter installer

Author: eocode

cookiecutter.json

@@ -2,10 +2,10 @@
   "full_name": "Hello World",
   "email": "[email protected]",
   "github_username": "activandoideas",
-  "author_name": "{{cookiecutter.github_username}}",
+  "author_name": "{{cookiecutter.full_name}} | @{{cookiecutter.github_username}}",
   "project_name": "",
-  "version": "0.1.0",
   "project_slug": "{{cookiecutter.project_name.lower().replace(' ', '_').replace('-', '_')}}",
   "description": "{{cookiecutter.project_name}}",
+  "version": "0.1.0",
   "open_source_license": ["MIT license", "BSD license", "ISC license", "Apache Software License 2.0", "GNU General Public License v3", "Not open source"]
 }

hooks/post_gen_project.py

@@ -1,4 +1,3 @@
-#!/usr/bin/env python
 import os
 
 PROJECT_DIRECTORY = os.path.realpath(os.path.curdir)
@@ -10,9 +9,7 @@ def remove_file(filepath):
 
 if __name__ == '__main__':
 
-    if '{{ cookiecutter.create_author_file }}' != 'y':
-        remove_file('AUTHORS.rst')
-        remove_file('docs/authors.rst')
-
     if 'Not open source' == '{{ cookiecutter.open_source_license }}':
-        remove_file('LICENSE')
+        remove_file('LICENSE')
+
+    remove_file('MANIFEST.in')

{{cookiecutter.project_slug}}/AUTHORS.md

@@ -6,7 +6,7 @@
 
 # Development Lead
 
-* {{ cookiecutter.full_name }} <{{ cookiecutter.email }}>
+* {{ cookiecutter.author_name }} <{{ cookiecutter.email }}>
 
 # Contributors
 

{{cookiecutter.project_slug}}/CONTRIBUTTING.md

@@ -1,91 +1,84 @@
 # Contributing
 
-Contributions are welcome, and they are greatly appreciated! Every little bit
-helps, and credit will always be given.
-
-You can contribute in many ways:
+Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given. You can contribute in many ways:
 
 ## Types of Contributions
 
 ### Report Bugs
 
-```txt
-Report bugs at https://github.com/{{ cookiecutter.github_username }}/{{ cookiecutter.project_slug }}/issues.
-
-If you are reporting a bug, please include:
-
-* Your operating system name and version.
-* Any details about your local setup that might be helpful in troubleshooting.
-* Detailed steps to reproduce the bug.
-```
+> ---
+> Report bugs at https://github.com/{{ cookiecutter.github_username }}/{{ cookiecutter.project_slug }}/issues.
+>
+>If you are reporting a bug, please include:
+>
+> * Your operating system name and version.
+> * Any details about your local setup that might be helpful in  troubleshooting.
+> Detailed steps to reproduce the bug.
+> 
+> ---
 
 ### Fix Bugs
 
-```txt
-Look through the GitHub issues for bugs. Anything tagged with "bug" and "help
-wanted" is open to whoever wants to implement it.
+> ---
+> Look through the GitHub issues for bugs. Anything tagged with "bug" and "help
+> wanted" is open to whoever wants to implement it.
+> 
+> ---
 
-Implement Features
-```
+### Implement Features
 
-Look through the GitHub issues for features. Anything tagged with "enhancement"
-and "help wanted" is open to whoever wants to implement it.
+> ---
+> Look through the GitHub issues for features. Anything tagged with "enhancement"
+> and "help wanted" is open to whoever wants to implement it.
+>
+> ---
 
 ### Write Documentation
 
-```txt
-{{ cookiecutter.project_name }} could always use more documentation, whether as part of the
-official {{ cookiecutter.project_name }} docs, in docstrings, or even on the web in blog posts,
-articles, and such.
-```
+> ---
+> Personal Site could always use more documentation, whether as part of the
+> official Personal Site docs, in docstrings, or even on the web in blog posts, articles, and such.
+> 
+> ---
 
 ### Submit Feedback
 
-```txt
-The best way to send feedback is to file an issue at https://github.com/{{ cookiecutter.github_username }}/{{ cookiecutter.project_slug }}/issues.
-If you are proposing a feature:
-
-* Explain in detail how it would work.
-* Keep the scope as narrow as possible, to make it easier to implement.
-* Remember that this is a volunteer-driven project, and that contributions
+> ---
+> The best way to send feedback is to file an issue at https://github.com/{{ cookiecutter.github_username }}/{{ cookiecutter.project_slug }}/issues.
+> If you are proposing a feature:
+> 
+> * Explain in detail how it would work.
+> * Keep the scope as narrow as possible, to make it easier to implement.
+> * Remember that this is a volunteer-driven project, and that contributions
   are welcome :)
-```
+> ---
 
 ### Get Started!
 
-Ready to contribute? Here's how to set up `{{ cookiecutter.project_slug }}` for local development.
+Ready to contribute? Here's how to set up `personal_site` for local development.
 
-1. Fork the `{{ cookiecutter.project_slug }}` repo on GitHub.
+1. Fork the `personal_site` repo on GitHub.
 2. Clone your fork locally::
 
-    $ git clone [email protected]:your_name_here/{{ cookiecutter.project_slug }}.git
+`$ git clone [email protected]:{{ cookiecutter.github_username }}/{{ cookiecutter.project_slug }}.git
 
 3. Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development::
 
-    $ mkvirtualenv {{ cookiecutter.project_slug }}
-    $ cd {{ cookiecutter.project_slug }}/
-    $ python setup.py develop
-
 4. Create a branch for local development::
 
-    $ git checkout -b name-of-your-bugfix-or-feature
-
-   Now you can make your changes locally.
+`git checkout -b name-of-your-bugfix-or-feature`
 
-5. When you're done making changes, check that your changes pass flake8 and the
-   tests, including testing other Python versions with tox::
+Now you can make your changes locally.
 
-    $ flake8 {{ cookiecutter.project_slug }} tests
-    $ python setup.py test or pytest
-    $ tox
-
-   To get flake8 and tox, just pip install them into your virtualenv.
+5. When you're done making changes, check that your changes pass linters and tests
 
 6. Commit your changes and push your branch to GitHub::
 
-    $ git add .
-    $ git commit -m "Your detailed description of your changes."
-    $ git push origin name-of-your-bugfix-or-feature
+```
+    git add .
+    git commit -m "Your detailed description of your changes."
+    git push origin name-of-your-bugfix-or-feature
+```
 
 7. Submit a pull request through the GitHub website.
 
@@ -97,18 +90,20 @@ Before you submit a pull request, check that it meets these guidelines:
 2. If the pull request adds functionality, the docs should be updated. Put
    your new functionality into a function with a docstring, and add the
    feature to the list in README.rst.
-3. The pull request should work for Python 3.5, 3.6, 3.7 and 3.8, and for PyPy. Check
-   https://travis-ci.com/{{ cookiecutter.github_username }}/{{ cookiecutter.project_slug }}/pull_requests
+3. The pull request should work for Python 3.5, 3.6, 3.7 and 3.8. Check
+   https://travis-ci.com/eocode/personal_site/pull_requests
    and make sure that the tests pass for all supported Python versions.
 
 ### Deploying
 
 A reminder for the maintainers on how to deploy.
-Make sure all your changes are committed (including an entry in HISTORY.rst).
+Make sure all your changes are committed (including an entry in CHANGELOG.md)
+
 Then run::
 
-$ bump2version patch # possible: major / minor / patch
-$ git push
-$ git push --tags
+Describe version patch # possible: major / minor / patch
 
-Travis will then deploy to PyPI if tests pass.
+```
+git push
+git push --tags
+```

{{cookiecutter.project_slug}}/README.md

@@ -23,9 +23,9 @@ Your demo project
 
 ## How to clone
 
-You can clone the repository
+You can clone this repository
 
-    clone url
+    git clone https://github.com/{{ cookiecutter.github_username }}/{{ cookiecutter.project_slug }}
 
 ## Use on local
 To install this project just type