I'll be putting most of this in a blog post when we make the actual
move, but I wanted to send some heads-up now. A few of us have been
having some offlist discussions about how to improve the Yesod site,
and make it easier for others to contribute. I think it's time to open
up this discussion to the whole community.
A major problem is that our Wiki needs improving. It's not easy to
use, and since it lacks any kind of sophisticated change tracking,
there's always the concern of overwriting other people's changes. Greg
came up with a brilliant solution: just use the Github wiki! This
avoids the need to have to reinvent the wheel, and lets us continue to
use Git for storing our contents. The goal here is *not* to redirect
people to Github for reading our Wiki, but to mirror the contents onto
the main site, and to have people edit the contents on Github.
I've done an initial migration of our Wiki contents to Github:
https://github.com/yesodweb/yesod/wiki . Please do *not* start editing
content there, as I will be applying the migration again in the
future, wiping out any changes you've made. I just wanted to get some
input.
This is also a great time for anyone who wants to take over styling of
the site to jump in. I'm fine leaving the site with the current
styling, but if someone would like to contribute a new look, the next
codebase will be drastically simplified and allow anyone to build
locally. The repo is at: https://github.com/yesodweb/yesodweb.com
Michael
I have been wanting to restyle the site for ages, but being the noob that I am have been unable to build the site locally despite several efforts. Is anyone online next weekend who could help me get started? Michael has previously been kind enough with help on building, but I still ran into issues setting it all up.
Peace,
Bas
Now that all of the libraries required are available on Hackage, it
should be much simpler. Try pull the newest changes (including the
markdown submodule) and running "cabal update && cabal install". If
that doesn't work, then we have bigger problems[1].
Michael
[1] Unless you have installed some unreleased stuff from Git. If you
want to be extra safe, start off with rm -rf ~/.ghc
You'll notice that there is absolutely no styling applied (all of the
CSS is coming from normalize.css).
Michael
That's also the github wiki? I don't get it.
The repo in question (https://github.com/yesodweb/yesodweb.com) includes the Github wiki as a submodule. The site serves that content. It also includes another repository that contains the book, blog posts, static page (FAQ, about, etc) and the homepge.
Michael
Actually, all styling/logo questions I leave up to the community. I suppose I'm the de facto gatekeeper on this, and will have to make the final decision (since I'll be the one uploading the code to the server), but I'm happy to listen to everyone else's advice here.
If you have an idea for a new logo, my recommendation is to create it and put it up somewhere, and then we can decide if we should switch.
https://gist.github.com/1854004
And the crowd goes wild! Thank you! Thank you so much! You're all too kind.
I'll be here next week with all new material but for XMonad this time.
--
Darrin
I think we need to see how it would look when includes the 'esod'
Another approach for a logo would be to incorporate the foundation
(meaning of the word yesod) aspect.
What about Yesod's aspirations or practice is very different from
what's available in other frameworks, including Rails, Django, Wicket,
Snap, Happstack, etc.?
My thought behind replacing the lambda with a Y in the Haskell logo,
is that it combines something that represents Haskell, the roughly
same proportioned monad from the Haksell logo, with the Y to set
things apart and say Yesod. And it does all that with very few lines,
which is important. Maybe the Haskell logo could have been simplified
more but it is what is now.
So that's where my question comes from. What about Yesod is unique in
either aspiration or practice? That might give us some concepts to
think about representing as simple symbols or shapes. If we can work
out something that's distinctive and initially abstract but turns into
an in-joke people get later, that's fun too.
--
Darrin
are you using cabal-dev or virthualenv? cabal-dev seemed to work, but
I gave up on it after trying to figure out how to get it to recognize
alex. I then did a clean install with virthualenv
> i cannot build the new site.. do i miss somehting?
I'll start a separate thread on this later today (hopefully), but Max
Cantor and I met up and talked about a number of Yesod-related topics,
and we might have come up with a better solution to dependency hell.
Michael
I've got to say: cabal is incredibly mind-bendingly stupid at times. I
just pushed some changes that will *hopefully* help it compile
properly on your system.I'll start a separate thread on this later today (hopefully), but Max
Cantor and I met up and talked about a number of Yesod-related topics,
and we might have come up with a better solution to dependency hell.Michael
You could try:cabal install --upgrade-dependencies
If that doesn't work, then you'll probably have to upgrade to GHC 7.0.4 or 7.4.1.
cabal install alex
Then you should be able to install. This is another example of wanting
a better tool than cabal...
Michael
Fortunately, this is an easy one. Just make sure ~/.cabal/bin is on
your PATH, and run:
cabal install alex
Then you should be able to install. This is another example of wanting
a better tool than cabal...Michael
git submodule update --init
You need to check out the submodules. This is a good sign, you're almost there!git submodule update --init
>
>
You need to check out the submodules. This is a good sign, you're almost there!git submodule update --init
>
>
You need to check out the submodules. This is a good sign, you're almost there!git submodule update --init
>
>
Thank you! I'm actually thinking about putting together a script to
download/install GHC and the HP automatically, which should make some
of that process easier.
> based on my experiences i wrote a README for yw.com
>
> https://github.com/yesodweb/yesodweb.com/pull/1
>
>
Yesod is likely to attract a lot of very green Haskell devs. It's
probably best to give a single supportable set of install
instructions.
> We depend on HP 2011.4, so install that and setup your cabal-bin path and
> off you are.
>
> I dont know but maybe you should make HP 2011.4 a dependency here:
>
> http://www.yesodweb.com/page/five-minutes
>
Can we just send people to virtualhenv now? That way when they show up
here for help they should have a solvable problem. I would add to the
five minute docs that users wishing to work productively should add
--dev to cabal configure. -O0 is a _lot_ faster on my little ol' i3
mid tower and the debug logs are actually useful when flushed. Also,
that 40 second Model.hs compile problem goes away too.
FWIW I got the official yesod 0.10.1 working with just ghc-7.4.1 +
virtualhenv + alex + something I probably forgot. Not sure if we want
new people going that route though.
--
Darrin