I think it would be great, wouldn't it?

type: Markdown error
URL where error exists: https://reactfaq.site/
specific place: Additional information to start with section
Sorry but screenshot is not uploading so I can't provide you that
but the links are not transpiled properly and raw markdown is showing there.

Zero config starter kit - this is what FAQ calls "How do I create a new React project?". I believe zero config is the main feature, there are a lot of other template projects from which you can start react app.

I would add one more option: next.js

What if I want SASS or LESS or CSSModules with CRA: custom-react-scripts or eject

What if I want custom build of bootstrap or foundation with CRA: see or eject

*When ejecting make it in sepparate commit, so you can undo easily

PS. thanks for FAQ

I have no final opinion on this question. Will just list my thoughts on subject.

In section "What about styling things in React?" default option is CSS in JS. I see where it goes it is hype technology. But there are definitely downsides.

Overhead:

• memory: css in js will leave in JS memory
• parser: JS parser have enough to parse already with 100kb JS pages. It will parse JS and then render CSS (or set Inline styles of element?).

Dan Abramov recommends styled-components for CSS in JS. He also says that plain old CSS is good option too. styled-components supports theming and maybe will support Server Side Rendering.

Good articles on other than CSS in JS options:

• http://andrewhfarmer.com/how-to-style-react/
• http://andrewhfarmer.com/css-modules-by-example/

Hey there! 👋

First of all, I love this site. You've put together an awesome resource! 💜

I noticed a little CSS issue: the <summary> arrow marker in the <details> element at the bottom of your homepage (Beginning with "Additional information to start with...") does not display at all in Firefox (specifically, v 51.01). As a result, in Firefox it looks like the content is a cut-off sentence, rather than a collapsible element with additional hidden info.

The cause of the missing arrow appears to be related to the way Firefox handles <details> elements. From the Mozilla Developer Network:

For cross browser compatible styling hide Firefox's marker by setting summary { display: block }

There's a style rule being added (probably as part of a CSS reset?) that sets all <summary> elements to display: block, which hides the little arrow marker in Firefox. So removing or overriding the display rule for that particular element should fix the issue!

Thanks! Please let me know if you have any questions or concerns.

Best,
Jen

Q. How should I make Ajax requests in React?

Link to

http://andrewhfarmer.com/react-ajax-best-practices
http://mediatemple.net/blog/tips/loading-and-using-external-data-in-react/

Others you may know of ....

https://reactfaq.site NOT WORKING

Upper top level Menu items navigation are not apparent and does not look like primary navigation when i first visited the site.

We can change the color to more darker and closer to each other to make it feel like those are primary navigation

https://voice.kadira.io/react-storybooks-meets-create-react-app-ac8a3f32cc79