Style:WishList - Revision history

Mrcoolbp: removed "not until reskin" in multiple places, I think we are nearing the "reskin" phase

2014-06-10T04:26:46Z

removed "not until reskin" in multiple places, I think we are nearing the "reskin" phase

← Older revision		Revision as of 04:26, 10 June 2014
Line 2:		Line 2:
	===Phase 1 Repair List===		===Phase 1 Repair List===
	*'Read More' link and 'n Comments' needs '''font size definition changed to em''' from points, as it is unreadable on small devices such as phones. All links in the center column should be checked for this. (I bilieve that the new css will fix this -EP)		*'Read More' link and 'n Comments' needs '''font size definition changed to em''' from points, as it is unreadable on small devices such as phones. All links in the center column should be checked for this. (I bilieve that the new css will fix this -EP)
	*The Comments under articles need to be brought in line with the center column and not spill over to the right column. Otherwise this results in unacceptable whitespace when article summaries are short. (This would leave ~~whit~~ space on the side then -EP ... need to discuss further -MB )		*The Comments under articles need to be brought in line with the center column and not spill over to the right column. Otherwise this results in unacceptable whitespace when article summaries are short. (This would leave white space on the side then -EP ... need to discuss further -MB )
	*When posting comments: Both the '''original article must appear at the top''' and '''the parent thread must appear also''', whereas currently this does not occur. Very disorientating.(Still a problem when first post to an article)		*When posting comments: Both the '''original article must appear at the top''' and '''the parent thread must appear also''', whereas currently this does not occur. Very disorientating.(Still a problem when first post to an article)
	*We need to have a single column view for phones/narrow mobile devices with reduced functionality ~~- working on a schematic for this (Not until reskin)~~		*We need to have a single column view for phones/narrow mobile devices with reduced functionality
	*Mobile device viewing~~: nothing until reskin.~~		*Mobile device viewing


	===Typography===		===Typography===
	~~Nothing for now until reskin.~~

	===Color===		===Color===
	~~Nothing for now until reskin.~~

	===Art===		===Art===
Line 21:		Line 21:

	===Theming===		===Theming===
	~~Nothing until reskin.~~

	===Usability===		===Usability===

Mrcoolbp: removed: "*The comments list should be collapsible/expandable using CSS. Different CSS for different threshold views...." comments expanding added in latest code deploy already

2014-06-10T04:24:24Z

removed: "*The comments list should be collapsible/expandable using CSS. Different CSS for different threshold views...." comments expanding added in latest code deploy already

← Older revision		Revision as of 04:24, 10 June 2014
Line 5:		Line 5:
	*When posting comments: Both the '''original article must appear at the top''' and '''the parent thread must appear also''', whereas currently this does not occur. Very disorientating.(Still a problem when first post to an article)		*When posting comments: Both the '''original article must appear at the top''' and '''the parent thread must appear also''', whereas currently this does not occur. Very disorientating.(Still a problem when first post to an article)
	*We need to have a single column view for phones/narrow mobile devices with reduced functionality - working on a schematic for this (Not until reskin)		*We need to have a single column view for phones/narrow mobile devices with reduced functionality - working on a schematic for this (Not until reskin)
	*The comments list should be collapsible/expandable using CSS. Different CSS for different threshold views. This will reduce page reloads and make browsing more pleasant. (Not until reskin)
	~~These are more minor cosmetic problems:~~
	*Mobile device viewing: nothing until reskin.		*Mobile device viewing: nothing until reskin.

Mrcoolbp: /* Wish List and Identified Problems */ removed "The entire user preferences section should be merged into a single large page." paulej72 has been overhauling the prefs, but I don't think we'll merge to one page

2014-06-10T04:23:05Z

Wish List and Identified Problems: removed "The entire user preferences section should be merged into a single large page." paulej72 has been overhauling the prefs, but I don't think we'll merge to one page

