?

Log in

customization's Journal [entries|friends|calendar]
customization

[ website | cust support board ]
[ userinfo | livejournal userinfo ]
[ calendar | livejournal calendar ]

[23 Nov 2002|05:15am]

acerbic
[ mood | contemplative ]

I really didn't think I'd ever make this post and mean it. The way things are right now, I can't do this anymore. My activity levels on the board have been dwindling, this past month or two, and I can't imagine that reversing at any point in time unless the wheels of administration stop running backwards. Take my privs away, because God knows I've been doing this for a year (a year as of yesterday, actually) but I surely can't be trusted to not randomly screw things up and know my own limits.

I'll miss playing with code and making people's journals uglier than I could ever imagine, but that's about it. Stress as an excuse or not, I won't miss how I've been, and seen other people be, treated the past month or so. And who knows, maybe things'll change and I'll be back. Or maybe I'll get replaced and I won't need to come back. *shrugs*

11 comments|post comment

The "changing" currents hack for paid users. [18 Nov 2002|08:26pm]

arie
We need to start noting on answers where we are describing how to "change" the currents (protected entry, only I2 and above can see it, just a reminder what the override looks like) that it will only show up on the user's LASTN page and not on their friend's friends page or the talkread/post pages. Its the only way to avoid confusion about what can and can't be done with the override.

If you're new or just generally have no idea what I'm talking about, no worries, its a wicked hack and you're better off not knowing about it. ;)
1 comment|post comment

The difficulties with S2, from a support standpoint. [19 Nov 2002|12:26am]

adcott
It is my honest opinion that a lot of the worrying that has been going on in regards to S2 is completely groundless.

Yes, this is a new way of doing things, but the basic principles applicable to customization support will remain the same. If you think about it about 95% of the customization requests that come in are solved by basic CSS tweaking. This will be no different with S2, the syntax for CSS is going to be the same, right? Joe Average is not going to bothered about the new capabilities to do complex foreach loops, all he wants is to make his links go all kick ass and blurry when you hover over them. That means all you need to do is find the bit that looks like CSS and put in your prettifying bits.

But what about the rest? what about the ones who want to create their own S2 styles? well think about how you learned to use the current style system, simple copy and paste, right? this will not be any different.more detailCollapse )

When it boils down to it, all customization support is is making things look pretty for other people. You will always be using HTML and CSS to do that. Fret not about the rest, it will not be applicable very often and in the rare occasion that it might be, we have more than a handful of programming literate people to hand to help out.

So sit back, stick on some Pink Floyd and relax, it's not going to as bad as you think. Infact it wont be bad at all, it's gonna kick ass!
25 comments|post comment

brief post regarding S2 [16 Nov 2002|09:02pm]

asciident
[ mood | curious ]

Now, before you all panic, I just wanted to bring it up for some minor discussion. :) I don't mean to scare anyone, and I'm certainly not declaring what will or will not happen in customisation or customisation support. Because I don't know what exactly Brad has in mind for S2 LJ integration or how Jesse, Arie, etc. plan on supporting it. :)

With that in mind...

Click to view a layer source.

This, basically, is the future of customisation if S2 is implemented "as is" -- that is, with any bugs/kinks ironed out and obviously adapted to LJ. That code powers a page like this (to avoid confusion, it's meant to look like a directory).

For a "prettier" example, see this layer source and what it produces.

Now, it's my understanding -- and again, this is not final or official, it's simply what I know so far -- all users will be able to use customisation "wizards"; I presume most of you are familiar with these. If you're not, please comment, and I'll do my best to explain. However, it's also my understanding that paid/perm/(presumably)EA users will be able to create their own layout layers. The kind I linked above.

How do you feel about this? Are you nervous? Think you can't do it? Or think you can? Do you want time to learn it or get a feel for it before it's introduced to The General Public? Let me hear it, I want all your thoughts on this. Don't hold back.

No one here will be berated or made to feel bad/stupid/whatever if they express views that I or others don't like or don't agree with. Please do not refrain from commenting because you feel you might "get yelled at" or anything. And please do not do that to others. I want an open, helpful and honest conversation, not a flame war. Thanks! :)

Edit: Please see this. It's an "overrides wizard" -- that's not a real name, but it's the best way I can describe it. It's sort of like modify.bml in what it does. In terms of picpix.com it's a way the user can edit the properties of the current layer they're using.

Edit 2: For a comparison of S1 to S2, see this. If it appears jumbled, refresh. Disclaimer: it is not totally technically accurate as S2 is not currently implemented for LJ, but it gives a general idea.

65 comments|post comment

Pick the new icon! [13 Nov 2002|03:16am]

arie
The long awaited poll to select the new customization icon!

