Discuss Sitegen (React based static site generator) and Reactdown (markdown based rich document format).
Definitely interested in static site generators with ReactJS. I've been working on one that uses webpack. Of course, I can't stop myself wanting to get hot module reload to work with markdown files :P . For some reason I can't find a way to make it happen with 'dynamic' contexts.
zenlambda: do you mean reloading when new files is added?
It's not yet implemented in sitegen. But I think it's not that hard.
Let me find the relevant explanation from @sokra
That should make it, I think — https://github.com/webpack/webpack/issues/834#issuecomment-76590576
cc @KyleAMathews, as you also wanted this, I think
or maybe I wrong, I didn't check it yet, tbh
will report back when I will try to implement this
Hi guys, I'm curious: how does sitegen compare with https://github.com/jaredly/demobox ? I'm looking for a react style guide tool.
hey, i'm wondering what the current status of this project is. between sitegen, https://github.com/gatsbyjs/gatsby, and https://github.com/MoOx/statinamic/, i think sitegen has the simplest API and the best approach to deal with the build tool fatigue of configuring webpack, hmr, etc.
also, is there an API for getting the currently-rendered page metadata (markdown frontmatter) from inside a chrome component? e.g. to display a
title metadata value
Hi, sitegen works really nice. Thank you for sharing it! I was trying to understand sitegen's source code and stumbled upon transformation of public methods like
includePage in src/index.js by src/babel/QueryAPIBabelPlugin.js Wow, I had to grep for includePage throughout the repo in order to find the place where it's rewritten. Can someone explain me the reasoning behind transforming the code like that? It looks so mysterious to me.
includePages('./posts/*') is better than require('page?glob=./posts/*!')
But yeah... could be simpler I guess.
@elliottsj Hey, sorry for late reply. Currently we use https://github.com/nfl/react-helmet through
<Sitegen.Meta /> so any page can inject <title /> or <meta /> into the <head />.
@andreypopp no worries! i was actually wondering if there was a way to get the metadata for the currently-rendered "child" page from a parent component. e.g. if i have pages/posts.js_ and many posts in _pages/posts/*.md (and posts.js has
includePages('./posts/*.md')), is there a way for the posts.js component to get frontmatter values from the currently-rendered page and display them? something like:// posts.js
export class component extends React.Component {
render () {
const pageMeta = getCurrentPage().meta
return (
<div>
<h2>{pageMeta.title}</h2>
<span className='post-date'>{formatDate(pageMeta.date)}</span>
{this.props.children}
</div>
)
}
}
Is the source of the documentation site (https://sitegen.github.io/) on GitHub somewhere? Would like to look at the source to learn from it.
@cutemachine sorry for late reply!
Is there an easy way to add Jeet (https://github.com/mojotech/jeet) to a Sitegen project? Jeet is based on Stylus and I do not know how I can add a webpack loader to Sitegen.
:-)