← Older revision		Revision as of 04:23, 10 June 2014
Line 4:		Line 4:
	*The Comments under articles need to be brought in line with the center column and not spill over to the right column. Otherwise this results in unacceptable whitespace when article summaries are short. (This would leave whit space on the side then -EP ... need to discuss further -MB )		*The Comments under articles need to be brought in line with the center column and not spill over to the right column. Otherwise this results in unacceptable whitespace when article summaries are short. (This would leave whit space on the side then -EP ... need to discuss further -MB )
	*When posting comments: Both the '''original article must appear at the top''' and '''the parent thread must appear also''', whereas currently this does not occur. Very disorientating.(Still a problem when first post to an article)		*When posting comments: Both the '''original article must appear at the top''' and '''the parent thread must appear also''', whereas currently this does not occur. Very disorientating.(Still a problem when first post to an article)
	*The entire user preferences section should be merged into a single large page. (?)
	*We need to have a single column view for phones/narrow mobile devices with reduced functionality - working on a schematic for this (Not until reskin)		*We need to have a single column view for phones/narrow mobile devices with reduced functionality - working on a schematic for this (Not until reskin)
	*The comments list should be collapsible/expandable using CSS. Different CSS for different threshold views. This will reduce page reloads and make browsing more pleasant. (Not until reskin)		*The comments list should be collapsible/expandable using CSS. Different CSS for different threshold views. This will reduce page reloads and make browsing more pleasant. (Not until reskin)

Mrcoolbp: /* Art */

2014-06-10T04:21:27Z

Art

← Older revision		Revision as of 04:21, 10 June 2014
Line 18:		Line 18:

	===Art===		===Art===

			*new logo
			*new buttons for expand/collapse comments
			*new friend/foe/freak/etc. icons

	===Theming===		===Theming===
	Nothing until reskin.		Nothing until reskin.

Mrcoolbp: removed "add martyb's links" comment as his links were integrated into the about page already

2014-06-10T04:20:21Z

removed "add martyb's links" comment as his links were integrated into the about page already

← Older revision		Revision as of 04:20, 10 June 2014
Line 9:		Line 9:
	These are more minor cosmetic problems:		These are more minor cosmetic problems:
	*Mobile device viewing: nothing until reskin.		*Mobile device viewing: nothing until reskin.
	*We need martyb's links made live on the website: [http://soylentnews.org/~martyb/journal/ to be found in his journal entry here.]

	===Typography===		===Typography===

50.97.94.34: /* Wish List and Identified Problems */

2014-04-12T12:09:26Z

Wish List and Identified Problems

← Older revision		Revision as of 12:09, 12 April 2014
Line 1:		Line 1:
	=Wish List and Identified Problems=		=Wish List and Identified Problems=
	===Phase 1 Repair List===		===Phase 1 Repair List===
	~~These are what needs to happen as a priority on the current site:~~
	*'Read More' link and 'n Comments' needs '''font size definition changed to em''' from points, as it is unreadable on small devices such as phones. All links in the center column should be checked for this. (I bilieve that the new css will fix this -EP)		*'Read More' link and 'n Comments' needs '''font size definition changed to em''' from points, as it is unreadable on small devices such as phones. All links in the center column should be checked for this. (I bilieve that the new css will fix this -EP)
	*'Yesterday's News' needs to not have < and > surrounding it as this is confusing. It should either have square brackets or none at all.
	*The Comments under articles need to be brought in line with the center column and not spill over to the right column. Otherwise this results in unacceptable whitespace when article summaries are short. (This would leave whit space on the side then -EP ... need to discuss further -MB )		*The Comments under articles need to be brought in line with the center column and not spill over to the right column. Otherwise this results in unacceptable whitespace when article summaries are short. (This would leave whit space on the side then -EP ... need to discuss further -MB )
	*When posting comments: Both the '''original article must appear at the top''' and '''the parent thread must appear also''', whereas currently this does not occur. Very disorientating.(Still a problem when first post to an article)		*When posting comments: Both the '''original article must appear at the top''' and '''the parent thread must appear also''', whereas currently this does not occur. Very disorientating.(Still a problem when first post to an article)

50.97.94.34: /* Phase 1 Repair List */

2014-04-12T12:08:39Z

Phase 1 Repair List

