Zigorat website

This is the source for the main Zigorat company website, found at zigorat.co.

TEAM (1Devs Web Department)

• Mohammad Sedaghat sedaghat Project Manager
• Ali Mihandoost AliMD Technical Manager / Developer
• Ali aGHasizadeh AliGH Developer / Programmer
• Mohammad Reza Shariatzadeh Mrshcom Developer / Programmer
• Mohammad Rahimpour Rahimpour Graphic Designer

THANKS (Contributors)

• Aida Naderi ainaderi
• Naser Rahmani naserr
• Ali Abdollahi aliab

TECHNOLOGY

• HTML5
• CSS3
• 1Styles
• JavaScript
• Zepto.js
• jQuery.js
• html5shiv
• PHP
• MySQL

Change Log

HEAD (now)

• Fix some bugs.
• Cross browser compatibility.
• View full changes

v1.0rc1 (12/1/2012)

• Fix some bugs.
• Dynamic our-oustomers page.
• Dynamic Home and last project.
• Add iE2wall Technology.
• View full changes

v0.9 (11/27/2012)

• Products category.
• Preview.
• View full changes

v0.8 (11/21/2012)

• Ready to publish.
• View full changes

v0.7 (11/21/2012)

• Dynamic content with admin pannel.
• View full changes

v0.6 (11/20/2012)

• Better Architecture.
• View full changes

v0.5 (11/13/2012)

• Pages Complete.
• View full changes

v0.4 (11/10/2012)

• Better team managing.
• Better codding.
• View full changes

v0.3 (09/06/2012)

• Keep forward.
• View full changes

v0.2 (08/11/2012)

• Change team for better codding.
• View full changes

v0.1 (07/23/2012)

• Amature codes
• View full changes

Contributing

♥ Zigorat website and want to get involved ?
Thanks! There are plenty of ways you can help!

Report issues

Check project and report your issue here

1. Report your Idea
   If you have a any idea about design, programming, technology and other, please open an issue.

2. Ask any question
   If you're one of my students and want to upgrade your skills, you can ask any question.

3. Bug report
   Please try to be as detailed as possible in your report. What is your environment? What steps will reproduce the issue? What browser(s) and OS experience the problem? What would you expect to be the outcome? All these details will help people to assess and fix any potential bugs.

Pull requests

Good pull requests — patches, improvements, new features — are a fantastic help. They should remain focused in scope and avoid containing unrelated commits.

If your contribution involves a significant amount of work or substantial changes to any part of the project, please open an issue to discuss it first.

Please follow this process; it's the best way to get your work included in the project:

1. Fork the project.

2. Clone your fork (git clone https://github.com/<your-username>/zigorat.git).

3. Add an upstream remote (git remote add upstream https://github.com/AliMD/zigorat.git).

4. Get the latest changes from upstream (e.g. `git pull upstream

   `).

5. Create a new topic branch to contain your feature, change, or fix (git checkout -b <topic-branch-name>).

6. Make sure that your changes adhere to the current coding conventions used throughout the project - indentation, accurate comments, etc. Please update any documentation that is relevant to the change you are making.

7. Commit your changes in logical chunks; use git's interactive rebase feature to tidy up your commits before making them public. Please adhere to these git commit message guidelines or your pull request is unlikely be merged into the main project.

8. Locally merge (or rebase) the upstream branch into your topic branch.

9. Push your topic branch up to your fork (`git push origin

   `).

10. Open a Pull Request with a clear title and description. Please mention which browsers you tested in.

All rights reserved

Please note that zigorat.co is a curated site and that we reserve the right to refuse any listing for any reason.

The zigorat.co source code is released under MIT License.

A 1Devs Website

Produced by TheOneDevelopers - Web Department