search

paz-sh / paz

An open-source, in-house service platform with a PaaS-like workflow, built on Docker, CoreOS, Etcd and Fleet. This repository houses the documentation and installation scripts.
http://paz.sh
Other
1.08k stars 56 forks source link

paz.sh #14

Closed tomgco closed 9 years ago

tomgco commented 9 years ago

Currently the website paz.sh is still an email capture with a few descriptions about paz, will this be open-sourced so we can update the site with more up to date details and documentation? =D

jemgold commented 9 years ago

Absolutely. I propose we figure out roughly what content we want on the site in the next few months, I'll build the first pass on it and then open source it so anyone can update it.

Can either plan content on here or in the pub ヽ(。_°)ノ

lukebond commented 9 years ago

Yes good point, thanks guys.

Perhaps this is a good place to determine what that is. And you remind me that I need to email all those people...if any of you are reading this, sorry :)

For me, I think the landing page needs to contain the following:

Anything I've forgotten?

sublimino commented 9 years ago

prominently featured "try it now" minimum-friction walkthrough?

On 26 February 2015 at 17:17, Luke Bond notifications@github.com wrote:

Yes good point, thanks guys.

Perhaps this is a good place to determine what that is. And you remind me that I need to email all those people...if any of you are reading this, sorry :)

For me, I think the landing page needs to contain the following:

  • Screenshots and a screencast
  • List of features
  • Links to documentation and repositories
  • Links to talks/slides/etc. about Paz

Anything I've forgotten?

— Reply to this email directly or view it on GitHub https://github.com/yldio/paz/issues/14#issuecomment-76221338.

tomgco commented 9 years ago

Screenshots and a screencast List of features Links to documentation and repositories Links to talks/slides/etc. about Paz

All sound good to me, especially like the “Try it now” / UI Demo.

Also one thing that I am finding difficult to decide is what to work on next / what needs to be done before we can call paz “Stable”, maybe this would suit well some place on the site or in the Contributing.md file. I specifically like the https://www.consul.io site.

jemgold commented 9 years ago

For the demo - I wonder if we can rig up a version of the web UI with Ember fixtures to play around with?

tomgco commented 9 years ago

@jongold Sounds great.

jemgold commented 9 years ago

First pass:

… but I think this is starting to get there.

desktop hd

lukebond commented 9 years ago

wow @jongold that looks absolutely beautiful :) thanks so so much

lukebond commented 9 years ago

@jongold roadmap not solidified but discussion can be found here: #19

documentation is currently a big problem, being addressed this weekend, see here: #20

lukebond commented 9 years ago

I think we should make a stop-gap fix to the landing page, maybe just removing all copy except the logo and "Website coming soon", and a link or two.

jemgold commented 9 years ago

Why not just point the domain to this repo for the meantime?

jemgold commented 9 years ago

(I agree btw - don't think I'll have this design coded until the end of the weekend at the earliest)

lukebond commented 9 years ago

Don't really want to redirect it to GH. Might just change that "coming soon" message and leave it at that for now. Would you object @jongold?

jemgold commented 9 years ago

Go for it! 

lukebond commented 9 years ago

Done. I apologise for my front-end skills.

lukebond commented 9 years ago

Just found the paz-landingpage repository, will move it to yldio and make it public and we can take it from there.

tomgco commented 9 years ago

@jongold Looks awesome =D

jemgold commented 9 years ago

Weekend progress on front end - https://github.com/yldio/paz-landingpage/tree/v2

paz - continuous deployment for production environments

Couple of things left to do but I think it's basically shippable.

If someone wants to proofread it, I can merge. Was thinking we could just host it on GitHub Pages unless you particularly want to keep it Dockerized - but that might be over complicating things.

btw I created a new orphan branch in Git as it's essentially a new project; GitHub won't let me create a PR vs. current master but when I get the go-ahead I'll force push to master…

lukebond commented 9 years ago

Got for it, @jongold. Great stuff, thanks.

There are one or two minor copy tweaks I'll make after you merge.

lukebond commented 9 years ago

re Github pages, that would be fine normally but it would only work if Paz was it's own organisation I think? I think we will move it to its own organisation btw.

Landing page isn't Dockerised, perhaps you're thinking of paz-web.

lukebond commented 9 years ago

@jongold I created https://github.com/paz-sh and moved the landing page repo there

jemgold commented 9 years ago

Moved from paz-sh/landingpage to paz-sh/paz-sh.github.io

Ready to go once you set up the DNS - just make a CNAME from www.paz.sh -> paz-sh.github.io https://help.github.com/articles/tips-for-configuring-a-cname-record-with-your-dns-provider/

lukebond commented 9 years ago

Thanks @jongold. I've done it, now we play the DNS propagation delay waiting game.

tomgco commented 9 years ago

Seems we are live shall we close this and move further discussion to: https://github.com/paz-sh/paz-sh.github.io/

lukebond commented 9 years ago

Yes, thanks all for this one.

tomgco commented 9 years ago

:heart: @jongold & all