← Older revision		Revision as of 12:08, 12 April 2014
Line 5:		Line 5:
	*'Yesterday's News' needs to not have < and > surrounding it as this is confusing. It should either have square brackets or none at all.		*'Yesterday's News' needs to not have < and > surrounding it as this is confusing. It should either have square brackets or none at all.
	*The Comments under articles need to be brought in line with the center column and not spill over to the right column. Otherwise this results in unacceptable whitespace when article summaries are short. (This would leave whit space on the side then -EP ... need to discuss further -MB )		*The Comments under articles need to be brought in line with the center column and not spill over to the right column. Otherwise this results in unacceptable whitespace when article summaries are short. (This would leave whit space on the side then -EP ... need to discuss further -MB )
	*When posting comments: Both the '''original article must appear at the top''' and '''the parent thread must appear also''', whereas currently this does not occur. Very disorientating.		*When posting comments: Both the '''original article must appear at the top''' and '''the parent thread must appear also''', whereas currently this does not occur. Very disorientating.(Still a problem when first post to an article)
	*The same goes after moderation. There should not be separate notification pages that then link to ~~the original page. Notifications should appear conveniently at the top or bottom of the working page.~~		*The entire user preferences section should be merged into a single large page. (?)
	*The entire user preferences section should be merged into a single large page.		*We need to have a single column view for phones/narrow mobile devices with reduced functionality - working on a schematic for this (Not until reskin)
	*We need to have a single column view for phones/narrow mobile devices with reduced functionality - working on a schematic for this		*The comments list should be collapsible/expandable using CSS. Different CSS for different threshold views. This will reduce page reloads and make browsing more pleasant. (Not until reskin)
	*The comments list should be collapsible/expandable using CSS. Different CSS for different threshold views. This will reduce page reloads and make browsing more pleasant.
	These are more minor cosmetic problems:		These are more minor cosmetic problems:
	*~~Bottom right of the right column there are some included lower-borders of non-existent boxes. They need removing (quick and dirty css fix is on its way -EP)~~		*Mobile device viewing: nothing until reskin.
	*We need a more consistent font that looks the same on different browsers, need to make some mockups and see what people think (Another fix is on its way with a font stack that has friendly fonts for all major systems -EP).
	*The left bottom window needs to have some kind of links of interest, and not a message "put links here" (I have roughed-out something for this. Not sure how to submit. -martyb)
	*The word slashdot needs to be removed from the face of the earth, including soylentnews.org
	*The view on mobile phones is good for center column, microscopic for side columns. This is not critical yet but we need to start work soon on a mobile devices interface, taking note that the size of the pointer (finger) is massive and clumsy compared to a mouse cursor from the POV of user interface design.
	*We need martyb's links made live on the website: [http://soylentnews.org/~martyb/journal/ to be found in his journal entry here.]		*We need martyb's links made live on the website: [http://soylentnews.org/~martyb/journal/ to be found in his journal entry here.]

50.97.94.34: /* Theming */

2014-04-12T12:05:40Z

Theming

← Older revision		Revision as of 12:05, 12 April 2014
Line 26:		Line 26:
	===Art===		===Art===
	===Theming===		===Theming===
	~~<ul>~~		Nothing until reskin.
	~~<li>User selectable themes</li>~~
	~~</ul>~~
	===Usability===		===Usability===
	<ul>		<ul>

50.97.94.34: /* Color */

2014-04-12T12:05:24Z

Color

← Older revision		Revision as of 12:05, 12 April 2014
Line 22:		Line 22:

	===Color===		===Color===
	~~<ul>~~		Nothing for now until reskin.
	~~<li>Red theme is ok, however color contrast is excessive on wide gamut displays, especially some Apple devices~~. ~~(Frogblast and MrBluze are working on mockups / test designs for replacing the current color scheme)</li>~~
	~~</ul>~~

	===Art===		===Art===

50.97.94.34: /* Typography */

2014-04-12T12:05:09Z

Typography

← Older revision		Revision as of 12:05, 12 April 2014
Line 19:		Line 19:

	===Typography===		===Typography===
	~~The fonts are "not right", but to elaborate:~~		Nothing for now until reskin.
	*Some people consider the typeface to be too 'generic' and does not give the site a unique look.
	*Because of differences in rendering fonts between operating systems and browsers, there is inconsistency in font weight and kerning. (see below -EP)
	*We need to trial different font sets and ordering of fonts and decide on the optimal set. (upcoming css changes have this font-family: Verdana, Geneva, "Bitstream Vera Sans", "DejaVu Sans", sans-serif; this is a test, but the stack is Linux friendly -EP)

	===Color===		===Color===