12 Days until beta download package

[Brad Czerniak]

Thank you for joining hawiducss-discuss!

September 1st I'd like to officially make a Hawidu CSS beta. What this means:

• The release will be tested based on the testing protocol (to be completed) using the build tests (to be completed), and considered stable-ish
• All files will be rolled into a compressed download rather than only being in source control
• A deployment branch (probably named "releases") will be created in the git central repo
• The branch will get a beta 1 tag
• Work will continue in the master branch

In order to make this release attractive enough for anyone to want to download, quite a bit needs to get done in the next 12 days:

• Review nomenclature and semantics (does the class 'hawidu' mean anything? Should it be changed to 'page'?)
• Remove the button background image dependency and replace it with CSS gradients
  
• Create pasteins in the pending and unsupported categories (grid systems, colorful designs, etc., formatted to the syntax rules)
• 'Borrow' common widgets from other popular frameworks [with preference to GPL CSS, though licenses for style sheets are kinda BS IMO]
• Finish testing protocol doc and create/finish a [graded?] browser support statement
• Make a reasonably-complete line-by-line doc
• Make a getting started wiki page
• Build out the test page
• Test against supported browsers
• Fix any browser support bugs
• Make a last-minute change to a new layout technique (Golden grid maybe? Sorry Vladimir, Joni stole your project name)

In my mind I'm splitting this into the first five items in the next six days, and the last five in the second six. It happens that I've got September 1st and 2nd off from work with nothing really to do, so I might push the release a few days and spend the Labor Day weekend on it. This Sunday will likewise be devoted mostly as a hawiducss work day. If you've got some time in the next two weeks to help out, I'd be thrilled to have it!

Why I'm emailing / tl;dr

1. If you have input into the framework, this would be a good time to voice it
2. I'm struggling with an "elevator pitch". Any pointers on concisely explaining why a single-page, compact-syntax, semantics and efficiency focused CSS framework without all the cruft of other frameworks is a good thing would be greatly appreciated. What's the sentence that sells this to designer/developers?
   

Accessibility could be a real selling point with the first crop of approved pasteins, so I figured Deborah might have some direction for accessibility styles (one for each of the WAI-ARIA roles?). The default styles should be attractive, and Nate has been in the making-good-looking-sites-using-CSS game for longer than anyone I know. And in terms of layouts and making useful CSS frameworks, nobody really has as much experience as Vladimir. So if you have any advice for the sort of things you look for, I'd truly value your opinions.

Have a great weekend!

[vladocar]

Hi All,

I think one of the most important thing is to show people more demos
and examples. Nobody will bother to look at the code if they don't
like the demos.

I think the strong side of this framework is the typography it will be
nice to point that out.

About some questions:

Does the class 'hawidu' mean anything? Should it be changed to 'page'?
*** Yes. Page or something else.

Make a last-minute change to a new layout technique? *** Focus on
making more demos, you can always add more features in the next
version.

Have a nice day

On Aug 20, 12:12 am, Brad Czerniak <ao5...@gmail.com> wrote:
> Thank you for joining hawiducss-discuss!
>

> September 1st I'd like to officially make a Hawidu CSS<http://code.google.com/p/hawiducss/>beta. What this means:
>
>    - The release will be tested based on the testing protocol<http://code.google.com/p/hawiducss/wiki/Testing>(to be completed) using the build
>    tests <http://hawiducss.googlecode.com/git/index.html> (to be completed),
>    and considered stable-ish
>    - All files will be rolled into a compressed download<http://code.google.com/p/hawiducss/downloads/list>rather than only being in source control
>    - A deployment branch<http://book.git-scm.com/3_basic_branching_and_merging.html>(probably named "releases") will be created in the git central repo
>    - The branch will get a beta 1 tag<http://learn.github.com/p/tagging.html>
>    - Work will continue in the master branch

>
> In order to make this release attractive enough for anyone to want to
> download, quite a bit needs to get done in the next 12 days:
>

>    - Review nomenclature and semantics (does the class 'hawidu' mean

>    anything? Should it be changed to 'page'?)

>    - Remove the button background image dependency and replace it with CSS
>    gradients
>    - Create pasteins<http://code.google.com/p/hawiducss/source/browse/#git%2Fpasteins>in the pending and unsupported categories (grid systems, colorful designs,

>    etc., formatted to the syntax rules)

>       - 'Borrow' common widgets from other popular frameworks [with

>       preference to GPL CSS, though licenses for style sheets are kinda BS IMO]

>    - Finish testing protocol doc and create/finish a [graded?] browser
>    support statement
>    - Make a reasonably-complete line-by-line doc
>    - Make a getting started wiki page
>    - Build out the test page
>    - Test against supported browsers
>    - Fix any browser support bugs
>    - Make a last-minute change to a new layout technique (Golden grid<http://goldengridsystem.com/>maybe? Sorry Vladimir, Joni stole your project name)

>
> In my mind I'm splitting this into the first five items in the next six
> days, and the last five in the second six. It happens that I've got
> September 1st and 2nd off from work with nothing really to do, so I might
> push the release a few days and spend the Labor Day weekend on it. This
> Sunday will likewise be devoted mostly as a hawiducss work day. If you've
> got some time in the next two weeks to help out, I'd be thrilled to have it!
>

> *Why I'm emailing / tl;dr*
>
>    1. If you have input into the framework, this would be a good time to
>    voice it
>    2. I'm struggling with an "elevator pitch". Any pointers on concisely

>    explaining why a single-page, compact-syntax, semantics and efficiency
>    focused CSS framework without all the cruft of other frameworks is a good
>    thing would be greatly appreciated. What's the sentence that sells this to
>    designer/developers?
>
> Accessibility could be a real selling point with the first crop of approved

> pasteins, so I figured Deborah <http://www.lireo.com/> might have some

> direction for accessibility styles (one for each of the WAI-ARIA roles?).

> The default styles should be attractive, and Nate<https://plus.google.com/117484395031255844960/about>has been in the making-good-looking-sites-using-CSS game for longer than

> anyone I know. And in terms of layouts and making useful CSS frameworks,

> nobody really has as much experience as Vladimir <http://www.vcarrer.com/>.