cerebral-legacy / cerebral-website Goto Github PK
View Code? Open in Web Editor NEWCerebral website
Home Page: http://cerebral-website.herokuapp.com
Cerebral website
Home Page: http://cerebral-website.herokuapp.com
The instructions for the tutorials say to go to localhost:8080 in your browser to view the application. It seems to actually be running at localhost:3000
To me it's always very helpful to look a frameworks recommended folder structure before reading about whats what. It's an easy way to get an overview of the bits an pieces. When you then later read about them you will already know where it sits in your project :)
Hope this makes sense - I had a bear or two before I took this note.
Refer to cerebral/cerebral#131
So maybe we could make a default rule:
"Never pass props into a Cerebral component. Use signals to trigger state changes and extract state from state store. Only pass props to stateless components"
So then you have statefulcomponents, which gets their props from Cerebral. And then you have stateles components which gets their props from parents
nice separation
Would be cool to have a diagram that explains the cerebral application flow:
State -> View -> Event -> Signal -> Action Chain -> State/Side effects
It opens the same site in a new tab.
Minimum: point it to https://github.com/cerebral/cerebral-website/tree/master/app/markdown
Maximum: point to current article markdown file on on github
PR are welcome
// We just add the chains that puts the application in
// "messagesOpened" state
messageOpened: [...messagesOpened, ...messageOpened]
and
When the user goes to /messages/123 the messagesOpened and messageOpened chain will run.
looks a little strange to me.
At least it's hard to reason about ;)
Not even sure how big the performance gain is, but in theory the rendering performance should be better when using immutable model in combination with shouldComponentUpdate and shallow checking.
we can make to deploy website from ci. it could collect all docs from correspondent github repos instead of dublicating documentation both on repo and website. it should simplify support docs in actual state.
see bem.info for example
I had a quick read through the V2 website in Vienna and think that we could maybe improve the content structure. Since I haven't had the time to discuss this on the meetup, I will just post it here as reminder.
Both http://www.christianalfoni.com/cerebral/ and http://www.cerebraljs.com/ has glitchy scroll in menu.
On my first reading "Structuring State" in V2 I found it confusing to read about namespaces. Why exactly would you call it a namespace?
http://www.christianalfoni.com/cerebral should redirect to the new site
Should we use classes or functions in the react examples on website V2?
We should also mention that you should avoid internal state, when using classes.
Code examples with horizontal scroll does not work for some strange reason
JSON.stringify doesn't correctly escape some strings (such as </script>) leading to potential client code injection. The use of a library such as serialize-javascript is recommended.
Vulnerability description:
http://benalpert.com/2012/08/03/preventing-xss-json.html
https://github.com/cerebral/cerebral-website/blob/v2/app/markdown/doc_servercontroller.md should be updated.
Heroku is overkill for doc site. Let host it on github pages.
I found the FAQ a bit unhelpful when it comes to the difference between Cerebral and Redux. I think most important thing to highlight would be what Dan said in a Twitter conversation about this very topic: "I guess Redux helps when your data structure is complex but async interaction is not very complex. Cerebral is opposite."
With many API and best practice changes it can be very confusing for users to figure how to do things if they're not on the latest versions of cerebral and related packages. We should maintain documentation and tutorials for all releases of cerebral, so we can always point users to docs for their versions.
This will also help us make changes and releases without confusing or disturbing people who can't always upgrade to the latest.
doc_operators
) to a specific git commit:{
"doc_operators": "https://github.com/cerebral-operators#cdndd33jdfeeed<SHA>
}
See github for example :)
Check and update testing documentation with latest changes.
At least it contains old action signature.
PR are welcome.
Now http://www.cerebraljs.com/#/6/1:
After http://www.cerebraljs.com/#/signals/input
http://www.cerebraljs.com/ is good place to demonstrate best practices.
would be great to see it covered with tests
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.