Create landing page

[mitar]

We have domain: http://blazejs.com/

Probably something simple hosted on GitHub pages.

[laosb]

So we need a separated repo for the GitHub Pages. Even an separated organization.

[mitar]

No, it seems we can just have a gh-pages branch in this repository.

[laosb]

That's true, but it's not a good practice since you may put Pages and package things, which are slightly different, into same repo.
Look at Node.js, they use different repos, and even have separated workgroup for it.

[mitar]

Look at Node.js, they use different repos, and even have separated workgroup for it.

They are slightly bigger project. ;-)

But yes, we can have a separate repository. But this goes more to the question of #13. How many repositories we do want. If we want to stick everything into this repository, it is doable, but I personally agree that I would go with something like vue.

[laosb]

Yup, +1 for something like vue.

[MiroHibler]

There's also a repo by the guy who is currently hosting http://blazejs.com - https://github.com/voidale/blazejs, but yes, having it here (as gh-pages) does make sense.

On a related note, since the idea is also to make the landing page a Blaze showcase, it may be a good idea to host it on Galaxy.

[ghost]

Hi guys ! We're are we on this landing page ? Do we have something yet ?

[alexandesigner]

Hey guys, what the repository we're going to work? the site should be something similar to Apollo, a apollostack.com and docs.apollostack.com?

blazejs.com and docs.blazejs.com

We already have something? I would like to add up efforts to this task.

[laosb]

Willing to help +1

[mitar]

We do not have yet a repository, but feel free to have it under your username and we can later on consolidate when we create an organization.

[brown2rl]

Thinking about content.. If we are to showcase on the homepage, should we have testing results and out of the box compatibility demos with other UI things like jade?

[alexandesigner]

See: https://alexandesigner.github.io/blazejs/docs

We do not have yet a repository, but feel free to have it under your username and we can later on consolidate when we create an organization.

See too: #19 (comment) and see what we can get, I'm replicating content Blaze Docs + Blaze Guide (Meteor). There's more we can explore, API, own project Blaze Components ... ?

Any help in this regard? (content) Then, I can focus on creating the other pages during week

[comerc]

We need logo to start. React will dead! :)

[comerc]

it is not very expressive logo

we need an animated character like this example:

[MiroHibler]

Or this one ;)

[mitar]

I would suggest we simply use GitHub pages to host a landing page. I think we can use a custom domain with it as well.

Let's create gh-pages branch in this repository and then use it to create a landing page.

[stubailo]

it is not very expressive logo

I love the Blaze logo above.

I would suggest we simply use GitHub pages to host a landing page. I think we can use a custom domain with it as well.

Definitely the easiest idea.

[mitar]

We have a landing page: https://meteor.github.io/blaze/

[karldanninger]

Can help out with this at least a starting point

[mitar]

Please do! Pull requests welcome! Consider maybe adding content you ever wanted to see on the landing page. I asked @alexandesigner if he could help us with the design of it.

[mitar]

We have it deployed at http://blazejs.org/!

[alexandesigner]

@mitar The site is being updated automatically after merging with the master? I think we're still an outdated version 😫

[mitar]

You can see here when wast the last update.

And here was the last build. It failed with:

ERROR Deployer not found: git

Strange that CircleCI did not report any error about that.

[mitar]

Fixed in 5c588d6.

I am closing this ticket now. I think we have now a pretty good site.