Read more...Collapse )
14 comments|post comment

Fixing HowTo tutorial for Generator Realign/Resize [13 Nov 2002|02:57am]

arie
Made two changes to Generator Realign/Resize override.

1/ Adjusted percentages to equal 95% to prevent horizontal scroll bar in certain situations. It was mentioned the default is center and the horizontal scrollbar is elminated if you remove the margin-left and right values, however users may want the journal placed non-center. For ease of use by the sometimes less than expierenced, its best to leave in the margin-right/left and drop the total to 95 than explain each set of circumstances and a series of overrides.

2/ changed the table table table value to auto vice 0 to prevent bugginess in Mozilla with display of currents. If you notice oddness due to this change please drop me an e-mail at howto [at] arieanne [dot] org.
7 comments|post comment

Follow-Ups, Closings, Support & NaNoWriMo [05 Nov 2002|01:02pm]

arie
Anyone who doesn't know yet that I'm participating in NaNo hasn't been paying attention. ;) I'm sure you'll all be happy to hear I'm still on target to finish, a little ahead even. :P

Alot of Support is participating in NaNo. Basically, what this means is we're all busy writing novels instead of doing Support. Which is wonderful because the world needs more hastily written, unedited novels. On the flip side Support, and Customization is a touch neglected. A little neglect is fine, nothing in Cust is ever that earth shattering, and nobody will die if we wait a few days to tell them how to color their scrollbar or hover their mouse cursor. We've got plenty of time to catch it all up in December.

But in the interest of helping each other out and keeping the board at least somewhat tidy, I'd like to ask that we get back to the follow up of youreplied and the e-mailing of the closing lists. This will help everyone because a request doesn't always get regreened if a user comments back, so it could go an extra long time this month without being noticed. You can also use the xx that g/unk uses in its subject lines to indicate that a request is closeable. Just put a double x (xx) at the beginning of the current subject summary. Indicating something is closeable will help everyone save time by realizing they don't have to go into that request, its been handled.

Please, follow up on your youreplied filters whether you have the ability to change the subject or not. I1s and I2s can also leave ICs indicating they believe the request is closeable. Whether you are just leaving an IC or changing the subject, please indicate exactly why the request is closeable. "User applied overrides" "user changed their mind (link to a post in their journal where they say they want something else, perhaps)" etc. Do NOT worry about marking requests that are "old" as closeable. If a user hasn't applied overrides, a priv can nag them and eventually it will get closed by me.

Thanks a bunch guys! Good luck to those working on novels this month!
2 comments|post comment

Random Stats! [30 Oct 2002|03:22pm]

arie
Because they're fun!

In the last 2 months volunteers in the Customizaton category have submitted 4,941 answers (screened or otherwise).

--That averages out to just over 82 answers submitted a day.
--2,243 of those answers were submitted by volunteers who currently have no privs at all (I1, I2, or Supporthelp). Thats 45% of all submitted answers! Of course that's just answers submitted, it doesn't have anything to do with approvability. ;)
--Supporthelp privs sumbitted the second highest number of answers with 1,167.
--Followed very closely by I2s at 1,019 submitted answers.
--Nine (9) I1 privs were responsible for an amazing 512 of all submitted answers!
--There were 20 Supporthelp privs, 11 I2 privs, and 9 I1 privs submitting answers during this time.
--We have given 16 I1, 8 I2, and 3 Supporthelp privs in the last 2 months (since the beginning of interim privs).

Okay I think I've milked all the completely useless information I could out of that. It was only for submitted answers, not things like ICs, moving or touching. When you get into that stuff it gets even more nuts. ;)

The point was: YOU GUYS ROCK!
11 comments|post comment

customization's style. [29 Oct 2002|06:34pm]

arie
In effort to make it a little easier for those working on styles for us, I've removed all of the previous overrides and the custom color scheme.

Feel free to suggest a color scheme. Just please, for the love of little saints, no orange.
4 comments|post comment

CSS and hyperlinks, making them "pretty" without making them incorrect. [27 Oct 2002|06:32pm]

arie
If you come across a user who has an a{} definition it's important that you look at all of their hyperlink overrides very carefully before merging any of them together. In some cases the a{} definition can be merged with another definition (such as a:hover{}) but in many cases it can't be merged with other definitions. In order to determine what can and can't be merged you have to know what each of the hyperlink definitions do.

The a{} definition applies to ALL links whether they have been visited or not.

The a:link{} definition applies only to links that are unvisited.

The a:hover{} definition applies only when the mouse cursor "hovers" over the link.

The a:visited{} definition applies only to visited links.

The a:active{} definition applies only to the currently active link.

What can and can't be merged.Collapse )

