CFV for documentation people!

[ysobel]

Very soon*, there will be a stable** version of Core2 available on Dreamwidth. Which is totally awesome (*sends lots of cookies to the styles team*) and means that people can start customizing their journals more!

...it also means that we can start the process of documenting, so people know what's customizable and how to do it. Some of the things I'm planning are on a "would be nice eventually but not priority" list, but some of the things ... need to be done as soon as possible.***

Specifically, and pretty much in order of priority, we want to have:

1) CSS documentation (what classes are available in core2 / system styles)

2) Properties, aka the things that can be set through the wizard

3) Functions, part the first: Core2 functions that are specifically designed to be overridable by style writers

In all cases, these will have descriptions along with each item: not just listing what exists, but describing what it does.

If you would like to help, please comment to this post with:

* your name
* your email (or a way to contact you)
* which of the three area(s) you are comfortable with.

You don't need to know everything, I promise! (Styles docwork, like a lot of the rest of Dreamwidth, operates under the principle that a bunch of people working on a project is kind of like putting together a jigsaw puzzle; you have one piece, someone else has the one next to it, and so on.) It's fine to list more than one (especially since probably anyone who can figure out functions can also figure out properties) or to list all three or to only list one. Mainly, I don't want to have a CSS-only person working on raw S2 code (or, y'know, end up with someone who can translate S2 but doesn't know CSS all that well going wtf at the list of CSS classes).

<3

#

Footnotes:

* with the next major code push. in theory, at least.

** the current version is unstable, which you probably have noticed if you've used it at all.

***By magic, preferably, but unfortunately that's not an option.

Comments

[ex_lily871]

Lily
reach.galanthus@gmail.com (or Lily in IRC)
I'm good with CSS.

[katieastrophe]

Katie
katie@xugglybug.co.uk or tajasel on IRC
very comfortable with properties. to a lesser extent, CSS documentation as well.

[rho]

You might want to post this (or a link to this) to dw_docs as well. There have been a bunch of people who have been asking me about getting involved in doc work, and I've been telling them to keep watching the comm for announcements of opportunities.

[gypsy]

I have a potentially very stupid question for you.... is S1 (specifically 'Generator') going to be available on DW? I know it's archaic as far as styles go, but some of my favorite layouts are coded for S1.

[damned_colonial]

damned_colonial, skud@infotrope.net, anything.

[seleneheart]

seleneheart
raederleofan @ gmail.com
I know CSS the best probably.

[highlander_ii]

* Highlander II
* highlander (dot) ii (at) gmail (dot) com
* #2 - Properties

[ysobel]

Will do, thanks <3

[ysobel]

It's not a stupid question. :) S1 as a style system will not be on DW, no; there are a *lot* of features it doesn't support, and the way it's designed means that any future sorts of new content will be even harder to implement. S2 has been redesigned to be a *lot* more usable, though, and some LJ styles -- including (S2) Generator -- can be ported to DW (with some amount of tweaking; I really don't know whether it will be available as one of the official styles though, and S2 Generator isn't exactly the same as S1.

(Personally, I'm a little sad that S1 will not exist, even though I completely understand the reasons why.)

[gypsy]

Thanks for letting me know I totally understand, and actually I suspected LJ would have done it a long time ago. I'm surprised they haven't.

No worries, though. I can probably convince a friend to recode it for me, and if not, perhaps I'll find a new one I like better. You never know =)

[katemonkey]

Me + CSS = True Love

[katemonkey]

Sorry, because I'm dumb:

[Error: Irreparable invalid markup ('<user=katemonkey>') in entry. Owner must fix manually. Raw contents below.]

Sorry, because I'm dumb:

<user=katemonkey>
dreamwidth at dymphna.net

[katemonkey]

nuts.

katemonkey

THERE WE GO.

[liv]

Me, please. livredor [at] justemail [dot] net.

I'm on the S2 team so can work with pretty much anything, but probably better at S2 code than CSS. So my preference is for 3.

[cimorene]

Cim
cimness @ gmail
I'd love to help. Comfortable with CSS; getting into properties, but not too experienced there yet. Willing and eager to learn and I have lots of time on my hands, though!

[seperis]

Seperis
Seperis@gmail.com
Properties and CSS, I think? I've been pulling it apart piece by piece from the core page for the last day and documenting (for myself) what each does and where it shows up in the css and functions.

[ninetydegrees]

ninetydegrees
PM here on DW.
I'd be most comfortable with #2.

[alsatia]

* Dana
* my username at gmail.com
* I'm ok with any of it, and based on the other comments it looks like I'd be most useful working on functions.

[quivo]

Quivo
quivo at pinqury dot com
I'm good with CSS, and am okayish with properties.

[hatman]

I can't code. Just don't have the head for it. It comes out clunky and ineffectual. But documentation I can do. As long as I have a way to understand what I'm trying to document. I can also do editing. I'm not part of the team, but I'm happy to help. If that translates into anything useful, let me know.

Name: Paul
Email: pgwfolc at netscape dot net or zennerd at comcast dot net

[nextian]

I'm Emma (nextian@gmail.com) and I'm groping my way through building a Core2 style as we speak. I'm comfortable with CSS and I can probably explain what a property is, due to sheer trial and error.

[delight]

Rue
pseudelight@gmail (or Rue on IRC) (or private message on DW)
Comfortable & at home with CSS, familiar with properties if needed

[quiara]

This name at gmail.

I understand CSS and I'm tentatively taking apart the other things. But like hatman, if I have a way to understand it, I can document it. And I'm a fast learner, so I'd be happy to pick it up as I go.

[gamine.livejournal.com]

I would love to help out with CSS as much as possible, as well as any designs that aren't totally compatible with the mac resolutions (I pushed LJ to speed up the design bug fixes for Safari in 2006).

My email address is my LJ name [at] livejournal.com

[matgb]

Mat, matbowles@gmail.com

Can definitely help with 1) (will be writing up what I'm learning anyway), can probably do stuff on 2), and would like to learn a lot of 3) so might be good to proofread for idiot-proofing, etc.

I've already hacked Zesty to death and back, really dislike Negatives, have moved to Core2 basic which I need to document the CSS for in order to theme it myself and put the sidebar on the right, etc.

So LMK what I can do, basically—if no one is doing a graphical pic of the classes I can work out how to do it, but my graphics skills are poor so if someone better than me can do it that's great.

[msblackeyeliner.livejournal.com]

Lauren
lawryn182@yahoo.com
I'm good with CSS and some properties/functions. I learn quick too! :D

[spydielives]

Are you still looking for volunteers?

spydielives [at] gmail [dot]

or

amy [at] spydielives [dot] com

I have written several S2 component and expressive custom styles (for myself) over on LJ. Anything I can't already write about in detail, I will learn quickly!

[maiden]

Still looking for people? I'd really like to help out with styling etc - journal themes, front page, anything! I glanced around Bugzilla, but frankly it's always confused me xP

brandnewaquarium at gmail dot com

I can do most things with CSS, and I can do some functions, though with that there may need to be a little bit of hand-holding, to a certain extent.