Converting it to a Static site

[sahitpj]

I think we need to change this into a static site, using either Jekyll or Hugo or any other possible alternative. Allows for the possibility of writing blog posts and other Talks as different categories.

For those would like to contribute, do make a new branch and merge it into the "developing" branch of this repository.

[jkomyno]

I'd suggest to convert the website to a ReactJS single page application. I'd also tackle #4 in the meantime, writing a static site that is mobile friendly from the beginning.

[AniaMakes]

Just asking for more questions before offering help :)

• Would you prefer the new site to be single page, or multi page?
• Do you want to use CMS (eg Contentful) to provide the data? If yes, which one?
• Do you want the design to closely match the current one or completely changed (if the latter - do you have designs in mind)

(@jkomyno 's comment just popped up - I do agree that ReactJS approach, maybe using Gatsby, would do the trick).

I agree this issue should integrate #4 and that issue be marked as "check status of #3 before working on this"

[jkomyno]

@AniaMakes Hi, I was also thinking about Gatsby, something among these lines: https://medium.freecodecamp.org/how-to-build-a-react-and-gatsby-powered-blog-in-about-10-minutes-625c35c06481

[AniaMakes]

If @sahitpj wants to have blog posts, then using Wordpress API might be a good approach.

I'd also suggest using Styled Components if using Gatsby.

[sahitpj]

hey @AniaMakes we are thinking if adding the blog-posts feature, as an initiative for people to come up with good articles and interesting findings they have. I am thinking of the same deign for now, and I think gradually over time we can slowly modify it

So i think that talks about it being a single page webpage or not right? @jkomyno .

Let me know what you guys thing, and thanks for budging in on this. 😄

[AniaMakes]

@jkomyno I've set up a gatsby project here. The structure is rather clunky because it keeps the current structure so that if I do make a PR as-is, it won't break the current website. It would be nice to work on this with someone else - what's the best way to proceed in your opinion?

[jkomyno]

@AniaMakes The first thing I'd do is split the PRs in a divide et impera fashion. For instance, there should be a PR for every page, or even for every section. This way it'll be easier to review what's been done, and it will also help us share the work between us :)

[AniaMakes]

@jkomyno Sure, but it would be silly for us to be working on independent copies of code and try to merge them after XD I've never worked remotely, so I'm not sure what tools there are beyond trello to coordinate and communicate (otherwise this issue will be more chat than actual content).

[sahitpj]

hey @AniaMakes you can start by making a PR of your basic outline to the static branch and then you and @jkomyno could start working from then

[jkomyno]

@AniaMakes do you have a Gitter account?

[AniaMakes]

@jkomyno I've set this up: gitter.im/pydatagn-static

[jkomyno]

Joined it, thanks