-
-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Boilerplate #13
Comments
Sorry, misclicked and closed the issue on accident. I'd say let's go with components + CSS modules, it's the future and PostCSS fits perfectly with it. |
Do not forget about |
I can setup the boilerplate for Statinamic, that will help me review statinamic doc + enhance the |
@MoOx can we do it together/can you walk me through it? Haven't worked with Statinamic at all. |
Here is a start http://moox.io/statinamic/docs/setup/ |
@MoOx Cheers, will take a look! |
Great, feel free to override README with documentation of how to to get Statinamic up and running locally once it's up. |
"npm start" will be enough for local usage. For "production" (build + commit to github pages - gh-pages branch) we will need to follow (once) instructions of statinamic docs to automate deploy on each commit pushed to master. I can help for that. |
Let's do that and make master protected and only be committed into via PRs for safety. If all you are going to do is the setup thing in the Statinamic docs, I can submit a PR as well. |
Feel free to do it @mxstbr ;) |
@mxstbr if you need assistance, do not hesitate to use Statinamic support (me haha). I plan to work on this project for the incoming weeks/months. |
@marcustisater will do! @MoOx thanks, if I run into problems I'll submit issues! |
Very initial setup done, will take a deeper look tomorrow! |
Do not hesitate to tell me how bad your experience was (because currently I think it's not really convenient...) and what we should improve. Feedbacks are important to me. |
Can someone double check this for me #16? Thanks. |
Need a better webpack config maybe |
I think I will include postcss-cssnext in the default boilerplate but that won't be good for everybody. |
I think it makes sense to separate available layouts (e.g. I suggest we call the folder
Thoughts? (Maybe worth including that separation in the official boilerplate @MoOx?) |
What about this (I use it on a website and I like it)
|
👍 I like it! |
When #45 is reviewed and merged, this issue can be closed as the boilerplate setup is done for now. There will highly likely be small improvements over time, but the current state is enough for beginning to work on the actual site. |
Yup, sounds good. Nice work. |
Merged? |
Oh yeah sorry, forgot to close the Issue! |
Boilerplate to be started when #8 is completed. What I mean by boilerplate is to add things like well documented and thought out structured CSS, JS before we get to building.
Should we consider to use structure like BEM or just plain up components with CSS Modules etc...
Assignee: TBA Lead Developer to help out?
The text was updated successfully, but these errors were encountered: