-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📚 Docs/add md docs #54
Merged
ARYAN-NIKNEZHAD
merged 9 commits into
Lazarus-org:develop
from
MEHRSHAD-MIRSHEKARY:docs/add-md-docs
Aug 30, 2024
Merged
📚 Docs/add md docs #54
ARYAN-NIKNEZHAD
merged 9 commits into
Lazarus-org:develop
from
MEHRSHAD-MIRSHEKARY:docs/add-md-docs
Aug 30, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Added index.rst file to serve as the main entry point for the documentation. - Included quick_start.rst file with initial setup and configuration instructions. - Ensured proper formatting and structure to align with Sphinx documentation standards.
- Created usage.rst file to document various usage scenarios of the django_logging package. - Included examples of basic logging, request logging middleware, and context manager usage. - Provided instructions for using the log and notify utility and the send_logs management command. - Ensured clarity and usability for developers integrating django_logging into their projects.
- Added settings.rst to document all available configuration options for django_logging. - Included descriptions for AUTO_INITIALIZATION_ENABLE, LOG_FILE_LEVELS, LOG_CONSOLE_FORMAT, and other settings. - Provided example configuration and explanations for customizing logging behavior in Django projects. - Documented available log format options and required email settings for the email notifier. - Ensured that developers have a clear reference for configuring the package to meet their specific needs.
- Added contributing.rst to provide guidelines for contributing to the django_logging project. - Included instructions for setting up the development environment, running tests, and submitting pull requests. - Outlined code style requirements, including adherence to PEP 8 and the use of proper commit messages. - Provided details on how to report issues, suggest features, and collaborate with other contributors. - Aimed to streamline the contribution process and maintain code quality across the project.
- Added rules.rst to document the rules and guidelines for using django_logging in Django projects. - Outlined the recommended practices for configuring logging levels, formats, and destinations. - Included examples of common logging scenarios and how to handle them using django_logging. - Provided guidance on maintaining consistency and clarity in log messages across the application. - Aimed to ensure that logging is effective, informative, and easy to manage within the project.
- Added conf.py to configure Sphinx for generating project documentation. - Set up project information, including project name, author, and version. - Configured Sphinx extensions, templates, and paths. - Enabled autodoc, intersphinx, and other relevant extensions for better documentation generation. - Customized HTML theme and output options for a more user-friendly appearance. - Established configurations to support future documentation expansion and maintenance.
- Added Makefile for building Sphinx documentation on Unix-based systems. - Added make.bat for building Sphinx documentation on Windows systems. - Configured both files to support common build targets such as html, latexpdf, and clean. - Enabled easy execution of documentation builds, streamlining the documentation generation process. - Facilitated cross-platform compatibility for generating project documentation.
- Updated README.md file to provide an overview of the project, its purpose, and how to get started. - Included sections on installation, configuration, and verification of django_logging. - Provided examples for adding the package to INSTALLED_APPS and running the Django server to ensure proper setup. - Added details on default logging configurations and instructions for further customization. - Included a brief conclusion directing users to additional settings for more advanced configurations.
Added CHANGELOG file to provide all new changes to the project ----- Updated CONTRIBUTORS.md & LICENCE file Ensured clear documentation for whole project including Makefile and reStructureText format Closes Lazarus-org#52
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces several important documentation and contribution-related updates to the project:
README.md
: Enhanced the main documentation file with sections for installation, configuration, usage, and additional details about the project.CONTRIBUTING.md
: Provided clear guidelines for contributing to the project, including instructions for reporting issues, submitting pull requests, and coding standards.CODE_OF_CONDUCT.md
: Added a code of conduct to outline expected behavior and community guidelines.LICENSE
: Updated the project's license information.CONTRIBUTORS.md
: updated list of contributors to acknowledge those who have contributed to the project.These updates aim to improve the clarity of project documentation.