Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Engine #8

Closed
marcustisater opened this issue Dec 31, 2015 · 11 comments
Closed

Engine #8

marcustisater opened this issue Dec 31, 2015 · 11 comments
Assignees
Milestone

Comments

@marcustisater
Copy link
Member

The main decision is to agree on what system is going to be used for this website. My first thought was to do this website in like Jekyll or an small CMS system but now after so many people already wanting to contributing and having suggestions I will leave this up for a very open discussion.

@MoOx has one suggestion of using Statinamic stated in ticket #391

Don't know what you plan to use for the engine, but I would be really happy to offer some support for my new engine Statinamic (react based static website generator, that also provide client side optimised navigation).

What do you guys think? Let us know you're thoughts.

@marcustisater marcustisater added this to the Sprint 1 milestone Dec 31, 2015
@marcustisater marcustisater mentioned this issue Dec 31, 2015
@ai
Copy link
Member

ai commented Dec 31, 2015

@mxstbr can we run plugins search on client side with any help from server?

@MoOx
Copy link
Contributor

MoOx commented Dec 31, 2015

statinamic can prerender page during the build step and can also run client side react view (so live search with an api is not an issue)

@jonathantneal
Copy link
Member

My 2 cents: Let’s not over React.

I’d aim for beauty and simplicity while leveraging the tools of our community.

@marcustisater
Copy link
Member Author

I'm all about using more modern stuff like React but I'd say that simplicity is a great point by @jonathantneal because we would want to have a low "learning curve" so more people can contribute something and also not relaying on @MoOx to be around for 24:7 support if anything goes wrong.

@mxstbr
Copy link
Member

mxstbr commented Dec 31, 2015

@ai yeah, that works.

I love React, have worked a lot with it (postcss.parts is written in react), and have been meaning to try Statinamic for a project, so I'll +1 that. I'm fine with Jekyll as well though.

@ai
Copy link
Member

ai commented Dec 31, 2015

I understand @jonathantneal with this idea of simplicity.

But I really think that we should experiment with React based statis site. Yeap, it will be more complicated. But it is now fun, and hobby site is for fun.

Also we should use 100% isolated components with CSS Modules and postcss-autoreset with all: initial, like I told on http://ai.github.io/postcss-isolation/

It is good to show full power of PostCSS on main site.

@mxstbr
Copy link
Member

mxstbr commented Dec 31, 2015

@ai 👍

@stephenway
Copy link
Collaborator

@ai Exactly, we need to make this website the driving force for all this project has to offer. 👍

@marcustisater
Copy link
Member Author

Alright, let's try out Statinamic. I think we have enough react heroes to make that happen 😄

@mxstbr will be leading the development process. TBA upcoming meeting.

@MoOx
Copy link
Contributor

MoOx commented Jan 2, 2016

I will try to submit a PR this week with a Statinamic default boilerplate.

@marcustisater
Copy link
Member Author

#13

@marcustisater marcustisater modified the milestones: Sprint 1 - Mockup & Planning , 1.0 Jan 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants