search

webcomponents / webcomponents.github.io

WebComponents.org is where community-members document Web Components best practices
http://webcomponents.org
734 stars 119 forks source link

Initial development for 1.0.0-alpha #20

Closed zenorocha closed 10 years ago

zenorocha commented 10 years ago

Hey guys,

After couple more iterations with @brizabueno, I think we got something to show you.

This screenshot was taken from 1.0.0-alpha branch; the page is responsive, dependencies are managed via Bower and it's already integrated with Jekyll.

In the next weeks we're going to work on the other pages, like Articles/Presentation archive and single post.

We know that are lots of stuff to improve, but at least we have something to start with and we're really excited about it.

0x-r4bbit commented 10 years ago

@zenorocha This looks so neat! :) great job, wow!

ebidel commented 10 years ago

This is looking particularly sharp!

Some initial feedback:

robdodson commented 10 years ago

Yeah I wonder if "Examples" could just be "Discover" then

zenorocha commented 10 years ago

Thanks a lot for the feedback guys, we're working hard to make it really awesome.

  1. +1 for better tag line. Any suggestions guys?
  2. Cool, let us know.
  3. Renamed to "Browser support"
  4. Done!
  5. Renamed to "Discover"
sindresorhus commented 10 years ago

The site looks really good. Nice work!

Some nitpick feedback:

screen shot 2013-11-22 at 09 33 48

I was going to suggest you use Masonry or Packery to make the boxes fit fluidly, but then I tried it and you already did :)

addyosmani commented 10 years ago

Really nice work, Zeno! This looks great.

Maybe "Getting started" or "Writing an element?" could dive into a page that links up to the best practices or other samples that we want to share with the community. That way the site remains really compelling for both element authors and consumers.

ebidel commented 10 years ago

Yep. Please refrain from the Polymer logo. We're working on something better. I'll get you that when it's ready.

Addy, I like your first tag line. Also, feel free to rip off the one I used used for Chrome Dev Summit: "Declarative, reusable, encapsulated components"

On Fri, Nov 22, 2013 at 2:59 AM, Addy Osmani notifications@github.comwrote:

Really nice work, Zeno! This looks great.

  • Although I (believe) this version of the design is targeted more at everyday web developers, I feel like we should still preserve the message of the site being a great place to learn how to author web components and learn about best practices. The current sections are great, but perhaps we could introduce one thats targeted to component authors.

Maybe "Getting started" or "Writing an element?" could dive into a page that links up to the best practices or other samples that we want to share with the community. That way the site remains really compelling for both element authors and consumers.

-

Slogan: I don't have a perfect answer to this, but maybe "Reusable elements using technologies you already know" or "Leverage your HTML, JS and CSS knowledge to build easily reusable elements." might work better here.

Polymer logo: I would personally opt for what Polymer uses in their twitter avatar. It's a P which is both a logo and not a logo. Would that make more sense until an official one is available @ebidelhttps://github.com/ebidel?

-

Header: could we try reducing the letter spacing between the characters in 'web components' by a few pixels to see if that looks better?

I feel like Examples should be 'Discover Elements' or 'Discover'. Glad to see that change made!

Shareability: might be useful to have some links to social networks where users can follow along with the project too.

— Reply to this email directly or view it on GitHubhttps://github.com/WebComponentsOrg/webcomponents.org/issues/20#issuecomment-29064692 .

robdodson commented 10 years ago

I like @stopsatgreen's tagline :boom: :sparkles: :fire:

addyosmani commented 10 years ago

Could we get some more votes on tagline? Any more thoughts on the other points? Would love to get a first private alpha complete in the next week or two if possible :)

0x-r4bbit commented 10 years ago

@addyosmani Let's take your first slogan but replace "element" with "component", so that we have something like: "Reusable components using technologies you already know"

sindresorhus commented 10 years ago

"Reusable components using technologies you already know"

:+1: despite you missing a white beard

0x-r4bbit commented 10 years ago

@sindresorhus Still working on it. I'm just 22 years old :(

robdodson commented 10 years ago

maybe "Reusable components with technologies you already know" so there isn't a redundant use of the word "use"?

sindresorhus commented 10 years ago

agree

brizabueno commented 10 years ago

Just getting through the retail crazy Black Friday and Cyber Monday days!! Now I'll start to work on the other layouts till the end of the week... Glad that in general you like the home page guys.

addyosmani commented 10 years ago

We really appreciate any and all time you can put into the design, @brizabueno! Thanks again.

On the tag-line, I was thinking 'elements' would help us avoid overloading the term 'components' too much as it tends to mean a bunch of other things. At the same time, the spec umbrella is 'Web Components'. @ebidel wdyt?

ebidel commented 10 years ago

It's a hard dance. Devs think web components. We say elements to relate to the olden days and a reminder that you're creating custom elements. At the end of the day, we're creating elements out of other elements...to form components.

My vote is elements but it's up to you guys. Agreed components is a loaded term at this point. On Dec 5, 2013 4:49 AM, "Addy Osmani" notifications@github.com wrote:

We really appreciate any and all time you can put into the design, @brizabueno https://github.com/brizabueno! Thanks again.

On the tag-line, I was thinking 'elements' would help us avoid overloading the term 'components' too much as it tends to mean a bunch of other things. At the same time, the spec umbrella is 'Web Components'. @ebidelhttps://github.com/ebidelwdyt?

— Reply to this email directly or view it on GitHubhttps://github.com/WebComponentsOrg/webcomponents.org/issues/20#issuecomment-29894781 .

0x-r4bbit commented 10 years ago

@addyosmani @ebidel Let's throw a coin, haha

addyosmani commented 10 years ago

Maybe take one more vote and it can be the decider? We can always change later :)

@zenorocha want to throw your thoughts in the bucket?

zenorocha commented 10 years ago

+1 for "element" :)

0x-r4bbit commented 10 years ago

Okay let's go with "element"!

sindresorhus commented 10 years ago

Using "element" when the project is named web components and components it's the most used terms is inconsistent and confusing. I would go with "component".

0x-r4bbit commented 10 years ago

Well @brizabueno looks like we need your opinion too!

brizabueno commented 10 years ago

Elements!!!

0x-r4bbit commented 10 years ago

@addyosmani your turn again.

cburgdorf commented 10 years ago

elements!

addyosmani commented 10 years ago

haha. Elements! We'll do another review in a few months to gauge community feeling on the wording. Sound good?

0x-r4bbit commented 10 years ago

@addyosmani Yupp

brizabueno commented 10 years ago

Hi there! I've been working in the archive and single page layouts (do we need any others?) Just made a few options, let me know what you think!

Archive: Option 1 archive3

Archive: Option 2 archive2

Single: Option 1 single2

Single: Option 2 single3

0x-r4bbit commented 10 years ago

Hey @brizabueno that looks great! I prefer archive option 1 and single option 1.

Archive option 1 because it also has cards. Maybe we could also show a little excerpt in a card?

Single option 1 because it's easier to read. On mobile, it'd be more like single option 2.

addyosmani commented 10 years ago

These look great @brizabueno! Thanks once again for all your time on these mocks :)

I like Archive option 1 and Single option 1 too. Do we have any ideas on how we might handle cards for content that might not have an image in place? e.g an article of text? I have seen a few themes handle this by using a content-specific placeholder (e.g image for post type) but perhaps there's a better way of handling that.

0x-r4bbit commented 10 years ago

@addyosmani well, I think when we also provide an excerpt per card and maybe add a little gravatar from the person from which the article is, it's not really a problem anymore, is it?

sindresorhus commented 10 years ago

This looks great :)

I would however strongly suggest we don't have comments. It never leads to good discussions and almost always ends up with trolling, questions and noise. Angular recently removed theirs. Most of the good blogs have removed it. We have github, twitter and mailing lists for discussions.

0x-r4bbit commented 10 years ago

Agreeing with @sindresorhus on removing comments section.

addyosmani commented 10 years ago

+1 on removing comments too for all the reasons stated.

@PascalPrecht indeed!

@brizabueno thanks once again for working on this. Do you think you'll have some time to continue working on it this month? :)

addyosmani commented 10 years ago

@zenorocha reviewing the current implementation in the 1.0.0-alpha branch, it looks like we would need to link up to pages for the various pages for cards and figure out how latest content should appear in the index, unless we want to handle that manually (which is also okay).

Because we're pre-alpha right now, I'd be happy for us to switch over to this branch for development once the pages are linked up but we can hold off if you would prefer to work in a clean branch instead. It would be great to figure out a rough timeline for the theme being in a position we could use it or what help you and @brizabueno might need on the implementation side :)

zenorocha commented 10 years ago

Imho, removing comments in documentations is indeed a good practice to avoid noise, but for blogs (which is the case for the Articles section) is the best way for people to interact with the page. But ok, 3 votes against 1.

zenorocha commented 10 years ago

Closing, since this was already implemented and moved to master branch.