Closed MicheleBertoli closed 7 years ago
On the road right now, I love that you included listing. How strict is it? We need to be as strict as humanly possible.
Maybe we should go with vanilla airbnb? That'd make it easy for most people.
Finally getting around to checking this out now, sorry for the wait! Let's kick this mofo off!
document.body
, let's choose a root node. (something unique like #example-root
) This will make creating the site with the different approaches a lot easier when we get around to that.http://mxstbr.com/headshot.jpeg
for the tweet avatar โ I changed my avatar and now the display is broken, which shouldn't happen. mxstbr.com/headshot.jpeg
will always exist ๐Other than that, the component structure and all that looks good to me!
hey @mxstbr, thanks for reviewing my PR. I'll push a new commit with the changes.
I've got just one question:
I still want to use vanilla airbnb. It's not about the whole semicolons-or-not thing, I think that it will make people more comfortable with the style if we use the vanilla one.
do you want me to remove only the "rules" or do you think it's better removing the "import/resolver" setting too?
sharing data, config and assets sounds great. I think we should merge this one first and then we can create a shared folder in a different PR, if it makes sense for you.
I think we should merge this one first and then we can create a shared folder in a different PR, if it makes sense for you.
Sure thing, sounds good to me โ let's get this done!
do you want me to remove only the "rules" or do you think it's better removing the "import/resolver" setting too?
Just the rules should be fine, I think. ๐
It should be ok now @mxstbr. Please let me know if there's something else I can do to improve it.
I like it. I say we merge it, factor out the common stuff and get onto the next one! ๐
What do you think @geelen @JedWatson?
Just realised we're including a .ejs
template without any ejs
specific stuff. Let's rename it to index.html
, throw it in the root of the example and point HTMLWebpackPlugin
at that?
Seems more obvious for beginners.
EDIT: Doing this now, will then merge and extract common stuff!
I also don't think we need to differentiate between containers
and components
โย really, they're all components. Let's put them in the same folder in an effort to put the focus on the method of styling used!
Along the same vein, what do you think about getting rid of the resolve.root
setting? I feel like this'll only serve confuse newcomers not used to webpack, I'd much rather avoid that and have the focus be on the styling method used.
We should also add a README to all methods of styling used and explain where to find the docs and what some of the specialities and ideas are โย I can do that.
Hello everyone!
This is the first iteration on the CSS Modules example. I implemented the Tweet Card from mobile.twitter.com, using the following tweet (as agreed in #3): https://mobile.twitter.com/mxstbr/status/755481795206971392
Notes:
css-loader
from GitHub because of webpack/css-loader/pull/307postcss-modules-values
but if you think it's out of the scope we can easily remove itI hope you like it and I'm looking forward to receiving some feedback.
359px
360px
600px