Decide on Website Stack

[thnukid]

Hi Guys, Sparking the discussion about the new homepage stack:

[Static Side Generator]

• https://www.gatsbyjs.org/
• https://middlemanapp.com/

[Hosting]

• https://www.netlify.com/
• github.io (gh-pages)
• ftp

[CMS]

• https://www.netlifycms.org/
• Github Pull Requests

[Template]

• TBD

---

I would like to give Gatsbyjs a try. Next step would be to do the initial commit and transfer the current content to the new repository.

What do you guys thinking about?

[thnukid]

https://www.gatsbyjs.org/docs/gatsby-starters/ # Templates, Starter Boilerplates with gatsbyjs

[npalm]

@thnukid sounds good. Will add some more details later this week.

[thnukid]

:+1:

Discovered this:

Typography.js provides a vastly simpler way to define and explore typography designs.

https://github.com/kyleamathews/typography.js Demo

[thnukid]

Example websites sit on one or the other end of the spectrum from very basic to complex/complete.

https://github.com/gatsbyjs/gatsby/tree/master/examples#gatsby-example-websites

[npalm]

@marcinczenko prefers to start from scratch and use the starter as inspiration. For me both is fine. but once we use a starter we should look only for starters that are based on Gatsby V2

Main required features are:

• Easy to add articles, lets say news items
• Easy to publish speakers, talks via markdown for example. Talks can have one or more speakers
• A way to publish a schedule.
• [nice to have] support also content for past editions
• All content that is on the current site