We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 27708 MODX Staff
    • 2,502 Posts
    I know this is a bit of a poke but why not just make the base font size larger. Many designers have a tendency to use tiny fonts.

    One another note. If my client wants a splash page with a 3 minute flash presentation before people can enter a site I will tell them no.

    You occassionally have to tell your client that they are wrong BUT you have to tell them why. If you don’t know why something is a bad idea your client will think that you are being a pain. If you can carefully explain that to do so will actually impair the user experience and slow down the process to the sale, they’ll see your point and respect you for being an expert. On the specific point of font sizing these size switchers are going the way of the dodo as now most people are using reasonably sized type on screen. Rarely is text too large it is almost always too small, hard to read and looks like a big grey blob when you squint.

    Best to you,

    Jay
      Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub
      • 26435
      • 1,193 Posts
      Quote from: smashingred at Dec 06, 2007, 08:04 AM

      One another note. If my client wants a splash page with a 3 minute flash presentation before people can enter a site I will tell them no.
      I admire your cajoñes Jay! I hate flash as much as or more than the next guy, but It would take me a minute to let someone know that using a flash splash would be a f***ing nightmare for me to design and a PITA for every single person who views the site.

      -sD-
      Dr. Scotty Delicious, DFPA.
        Husband, Father, Brother, Son, Programmer, Atheist, Nurse, Friend, Lover, Fighter.
        All of the above... in no specific order.


        I send pointless little messages
        • 27708 MODX Staff
        • 2,502 Posts
        Dr. Scotty Delicious,

        I test, research and try to learn what works for clients.

        If a client or prospect gets a case of instant-expertitis I can generally justify a refusal through cold-hard facts or at least some valid industry best-practices. I have had significant success consulting with my clients as an expert (at least at HTML, Web Design and elements of usability and small business marketing). Telling clients no is doing them a favour. If they want to have something that I don’t want to put my name on I won’t even take on the client. Almost all my clients rely on my knowledge and expertise to make their site work and therefore yield to most decisions I make on the direction of a project. If they were a web expert they wouldn’t need me. If they were a marketing expert they wouldn’t need a website as they would already have one that works.

        Now to back on topic: After posting about the font sizes I came across a site not five minutes after I posted that about the sizes. The base type size was not bad so I personally think it extraneous.

        Cheers,

        Jay
          Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub
          • 34162
          • 1 Posts
          Quote from: Pepest at Dec 06, 2007, 05:40 AM

          Quote from: sottwell at Dec 06, 2007, 05:15 AM

          It should work when the snippet is called uncached [!...!]

          I’ve already tried but when the snippet call is in this way simply it doesn’t work, the whole snippet. The placeholder is ignored in the css code.
          Sorry, forgot to mention that indeed the snippet should be called uncached embarrassed

          You should place this call on the first line of your html-code (usually the template), not in your css code.

          *Edit*
          Don’t want to get involved in the discussion about fontsize, but just wanted to let you know that my client is not the actual client itself, but the designer who has agreed to make the font sizeable. She has just asked me to build the site in MODx.

          Since I didn’t know how to go on with this issue, I thought I’d ask on this forum. Thanks to this wonderful community I got my solution very quickly. That’s why I love using MODx so much!
            • 21257 MODX Staff
            • 730 Posts
            It’s great to have so many perspectives on something like this.
            Personally, I rarely get to interface with the end client at all. I get 99% of my work from web shops who are in that position to advise the client on what they think is best. And everyone has a different style and a different set of preferences, so I’ve learned to roll with it most of the time. However, when I feel strongly about a particular issue, I will raise it, and sometimes my opinion becomes part of the consultation process, sometimes it doesn’t. I’m often called into the process after such decisions have been made.
            So when presented with a coding problem, I have much less of a "why would you want to do that anyway" filter happening than many of you.
              Mike Schell
              Lead Developer, MODX Cloud
              Email: [email protected]
              GitHub: https://github.com/netProphET/
              Twitter: @mkschell
              • 23019
              • 27 Posts
              When I call in my first line uncached ([!...!]) the placeholder ([+...+]) which is in my css code, is set empty.

              I’ve understood well, no? It doesn’t work then or only for me?
                • 34162
                • 1 Posts
                Quote from: Pepest at Dec 06, 2007, 11:35 AM

                When I call in my first line uncached ([!...!]) the placeholder ([+...+]) which is in my css code, is set empty.

                I’ve understood well, no? It doesn’t work then or only for me?

                You should not set the placeholder in your css. Instead, place something like
                <style>
                   #content {font-size:[+fontsize+]px;}
                </style>

                in the html-code of your template, just above the </head> tag.
                  • 23019
                  • 27 Posts
                  Quote from: WeBe at Dec 06, 2007, 11:40 AM

                  Quote from: Pepest at Dec 06, 2007, 11:35 AM

                  When I call in my first line uncached ([!...!]) the placeholder ([+...+]) which is in my css code, is set empty.

                  I’ve understood well, no? It doesn’t work then or only for me?

                  You should not set the placeholder in your css. Instead, place something like
                  <style>
                     #content {font-size:[+fontsize+]px;}
                  </style>

                  in the html-code of your template, just above the </head> tag.

                  I didn’t explain well, but it’s how I’ve set it, exactly as you say. And using, for example, firebug addon of Mozilla, the code between <style> tags are:

                  body {
                  font-size:px;
                  }

                  Something that doesn’t happen when I call the snippet on this way [[fontsizer]], but only works once.
                    • 21257 MODX Staff
                    • 730 Posts
                    Just to be sure, you have the question mark after the name of the snippet?
                    [[fontsizer? ]]
                    

                    or
                    [!fontsizer? !]
                    

                      Mike Schell
                      Lead Developer, MODX Cloud
                      Email: [email protected]
                      GitHub: https://github.com/netProphET/
                      Twitter: @mkschell
                      • 23019
                      • 27 Posts
                      Quote from: netProphET at Dec 07, 2007, 07:53 AM

                      Just to be sure, you have the question mark after the name of the snippet?
                      [[fontsizer? ]]
                      

                      or
                      [!fontsizer? !]
                      



                      I tried with both (with and without question mark).