I like the idea of splitting up the big page into smaller and cleaner pages. If both can co-exist I'm definately in favour of it.

By doing this split you can also easier document the features on the particular Settings page without creating a mess. You could also create an index that lists page by page with the features you find in it, with links taking you directly to the setting. That at least I would find easier than scrolling a big page. Those who don't can use the old big page, if that can co-exist.

I think creating a (possibly index) frontpage for the settings is a good thing. It makes it easier to get an overview, find a feature easily, and allows you to easier reorganize without confusing us users too much. It's also a natural place to advertise new settings.

I think the old settings system unnecessarily messy to navigate, and really welcome this effort to make it easier.

Just my thoughts,
ihb

PS. It's quite likely I'm just plain ignorant about some features and/or documents regarding this.

See perltoc if you don't know which perldoc to read!


In reply to Re: Renovating User Settings by ihb
in thread Renovating User Settings by demerphq

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.