Marcus (marcus132) wrote in suggestions,

S1 users can define "fallback" S2 style for tags and other non-supported features

S1 users can define "fallback" S2 style for tags and other non-supported features

Short, concise description of the idea
Users of S1 styles should be able to pick the default S2 style that is used in cases where S1 styles are not supported (such as tag aggregation).

Full description of the idea

It would be beneficial if users with custom S1 styles could choose which S2 style is used in places where S1 is not supported.

For example, when I tag entries on my custom S1 styled journal, they are aggregated on a page that looks like this:

This is clearly pulling an S2 LJ style from somewhere to build the page. There should be a way for S1 users to choose which S2 style is used to generate these pages.

Why this would be useful: As you can see in the above example, posts with large images start to run together in this style. If I could just set my default to "generator," this wouldn't happen.

An ordered list of benefits
  • A (seemingly) simple way to "throw a bone" to paid S1 users who have custom styles that are no longer fully supported.
  • Cleaner display of posts with large images.
  • An enhanced user experience for all.

An ordered list of problems/issues involved
  • None that I can see.

An organized list, or a few short paragraphs detailing suggestions for implementation
  • I imagine it as working exactly like the current S2 editor, but independently of S1. For example, paid S1 users can fully customize their S1 style, as they do now, but they could ALSO customize an S2 style as a fallback (with its own style, colors, etc).
  • Then that user can use their S1 style where it is supported, but when it's not, LJ automatically switches over to the user's S2 style.
Tags: s1, s2, styles, § no status
  • Post a new comment


    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded