docs: Updated documentations and version

Signed-off-by: Yash Pandey (YP) <[email protected]>

Author: EmperorYP7

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,11 @@
+### Description
+
+
+
+### Your System Info
+
+<!-- *Optional -->
+
+### Screenshots/Testimonials
+
+<!-- *Optional -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,18 @@
+<!--
+    We follow semantic pull requests. Make sure you sign-off and format every commit message
+    as well as the PR title as specified in 
+    https://github.com/commitizen/conventional-commit-types/blob/master/index.json
+
+    Eg. feat: New feature name,
+    fix: Some error, etc.
+-->
+
+## Fixes # <Enter the issue number>
+
+### Description
+
+
+
+### Screenshots/Testimonials
+
+

CMakeLists.txt

@@ -20,7 +20,7 @@ set(CMAKE_MODULE_PATH
 )
 
 set(CMAKE_WARN_DEPRECATED ON)
-set(PY_CASBIN_VERSION 1.0)
+set(PY_CASBIN_VERSION 1.1)
 
 if(APPLE AND NOT DEFINED CMAKE_OSX_DEPLOYMENT_TARGET)
     # The value of this variable should be set prior to the first project() command invocation
@@ -32,7 +32,7 @@ endif()
 # Project definition.
 
 project(CasbinCPP
-    VERSION 1.37.0
+    VERSION 1.38.2
     DESCRIPTION "An authorization library that supports access control models like ACL, RBAC, ABAC in C/C++"
     HOMEPAGE_URL https://github.com/casbin/casbin-cpp
     LANGUAGES CXX C

CONTRIBUTING.md

@@ -35,3 +35,8 @@ Good pull requests (e.g. patches, improvements, new features) are a fantastic he
 Please ask first before embarking on any significant pull request (e.g. implementing new features, refactoring code etc.), otherwise you risk spending a lot of time working on something that the maintainers might not want to merge into the project.
 
 First add an issue to the project to discuss the improvement. Please adhere to the coding conventions used throughout the project. If in doubt, consult the [Google C++ Style Guide](https://google.github.io/styleguide/cppguide.html).
+
+We follow semantic pull requests. Make sure you sign-off and format every commit message
+as well as the PR title as specified in [conventional-commit-types](https://github.com/commitizen/conventional-commit-types/blob/master/index.json).
+
+Eg. `feat: New feature name`, `fix: Some error`, etc.

README.md

@@ -15,8 +15,11 @@ Windows (VS C++)  | :heavy_check_mark: Available
 Linux   | :heavy_check_mark: Available
 macOS   | :heavy_check_mark: Available
 
+<br/>
 
-![casbin Logo](casbin-logo.png)
+![casbin Logo](./assets/images/casbin-logo.png)
+
+<br/>
 
 ## All the languages supported by Casbin:
 
@@ -108,6 +111,56 @@ You can also use the online editor (https://casbin.org/editor/) to write your Ca
 
 https://casbin.org/docs/en/tutorials
 
+## Integrating Casbin to your project through CMake
+
+Here is a [working project](https://github.com/EmperorYP7/casbin-CMake-setup) to demonstarte how to set up your CMake
+configurations to integrate casbin.
+
+You may integrate casbin into your CMake project through `find_package`. **It is assumed that you're using CMake >= v3.19.**
+
+You must have casbin installed on your system OR have it fetched from GitHub through [FetchContent](https://cmake.org/cmake/help/latest/module/FetchContent.html).
+
+Here's what your Findcasbin.cmake file should be:
+```cmake
+include(FetchContent)
+
+FetchContent_Declare(
+        casbin
+        GIT_REPOSITORY https://github.com/casbin/casbin-cpp.git
+        GIT_TAG v1.38.1
+)
+
+set(CASBIN_BUILD_TEST OFF)            # If you don't need to build tests for casbin
+set(CASBIN_BUILD_BENCHMARK OFF)       # If you don't need to build benchmarks for casbin
+set(CASBIN_BUILD_BINDINGS OFF)        # If you don't need language bindings provided by casbin
+set(CASBIN_BUILD_PYTHON_BINDINGS OFF) # If you don't need python bindings provided by casbin
+
+# Making casbin and its targets accessible to our project
+FetchContent_MakeAvailable(casbin)
+
+FetchContent_GetProperties(casbin)
+
+# If casbin wasn't populated, then manually populate it
+if(NOT casbin_POPULATED)
+    FetchContent_Populate(casbin)
+    add_subdirectory(${casbin_SOURCE_DIR} ${casbin_BINARY_DIR})
+endif()
+```
+
+Now that casbin's targets are available to your project,
+your may link your own targets against casbin's likewise:
+
+```cmake
+add_executable(myexec main.cpp)
+
+target_link_libraries(myexec PRIVATE casbin)
+
+set(myexec_INCLUDE_DIR ${casbin_SOURCE_DIR}/include)
+target_include_directories(myexec PRIVATE ${myexec_INCLUDE_DIR})
+```
+
+Do remember to include `casbin_SOURCE_DIR/include` directory wherever casbin's functions are utilised.
+
 ## Installation and Set-Up
 
 ### Build instructions for all platforms
@@ -162,7 +215,7 @@ https://casbin.org/docs/en/tutorials
     #include <casbin/casbin.h>
     ```
 
-2. New a Casbin enforcer with a model file and a policy file:
+2. Make a new a `casbin::Enforcer` with a model file and a policy file:
 
     ```cpp
     casbin::Enforcer e("./path/to/model.conf", "./path/to/policy.csv");