Comments (6)
or do we go with two separate repos? one for back end and one for frontend?
from generator-jam3.
I think separate repos makes more sense, probably won't be much code sharing
Also, scope creep!
from generator-jam3.
Not scope creep. 😁 It's a part of the long term plan. We've already been discussing backends and cmses that would work well with our workflow.
from generator-jam3.
Maybe we could have 2 generators: generator-jam3-frontend and generator-jam3-backend. In case you need both for the same project, you can create:
|-project-name/
|-- frontend
|-- backend
And then run the proper generator in each folder. With this maybe we loose the opportunity to have more advanced commands like yo jam3:update interacting with both projects at the same time. Maybe not. I'm not sure.
In the other hand, I think we should let this for phase 3 or 4 of the generator and just focus on front end at this point.
from generator-jam3.
I'm not sure separating the backend and frontend is a good route. By repo or by generator.
The holy grail of Node is to be able to use frontend code on the backend and backend code on the frontend.
One case where I've done thing many times is where I've setup a socket.io server and had an Object which stores all the "keys" for events in an Object. Like:
module.exports = {
CHARACHTER_MOVED: 'charMoved'
}
On the frontend I'll listen for for events.CHARACHTER_MOVE
and on the server I'll emit events.CHARACHTER_MOVE
.
The game plan with the backend is to mirror the way we work with routes.
So if we have a section and route such as /about
then the backend would also have an /about
route you could call and get a JSON model for that section.
from generator-jam3.
Look into using salt for bringing in the latest php backends, look for a way to standardize backend code.
from generator-jam3.
Related Issues (20)
- Optimize inline SVGs
- Load polyfills only when needed
- Move browserlist to package.json
- Move CSS compressing to cssnano HOT 1
- To use yarn HOT 2
- Proposal: Remove stats.js HOT 2
- React doesn't appear as prod mode
- Robot.txt addition
- Installing from source HOT 4
- Remove LESS
- Remove BigWheel
- Update to React 16 and React Router 4 HOT 1
- Create scripts to create component, stateless-component & section templates
- Remove Password Protection Question (Auto include password protection)
- Add npm package vulnerability check
- Remove "Would you perfer Landing/Landing.js over Landing/index.js?" HOT 1
- Remove "Use push states?"
- Remove "Would you like to use ES6?"
- Add default CSS breakpoints HOT 1
- Ensure all current functionality is working correctly
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from generator-jam3.