![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
Entry tags:
CFV for documentation people!
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.
...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.
no subject
THERE WE GO.