This question is not as much on CakePHP as it is on a workflow.
If this goes too far out of the scope of this forum, then please let me know.
So here’s the deal.
We have 3 teams in our company:
- front-end developers
- full-stack developers (yes, oddly enough, we do not have specialized back-end developers).
Now let’s say ACMECorp comes in and wants a website.
Our project managers go sit around the table with them and work out the site (the first version).
Project managers inform all the teams, and they get to work.
The designers build a design (in something like Photoshop) and hand this the front-end developers.
One they are done, they hand it over to the full-stack developers…
And this is where we lose a lot of our time.
We don’t really have a decent hand-over procedure for this.
Currently it’s just that the front-end developers hand it over and the full-stack developers copy paste everything into the CakePHP app and integrate it with the back-end code they have written.
To make matters worse, once the first version has finished, we hand it over to the customer, and often, the customer wants something extra.
who now have to look for everything that has changed and manually copy-paste this into the CakePHP app again, which is highly inefficient!
My question is, how can we do this better, without using stuff like Angular or React combined RESTful API’s…
The designs the full-stack developers get are in the following structure (roughly):
/ ├── css/ │ ├── bootstrap.min.css │ └── acmecorp.min.css ├── js/ │ ├── bootstrap.min.js │ └── acmecorp.min.js ├── img/ │ └── whatever.png ├── index.html ├── about.html └── blog.html
This ofc has to be turned into CakePHP workable-views… which is currently done by hand since this can’t really be done using a simple git pull request…
I hope someone here can enlighten me