Post diffs of style changes right before a code push

[zvi]

Title:
Post diffs of style changes right before a code push

Area:
styles, communications, codepushes

Summary:
The styles team is working to improve the CSS for official styles all the time. Sometimes people like the unimproved style or their customizations are based on the imperfections. We should give people more info so they can fix their customizations after code pushes.

Description:
Specifically, when a code push is going live, there should be an entry on DW-styles that explains what changes are being made to any layouts or themes. Calling it a diff is a bit of a misnomer, because I think it should include more info than that, i.e.

1) The old code
2) The new code
3) A plain English explanation of what both sets of code do, and the problem being solved by changing the code.
4) The custom CSS/changed wizard settings required to get the old behavior back on the default layout and theme.

Drawbacks: This will require more work on the part of the styles team and more warning from The Bosses that a code push is coming than is now the custom. People will still be unhappy that we're making them make a change instead of offering two versions of the code and putting them on the unchanged version.

Poll #1537 Post diffs of style changes right before a code push

Open to: Registered Users, detailed results viewable to: All, participants: 21

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
16 (76.2%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
5 (23.8%)

(Other: please comment)
0 (0.0%)

Already implemented! [WAS] Suggestion Preview: clearly delineate the preview/remove extra text

[ninetydegrees]

This is already implemented. I had some custom coding which prevented me from seeing the separation. My apologies.

---

Title:
Suggestion Preview: clearly delineate the preview/remove extra text

Area:
http://www.dreamwidth.org/site/suggest

Summary:
When you preview your suggestion I find it a bit difficult to spot what's the preview and what's a repeat of the suggestion page. There is no separation between the two.

Description:
Ideally, I'd like all the extra text starting from 'Have a way to make Dreamwidth better?' to be removed from the preview and a simple <hr> line to be added but, if that can't be done, just the line would be useful.

Here's a screenshot to show you what I mean: http://i38.tinypic.com/2j31f6c.jpg

Poll #1536 Suggestion Preview: clearly delineate the preview/remove extra text

This poll is closed.
Open to: Registered Users, detailed results viewable to: All, participants: 3

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
0 (0.0%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
1 (33.3%)

(Other: please comment)
2 (66.7%)

S2 Profile Module: Add 'Search Journal' to Interaction Icons

[ninetydegrees]

Title:
S2 Profile Module: Add 'Search Journal' to Interaction Icons

Area:
styles

Summary:
Search Journal is currently only accessible from the Profile page. Let's add it to the profile module of S2 layouts.

Description:
If you look at the homepage of dw_suggestions (http://dw-suggestions.dreamwidth.org/), there are several little icons in the profile sidebar module. I suggest 'Search Journal' be added to these so that it'd be directly accessible via any journal page, and not only from its profile page.

Edit: the username specified on the search link will depend on which journal you're viewing. When you're viewing your own journal, it'll let your search it. When you're viewing other journals/communities, it'll let you search them.

Poll #1538 S2 Profile Module: Add 'Search Journal' to Interaction Icons

Open to: Registered Users, detailed results viewable to: All, participants: 28

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
21 (75.0%)

Should be implemented with changes. (please comment)
2 (7.1%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
5 (17.9%)

(Other: please comment)
0 (0.0%)