Pars Engineering Company Website.
JavaScript PHP CSS
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
admin
app
backup
cachetmp
err
fonts
images
inc
pages
scripts
styles
underdev
.gitignore
.htaccess
.travis.yml
CONTRIBUTING.md
README.md
favicon.ico
index.php
script.combined.js
sendmail.php
share.php
style.combined.css

README.md

ParsEngCo website

This is the source for the main ParsEngineering company website, found at parseng.co.

TEAM (1Devs Web Department)

THANKS (Contributors)

TECHNOLOGY

Performance Tests

  • Chrome, Cable, About page, Dulles, VA : AAAAA First View : 1.44s - Repeat View : 0.21s 👍
  • Chrome, DSL 1.5m, About page, Dulles, VA : AAAAA Compare First View : 2s - Repeat View : 0.5s (More Info)
  • Chrome, DSL 1.5m, About page, Dulles, VA : AAAAA First View : 2.2s - Repeat View : 0.3s (fast memory caching and gzip l6)
  • Chrome, DSL 1.5m, About page, Miami, FL : BAFAA First View : 3.5s (Unistall nginx on server)
  • Chrome, DSL 1.5m, About page, Miami, FL : CAAAA First View : 2.4s (no code changed)
  • IE9, DSL 128k, About page, Dulles, VA : CAAAA, Compare with old test (Compare changes)
  • IE9, DSL 128k, About page, Dulles, VA : BABBA, Compare First View and Repeat View (test new htaccess config)
  • Chrome, Dial 56k, About page, Miami, FL: FAC?B
  • Chrome, DSL 1.5m, Products page, Miami, FL: DABAA
  • Chrome, DSL 1.5m, Underdev page, Asheville, NC : DAAAA
  • All Pages Test history

Change Log

Build Status

HEAD (now)

v1.0 (12/08/2012)

  • Cross browser support.
  • Fast memoty caching system.
  • Optimize images size.
  • Improve page laod performance upto 0.2s.
  • Improve webpagetest site grade upto AAAAA.
  • Fixed some bugs.
  • View full changes

v1.0rc2 (11/29/2012)

  • Improved SEO.
  • Dynamic product by admin panel.
  • Dynamic categories and submenus.
  • Fix some bugs.
  • View full changes

v1.0rc1 (11/24/2012)

  • Dynamic Products and projects.
  • Search engine friendly urls.
  • Admin panel.
  • View full changes

v0.9 (11/15/2012)

v0.8 (11/14/2012)

v0.7 (11/06/2012)

v0.6 (11/05/2012)

v0.5 (10/31/2012)

v0.4 (10/20/2012)

v0.3 (10/19/2012)

v0.2 (10/13/2012)

v0.1 (10/08/2012)

Contributing

♥ ParsEngCo 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>/ParsEngCo.git).

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

  4. Get the latest changes from upstream (e.g. git pull upstream <dev-branch>).

  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 <topic-branch-name>).

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

All rights reserved

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

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

A 1Devs Website

Produced by TheOneDevelopers - Web Department