Lazypig is an under development super web framework for Crystal lang. Stay Tuned.
Table of contents
- Issue Template
- Pull Requests
Section about the description of the project. Also common usage goes here.
This is the section of installation intructions. If is possible use more than one way.
First way to install.
Second way to install.
Some instructions to use the software. It preferred to have a link to project documentation own site.
This is the examples section.
More examples. This section is for external links of examples.
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
You may contribute in several ways like creating new features, fixing bugs, improving documentation and examples.
name: Bug report
about: Create a report to help us improve
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. MACOS]
- Browser [e.g. chrome, safari]
- Version of Software or Programming Language [e.g. Crystal 0.27.0]
Additional context Add any other context about the problem here.
name: Feature request
about: Suggest an idea for this project
Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like A clear and concise description of what you want to happen.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.
Description of the Change
We must be able to understand the design of your change from this description. If we can't get a good idea of what the code will be doing from the description here, the pull request may be closed at the maintainers' discretion. Keep in mind that the maintainer reviewing this PR may not be familiar with or have worked with the code here recently, so please walk us through the concepts.
Explain what other alternates were considered and why the proposed version was selected
What benefits will be realized by the code change?
What are the possible side-effects or negative impacts of the code change?
New members are welcome if they have the same philosophy with the organization.
MIT - Free Software for Everyone.