Its important to note that in all of the above examples the overrides given for "Before" and "After - Correct" will do what the user wants. Do not pass up an otherwise acceptable answer just because some of the hyperlink definitions aren't merged as fully as they could be. The important thing is that they work and that they are correct (they are correctly written and they do everything the user wants to do without leaving something out).

My intent here was to let everyone know about some common misconceptions I'd been seeing that could lead to a user's overrides being rewritten in such a way that they no longer function the way they wanted, not to say that we should reject answers that aren't merged in the ways described in the above examples. As long as the overrides are well written and function properly that's all we're really after. Full merging is nice, but not something that --by itself-- should cause you to pass over an answer.
7 comments|post comment

We've got no style. [27 Oct 2002|04:12pm]

arie
No really. We don't. customization is utterly style-less.

I'm not overly fond of the color scheme of our current style, and to be honest since its customization I think we need to show off a bit. Something more personalized, with links to all the friendly Customization related stuff, and perhaps to the other support comms.

Something....more "us" ;)

So here's your chance to really show off. Submit a style for customization!

Requirements:
--Must be for the LASTN view.
--Must be CSS based.
--Must be compatible with all common browsers.
--Must be as standards compliant as possible. (I'm not going to nitpick here as long as it works for all the common browsers.)
--Must contain links to all relevant customization info. (Userinfo, memories, calendar.)
--Must contain links to all relevant Customization info. (Support office, lj_support, you replied for Cust, support board filtered for Cust, any others you feel are relevant (such as howto and/or its memories).)
--Must be fun and creative.
--Must be original. (By original I mean not a carbon copy of a current system style with a few minor changes, you can recycle an old custom style of yours that you think might work well for customization).
--Must be willing to release all future claims of copyright (implied by submitting your style as outlined below), credit will be given to the "winner" in the userinfo of the community as well as via small text at the bottom of the style if the author includes such in their style.

Can optionally contain:
--Links to any other support related communities. (ie: helpscreening, supportlounge, support_general, support_upi, support_clients, support_interim, privchange)
--Styles for the other three views (DAY, FRIENDS, CALENDAR)

How to submit:
--E-mail all submissions to arieanne[at]livejournal[dot]com.
--Include the customview.cgi link(s) with the customization community in the username place.
--Include a link the style code itself.
--Include your user name.
--Include any other information you would like to share about the style.
--You can sumbitt more than one style in your e-mail (there's no limit on submissoins), just include all the above information for each style.

Deadline:
November 30th, at which point we will have a poll to determine which style will be selected. (Consider it a way to procrastinate/take a break from your NaNoWriMo novel. ;)

Come on, you know you want to.

Crossposted to supportlounge.
5 comments|post comment

Displayed Name vs. Displayed Title [11 Oct 2002|05:54pm]

braindrain
I've seen a lot of people doing this recently, screened volunteers and supporthelps alike, so I wanted to just bring it to everyone's attention.

This override from howto does not, I repeat, does not change the title in the first row of the first table in Generator.

It changes the displayed name. By name, I mean the lone %%user%% out in the center of the main cell in the first table, not the "%%user%%%%user-'s%% LiveJournal Entries" in the top row to the left.

So please, please stop linking to this when someone asks to change their title and/or specify "John Doe's Journal" as what they want to change. I will not approve you (unless our admin says otherwise).
4 comments|post comment

Friends, Romans, Custymen (or women, as the case may be) [08 Oct 2002|02:00am]

arie
My review queue is currently empty. Well not empty, I have one "quickie" left, but I'll finish that in under an hour tomorrow. If you haven't been reviewed in 3 or more weeks in Customization, e-mail me your links! (arieanne [at] livejournal [dot] com... *closes eyes and crosses fingers* I will not be harvested, I will not be harvested, I will not be harvested...)

Gracias.

PS: For the love of Pete, include your LJ username in the subject. Muchas gracias.
2 comments|post comment

Update the howto tutorial for *_DATE_FORMAT [07 Oct 2002|02:21pm]

arie
http://www.livejournal.com/talkread.bml?journal=howto&itemid=11414

At xtremesaints suggestion, I've updated the tutorial to reflect which system styles have both the time and date in the *_DATE_FORMAT and which have only the time in the *_DATE_FORMAT, the date being in the *_NEW_DAY variable and non-overrideable by free users.
4 comments|post comment

Community Memories Updated [06 Oct 2002|02:09pm]

arie
I've updated the community memories.
2 comments|post comment

A quick note on not logged in requests in Customization. [06 Oct 2002|01:25pm]

arie
If a user isn't logged in when they are making a request in customization, they need to be told to log in before we can answer their request. Please review the Policy & Procedures post for Supporthelp Privs, Sections I & II for more information on this.

Basically, if a user isn't logged in, or is request help for a friend, the best way we can help them is if they are logged in or if their friend opens their own request. Not just because we need to see their journal ourselves, or speaking with the person directly causes less confusion, but because it will eliminate requests that are really for UJ or DJ. We don't do Customization support for UJ or DJ; they have their own Customization support.

Customization isn't like g/unk where a user might have a legitimate reason not to be logged in. In customization they are requesting help with customizing their LiveJournal. Non-users don't make requests for how to add a custom scrollbar or background, they don't have a journal to customize, after all. ;)

Most of the time the user probably forgot they weren't logged in. That's fine, a polite comment to please resubmit while logged in --along with a brief explanation of why we can best help them that way-- will be great. This way we can actually check back to see if they've applied the override or had trouble, and we can offer them specific advise, while still eliminating requests from users of other services. If someone has both an LJ and a UJ or DJ, that's fine, but its not our responsibility to offer support for 350,000+ other users when we have 720,000+ of our own to worry about. ;) Having the user logged in helps us help them. A good thing all around.

Thanks so much guys, you're the best!
8 comments|post comment

Monster Guide Suggestions [09 Sep 2002|08:22pm]

braindrain
In my large amounts of free time over the next week or so, I plan on writing a monster of a guide for how to more efficiently answer in Customization.

Often, volunteers get lost in the sea of links to HowTo, merging, and actual guidelines on how to answer what. What I need from all of you are things you would like to see addressed in this guide. :) This will be a more complex version of my first two posts.

