We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 22303 MODX Staff
    • 10,725 Posts
    In response to this public thread, I have produced the following document to start us on our way to coming up with a clear and concise set of terminology to describe MODx 0.9.7 and beyond. Speak now or forever hold your peace!

    wink

    Cheers...

      • 25663 MODX Staff
      • 12,272 Posts
      Move that sucker public!
        Ryan Thrash, MODX Co-Founder
        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
        • 33337
        • 3,975 Posts
        Hmm, nice one! ... will read it in depth later tongue ...
          Zaigham R - MODX Professional | Skype | Email | Twitter

          Digging the interwebs for #MODX gems and bringing it to you. modx.link
          • 10487 MODX Staff
          • 1,535 Posts
          Makes sense to me, thanks Jason! smiley
            Garry Nutting
            Senior Developer
            MODX, LLC

            Email: [email protected]
            Twitter: @garryn
            Web: modx.com
            • 18397
            • 3,250 Posts
            Sounds good. Just out of curiosity, in 1.0 will it be possible to define all the fields as TV’s so there would be few (or no) forced fields?
              • 25663 MODX Staff
              • 12,272 Posts
              1.0 there should be no forced fields... how very anti-star trek/wars of us...
                Ryan Thrash, MODX Co-Founder
                Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                • 6726
                • 7,075 Posts
                lol Ryan, that was a good one grin

                @Mark : I sure agree with you ! This will avoid using the great HideEditor plugin when some templates don’t use default content fields smiley


                @Jason : Great ! Just what I neeeded to grasp things.
                I noticed most terms adress 3 questions really :

                • what it is
                • what it does
                • how it can be used

                And that’s a powerful communication tool !
                It will sure help make things clearer smiley
                  .: COO - Commerce Guys - Community Driven Innovation :.


                  MODx est l'outil id
                  • 27376
                  • 576 Posts
                  Thanks Jason! This is exactly what I was wanting!

                  Changing "Documents" to "Web Resources" is definitely a good move! My clients thought I was talking about pdf documents when I was teaching them :-/
                    • 6726
                    • 7,075 Posts
                    Fully in agreement here, terminology is key when you talk with clients : misunderstandings can cause high expectations and disappointments undecided Been there, learned that wink It won’t be as "critical" for "casual" MODx users but still that can help reduce redundant Qs and lighten the support load smiley

                    It’s really great to have this handy to explain what’s coming, I can’t emphasize this enough... this is helping A LOT.
                      .: COO - Commerce Guys - Community Driven Innovation :.


                      MODx est l'outil id
                      • 36541
                      • 222 Posts
                      IMO renaming "Template Variables" to "Content Fields" would help to clarify MODx lingo even further.

                      I think documents like this one should get published in the Wiki for team internal use. That would allow us to work together on concepts and internal documentation as well as collect information in one place in a structured form. I came on this idea just a few days after joining the team when I tried to catch up with the development discussion, which is spread in a number of topics.

                      After giving it a deeper thought, I think the lack of team documentation is one of the reason for the lack of the public one. At least concepts and plans for the future releases should be published for the team use in a document form. Remember, we come from different countries, cultures, professional backgrounds, and have diffrent level of English. That means not all of us, myself included, are able to understand easily what others try to communicate. Let me quote Ryan:

                      Quote from: rthrash at Sep 06, 2006, 12:30 AM

                      The biggest problem with Jason’s stuff is that no one outside of him has really seen it, and quite frankly when he describes it, it seem way too complex and intimidating for me -- I call it too "wooshy".

                      I’m far from trying to offend Jason. I’m rather trying to communicate a need for a better way of discussing the development path.

                      What you think?
                        This is the web: the only thing you know about who will come is that you don't know who will come.