Boilerplate about postcss.org HOT 26 CLOSED

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.

from postcss.org.

Do not forget about all: initial and postcss-autoreset. Global reset and inherited properties is a problem too.

from postcss.org.

I can setup the boilerplate for Statinamic, that will help me review statinamic doc + enhance the setup command.
Note: Statinamic default boilerplate provides css modules.

from postcss.org.

@MoOx can we do it together/can you walk me through it? Haven't worked with Statinamic at all.

from postcss.org.

Here is a start http://moox.io/statinamic/docs/setup/
That should help.
I think I need to add more stuff based on a discussion with someone in reactiflux.
Meanwhile, if you want to try this now, feel free to ask all the question you got as Github issues in Statinamic repo for now :)

from postcss.org.

@MoOx Cheers, will take a look!

from postcss.org.

Great, feel free to override README with documentation of how to to get Statinamic up and running locally once it's up.

from postcss.org.

"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.

from postcss.org.

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.

from postcss.org.

Feel free to do it @mxstbr ;)

from postcss.org.

Agreed @mxstbr that's already set to default. PR needs to be reviewed before merged into master.

@mxstbr can you setup the initial files to master then we can go from there with setting up more files and things like PostCSS if needed.

from postcss.org.

@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.

from postcss.org.

@marcustisater will do!

@MoOx thanks, if I run into problems I'll submit issues!

from postcss.org.

Very initial setup done, will take a deeper look tomorrow!

from postcss.org.

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.

from postcss.org.

Can someone double check this for me #16? Thanks.

from postcss.org.

Need a better webpack config maybe

from postcss.org.

I think I will include postcss-cssnext in the default boilerplate but that won't be good for everybody.
Anyway, that's the power of statinamic: you define what you want/need.
Here is an example of another config https://github.com/putaindecode/putaindecode.io/blob/master/scripts/build.js

from postcss.org.

Discussion from the meeting is to get the boilerplate ready before #12 is completed and also provide more documentation - #28

from postcss.org.

I think it makes sense to separate available layouts (e.g. Page, PageError,...) from more general React components (e.g. Button, Footer,...) by putting them in a separate folder.

I suggest we call the folder web_modules/pages for the layouts and web_modules/components for more general components.

routes was another option I was thinking about, but I'm pretty sure for beginners the connection between the URL and the component is clearer if the folder is called pages.

Thoughts? (Maybe worth including that separation in the official boilerplate @MoOx?)

from postcss.org.

What about this (I use it on a website and I like it)

• web_modules/* for components
• web_modules/layouts/* for layouts components ?

from postcss.org.

👍 I like it!

from postcss.org.

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.

from postcss.org.

Yup, sounds good. Nice work.

from postcss.org.

Merged?

from postcss.org.

Oh yeah sorry, forgot to close the Issue!

from postcss.org.