We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 32963
    • 1,732 Posts

    What do you think about the following manager page layout?

    <div id="cms_header">Header goes here</div>
    <div id="cms_menu">Menu goes here</div>
    <div id="cms_sidebar">Side/Panel bar and DocTree goes here.</div>
    <div id="cms_content">Content goes here</div>
    <div id="cms_footer">Footer goes here</div>

    The DocTree could be a simple pop-out menu option with a sticky button. If the sticky button is pressed then it will remain visible.

    Anyone has any other ideas or demo?





      xWisdom
      www.xwisdomhtml.com
      The fear of the Lord is the beginning of wisdom:
      MODx Co-Founder - Create and do more with less.
      • 25663 MODX Staff
      • 12,272 Posts
      I’m a big fan of keeping it that simple, indeed. It might also make sense to hang some extra "wrapper DIVs" and some extra "clearing DIVs/BRs" here and there too. This would give us some extra flexibility for styling that might be needed for different techniques.

      I might even contact David Shea of the CSS Zen Garden to get his input on how he’d do it differently if he had it to do over.

      The structure Raymond proposed is very solid. smiley
        Ryan Thrash, MODX Co-Founder
        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
        • 25663 MODX Staff
        • 12,272 Posts
        BTW, has anyone noticed that the manager as it’s being morphed is suspicously starting to look like a front end site? laugh
          Ryan Thrash, MODX Co-Founder
          Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
          • 32963
          • 1,732 Posts
          Quote from: rthrash at Nov 08, 2005, 09:13 AM

          BTW, has anyone noticed that the manager as it’s being morphed is suspicously starting to look like a front end site? laugh

          Yeah smiley

          Here’s the revised manager page template layout:

          <div id="cms_header">[+header+]</div>
          <div id="cms_menu">[+menu+]</div>
          <div id="cms_sidebar">[+panels+]</div>
          <div id="cms_content">[+content+]</div>
          <div id="cms_footer">[+footer+]</div>

          I’m thinking that the manager themes should be a complete separation (maybe 99%) of html code and logic. We could use placeholders to render parts of the manager as we see it fit. This also means that a user can write a plugin to replace any part of manager before it’s rendered.

            xWisdom
            www.xwisdomhtml.com
            The fear of the Lord is the beginning of wisdom:
            MODx Co-Founder - Create and do more with less.
            • 25663 MODX Staff
            • 12,272 Posts
            OHHHHHHH!!!!!!

            People. Will. Cry. For. Joy.

            laugh
              Ryan Thrash, MODX Co-Founder
              Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
              • 4018
              • 1,131 Posts
              Looks like you’re going in the right direction with the div layout there. However, we might want to take a look at the actual design of the manager first. Reason is that if the design calls for a footer to float down to the bottom then the proposed layout might be a little quirky from a CSS point of view. In alot of case, I’ve grown accustomed to wrapping most of my divs with a container div, like so:

              <div id="cms_container">
                  <div id="cms_header">[+header+]</div>
                  <div id="cms_menu">[+menu+]</div>
                  <div id="cms_sidebar">[+panels+]</div>
                  <div id="cms_content">[+content+]</div>
                  <div id="cms_footer">[+footer+]</div>
              </div>
              


              If you look at the code for the CSS Zen Garden site, you’ll notice that just about all of the divs are wrapped with a container div (except for the extra blank divs at the bottom). The benefit of this is that you can define the container div to be a relative height to the body tag, which more or less allows you to easily float a footer or some other div to the bottom of the page. There is a trick to it...mostly involves the use of the min-height definition in your css.

              At any rate, a container div is a good idea because it offers much more flexibility in the longrun. smiley

                Jeff Whitfield

                "I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
                • 32963
                • 1,732 Posts
                sounds great to me
                  xWisdom
                  www.xwisdomhtml.com
                  The fear of the Lord is the beginning of wisdom:
                  MODx Co-Founder - Create and do more with less.