script47 / panther Goto Github PK

A code standard should be applied so that the code base maintains consistent, this includes Comments, file naming, structuring, tabs vs spaces, etc.

At least some general guidelines.

I would suggest using tags instead of having all releases of Panther in the master branch folder. That is the real way of making releases on Github.

Look at https://help.github.com/articles/creating-releases

Known bug where you have to click logout a couple of times before it works.

In my opinion the folder structure of Panther is inconsistent. Here's an alternative.

./public
  ./index.php
  ./assets
    ./css
    ./js
    ./img
./config
  config.php
  config.development.php
./modules
  ./register
    ./main.php
./lib
./templates
./files
./installer
./core
  ./functions.php
  ./init.php
  ./libs/
   ./config.class.php
   ./template.class.php

• Update password hashing
• Migrate to PDO
• Objectify the base source
• Normalise / rework the database
• Standardise the code base
• CSRF
• Boostrap 4+ / Materialize

I would suggest that we use a encoding completely throughout the engine to make sure we don't run in to any encoding/collation problems.

UTF-8 is usually a good bet. However the main cause is to keep the engine consistent.

You should use branches and tags to get a better structure on the repository.

I would suggest that you adopt a semantic version approach. This approach are used by many popular frameworks and libraries.

MAJOR.MINOR.PATCH
Take a look at http://semver.org/

Branches:

master - The most recent stable version
develop - The branch you are developing next release on

Tags:
x.x.x

Until you have a first release (1.0.0) I would simply use the develop branch and then push in to the master and call it the day. When you release 1.0.1, I would tag 1.0.0 and move 1.0.1 to master branch from develop.