Discussion on plugin system

Generating a static site isn’t only a matter of routes and flat files. Sometimes you need to generate files that don’t lend themselves to react-router routes:

1. Resized images
2. RSS feeds
3. .htaccess redirect rules
4. Downloaded/locally-cached resources

I can imagine writing generated files directly to /dist during getSiteProps() or getProps(). But that feels incredibly dirty, both because it’s relying on side-effects and because it’s circumventing whatever resource conservation react-static has or will someday have.

So what’s the recommended way for handling these situations?

[tannerlinsley]

So far my thoughts are leaning towards keeping the react-static api very lean and improving the way people use and interact with the examples. I’ve heard some great ideas here and elsewhere about improving the documentation for each example to show linear changes that are made to accomplish each one. We could also make a new Guides section in the documentation that instead shows how to implement other popular concepts step by step (ultimately pointing them to the examples for a finished product).

[tannerlinsley]

I think it’s the latter. The readme should document the core changes and usages in the example with code blocks.

On Thu, Mar 1, 2018 at 10:21 AM Riley [e-mail] wrote:

I wonder if there is a good filesystem diffing we could do to compare examples.

Say we have a core example folder, then we compare that to examples and have some mardown or HTML diff viewable so people see what files are different?

Sometimes looking through examples can be hard to know what files are different?

Or maybe this means the readme examples should have a more strict readme format explaining the example in more detail??

— You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub https://github.com/nozzle/react-static/issues/309#issuecomment-369664277, or mute the thread https://github.com/notifications/unsubscribe-auth/AFUmCUYj0Ssjvb-gAlQ2iccqfQcS--9Yks5taC4NgaJpZM4Rpkt2 .