Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Sep 11, 2015

This completely refactors the file and menu structure of the site.

My feeling is that this new structure is not ideal but is better than the current.

  • The menu items are roughly ordered left-to-right in the order you use them.
  • IDEs is broken out from env
  • Implementations new category instead of env. This also partially fixes Implementations aren't "systems" #37
  • Consistent capitalization
  • Theoretically more noobie-friendly menu titles.

Two questions:

  • What the should we call the quicklisp link? I like it up by itself, but i'm not sure if "Libraries" is really the right thing. Maybe packages? Idk, trying to be noobie friendly.
  • LispWorks is an IDE and an implementation. Right now i'm solving this via symlinks (which git supports last I heard) but maybe there's a better way?

Christopher Carpenter added 5 commits September 11, 2015 00:50
This standardizes capitalization in the menu and categorizes things into
more distinct categories that I hope are more helpful.

Quite frankly we could use a web designer to give this kind of thing a
once over, I'm a web developer :).
Order them roughly in the order that you'd use them being a novice, I think.
@pnathan
Copy link
Collaborator

pnathan commented Sep 11, 2015

Interesting. Any particular rationale for the reordering of the nav structure?

@ghost
Copy link
Author

ghost commented Sep 11, 2015

The literal ordering rationale was simply "The menu items are roughly ordered left-to-right in the order you use them.". It makes sense to me since western audiences read left to right.

As far as the reorganizing of categories(removing some, adding others) and such, it was mainly just based on what I felt made sense. No real hard reasons.

@ghost
Copy link
Author

ghost commented Sep 11, 2015

Off to bed. I imagine this should be a discussion, let me know if you want to do IRC chat or even a call or something.

@pnathan
Copy link
Collaborator

pnathan commented Sep 11, 2015

@mordocai Somewhat. My heroic weakness is UX. If you're practiced at making sites easy to use and comfortable for newbies, I am happy to defer. I compared the two sites and I don't have a strong opinion.

@ghost
Copy link
Author

ghost commented Sep 11, 2015

I don't consider myself great at UI but I have a friend who I do consider great at it. I'm going to have her take a look at both versions and offer suggestions

@pnathan
Copy link
Collaborator

pnathan commented Sep 11, 2015

The one thing is that I would like to ensure a highly information-driven aesthetic, with minimal "pop" and "flair"; just enough to smoothly and effectively communicate.

@ghost
Copy link
Author

ghost commented Sep 17, 2015

Just to let you know, I haven't forgotten about this. My friend just hasn't had time to take a look yet.

@pnathan
Copy link
Collaborator

pnathan commented Sep 18, 2015

noted! I look forward to a design critique. :)

@veddox
Copy link
Contributor

veddox commented Sep 23, 2015

@mordocai, I like your revised structure of the site. I think the current menu, while no doubt functional, feels rather hacked up ("env" instead of "Lisp Environment" or some such, lower-case first letters). Your changes eliminate that and make the whole site more easily navigable. (I was confused by the menu myself when I first saw the site.)

@pnathan, I vote for adapting the menu.

@escarre
Copy link

escarre commented Sep 23, 2015

@pnathan, I'm the friend @mordocai mentioned! I understand the goal is straightforward-ness and clarity rather than "making it pop", and @mordocai's changes definitely help achieve that end. As a non-Lisper myself, I'm a great test subject, and I prefer the new menu structure. I vote for merging.

In an ideal world, I think the best case scenario would be a bit of a 'getting started guide' that culminated in the list of further resources. That said - this is a great start.

@pnathan
Copy link
Collaborator

pnathan commented Sep 24, 2015

ok!

pnathan added a commit that referenced this pull request Sep 24, 2015
@pnathan pnathan merged commit faf54b8 into articulate-common-lisp:master Sep 24, 2015
@ghost
Copy link
Author

ghost commented Sep 24, 2015

Hey, when do you expect this will be deployed to the live site? Just wondering because I want to double check everything on live since I'm paranoid.

@pnathan
Copy link
Collaborator

pnathan commented Sep 24, 2015

Good question... Probably by Sunday night.
On Sep 24, 2015 10:52 AM, "Chris Carpenter" notifications@github.com
wrote:

Hey, when do you expect this will be deployed to the live site? Just
wondering because I want to double check everything on live since I'm
paranoid.


Reply to this email directly or view it on GitHub
#46 (comment)
.

@pnathan
Copy link
Collaborator

pnathan commented Oct 5, 2015

Hey, @mordocai , @veddox and @escarre - Super sorry regarding the delay. Long story involving pnathan and his travails in DIY Linux. The Docker image is pushed and running.

@veddox
Copy link
Contributor

veddox commented Oct 8, 2015

@pnathan, great! I think I'll take a look at the CLisp page, it's the implementation I use so I should be able to write something about it...

@pnathan
Copy link
Collaborator

pnathan commented Oct 8, 2015

@veddox - thanks! Love to see it!

On Thu, Oct 8, 2015 at 1:50 PM, veddox notifications@github.com wrote:

@pnathan https://github.com/pnathan, great! I think I'll take a look at
the CLisp page, it's the implementation I use so I should be able to write
something about it...


Reply to this email directly or view it on GitHub
#46 (comment)
.

@veddox
Copy link
Contributor

veddox commented Oct 8, 2015

@pnathan I submitted a pull request. Let's switch the discussion over to the next thread ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implementations aren't "systems"

3 participants