This is sort of a reminder

"." != ""

putaindecode.io homepage gets a rerender each time, probably related to the test above.

https://github.com/rackt/redux-router

1.0.0 or 0.x ?

https://github.com/danmartinez101/babel-preset-react-hmre

• package.json
• baseUrl

Currently you cannot choose your url that are "guess" from your md files (content/whatever.md => /whatever/).
On GitHub pages, 404.html is used as a default page when an http 404 issue is raised. We need a solution to handle this case.
Simple solution is to support an url field in the md metadata header. Not sure if that's a good idea, but that will do the job and is flexible enough for other use-cases.

Dev server should redirect url like http://0.0.0.0:3000/my/page to http://0.0.0.0:3000/my/page/ and load the corresponding index.html if available.

With a fresh install, I get some 404 on requests like http://0.0.0.0:3000/994b3200cd56ef773c84.hot-update.json :/

Ref #21

...instead of classes.

Blocked by #42

Doesn't work with gh-pages-deploy-sh (it deploy the entire repo even if you provide the right glob) or gh-pages (say it works from log, but it doesn't)...

Related to #5

Currently we need to build a static version + run the dev server. This is counter productive. The express server should be able to generate the page on the fly directly.

I am on it.

Something like eslint-config-meticulous ? :)

https://ci.appveyor.com/project/MoOx/statinamic/build/41/job/xeld5cy5m6ek0r58#L1769

npm WARN ENOENT ENOENT: no such file or directory, open 'C:\projects\statinamic\docs\node_modules\README.md\package.json'

This is weird :/

npm install statinamic --save-dev
npm run statinamic

Error:

> statinamic setup

module.js:338
    throw err;
    ^

Error: Cannot find module 'npm-install-package'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:286:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/Users/GuillaumeDEMESY/Github/Me/magsout.github.io/node_modules/statinamic/lib/bin/statinamic-setup.js:5:26)
    at Module._compile (module.js:434:26)
    at Object.Module._extensions..js (module.js:452:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:475:10)

of course, if I install npm-install-package manually, its works

Since we don't do a lot of modifications (ie: no modification at all for now), we might consider replacing redux usage by react context (that are now documented http://facebook.github.io/react/docs/context.html).
That should be clearly enough to just "pass" some data (collection and page components references) that are declared during app initialization.

It don't really see any downside from the current usage.

Any thoughts? poke @bloodyowl

stats report only homepage from what I see. I need to investigate.

http://facebook.github.io/react/blog/2015/09/10/react-v0.14-rc1.html

If we do not specify any template for a page, we get this error :

Unkown page type

"undefined" component not available in "pageComponents" prop

I think you should use a fallback template

In order to be able to use some webpack loader during the static build, the static builder need to be generated using webpack.

or at least explain a little the usage of each of them.

Eg:

• tags
• date (year, year/month...)

with a way to sort / paginate results

reactiflux needs a constant activity on the channel and want to shut down the one of statinamic because of the current inactivity.

• use js instead of json
• use md to react instead of raw html https://www.npmjs.com/package/commonmark-react-renderer

https://github.com/barryclark/jekyll-now

This should be really easy to offer and will attract people. And btw, this should be the default way to create a statinamic website.

https://github.com/gaearon/react-transform-boilerplate

See https://github.com/sindresorhus/ava/blob/1d5ef4c5f6fcb70f9e90e584dfd0886/package.json#L35-L36

env:
  - CXX="g++-4.8"
addons:
  apt:
    sources:
    - ubuntu-toolchain-r-test
    packages:
    - g++-4.8
    - gcc-4.8
node_js:
  - 4.1.0

Should check if all that stuff is still necessary and if we need to specify the entire version (maybe - 4 just works for all 4.x versions)

Generated links are not good for the static version

If I try in your demo to go to other pages, I go to file:///routeName

This will also ensure npm@3 compat.

http://babeljs.io/blog/2015/10/29/6.0.0/
https://medium.com/@malyw/how-to-update-babel-5-x-6-x-d828c230ec53#.d5mdgg3vb
We miss a full config to == stage-0 + react

we need to wait for babel-plugin-react-transform to update (and friends)

https://discord.gg/0ZcbPKXt5bW1pAiw