A few things I know I want to discuss are: how CSS works (more specifically how it ties in with a majority of the system styles), the style system itself (how the properties and variables work together, as well as how overrides actually function), how to be more psychic when dealing with requests, and I'll probably go back over a few basic procedures.

This is all in an effort to make Customization easier to jump into. As it stands, it can sometimes be quite menacing and volunteers sometimes shy away from Cust and run towards G/U. ;)

This is where you come in. (Largely screened volunteers, but privs aren't barred from commenting. :p) What did you find most confusing when you began volunteering in Cust? What do you still sometimes have problems with? Name one or two specific areas that you think I should focus on that you think will help you and/or other volunteers improve the most.

Thanks! :)
22 comments|post comment

Customization Policies and Procedures [04 Sep 2002|02:43pm]

arie
I have gathered up all the various policy and procedure posts regarding Customization that have been made and put them in one place. Hopefully this will make it easier to keep up with things in the future, since as new policies and guidelines are decided, I can just add them to the appropriate posts.

Just to clarify, all the items included in all three of the posts below have been discussed at some point previous to this. I went back through every post in learn_support, customization, and lj_support to get all of this information. There were many items that we had all been letting slide recently and this should clarify those points. But as I said none of these items are new; if you have something to add then please let me know, but none of the items listed are removable at this point.

The only new item is the bandwidth theft item which is relatively new and isn't really a debateable issue since it involves ToS.


I've divided them up by level of privs in descending order. Each level of privs has its own post; you can make any or all of the individual posts memories. However, this Table of Contents post will be the only one that is placed in the community memories to ensure that new privs and volunteers see all of the information available as it applies to them.

You can find all of these posts together without the Table of Contents here. Supporthelp privs should read everything from the top down. Interim privs should read everything from the middle down (where the "all privs" mark is) and screened volunteers without interim privs should read from the all volunteers mark down.

A couple of terms to understand.
supporthelp privs
refers to those with full or full category privs
interims or interim privs
refers to those with either I1 (supportviewscreened, supportmakeinternal) or I2 (I1, supportviewinternal, supportmovetouch) interim privs
screened volunteers
refers to those who do not have any level of privs yet: note that those with interim privs are also still "screened" since they cannot approve answers, but for the purposes of these posts they are referred to separately as interims

>>S U P P O R T H E L P   P R I V S<<

>>A L L   P R I V S   ( I N C L U D I N G   I N T E R I M S )<<

>>A L L   V O L U N T E E R S   ( I N C L U D I N G   S C R E E N E D )<<
3 comments|post comment

------ALL VOLUNTEERS (INCLUDING SCREENED)------ [02 Sep 2002|02:00pm]

arie
first and doneCollapse )

testing overridesCollapse )

overrides vs. stylesCollapse )

bandwidth theft & copyright violationCollapse )

requesting reviewsCollapse )

------ALL PRIVS (INCLUDING INTERIMS)----- [02 Sep 2002|02:00pm]

arie
internal commentsCollapse )

duplicate requestsCollapse )

supporthelp vs. interim dutiesCollapse )

navigation
[ viewing | most recent entries ]
[ go | earlier ]