We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 42901 ☆ A M B ☆
    • 73 Posts
    Would it be right or wrong to have two contexts set up?

    Here is my thought/idea:

    Web
    All the pages which hold your website pages shown by your navigation

    • home page
    • products
    • services
    • about us
    • contact us

    Other
    All the non-menu displayed items that are key to a website

    • Privacy Policy
    • Sitemap
    • 404 Page
    • Terms and Conditions

    Is this totally unnecessary since you can hide from menus? How do you typically do this? [ed. note: adagency last edited this post 13 years, 6 months ago.]
      Woodlands Ad Agency
      Our blog should NOT be read by anyone....EVER http://woodlandsadagency.com/blog/
      ...Don't say we didn't warn you.
      • 3749
      • 24,544 Posts
      I typically avoid contexts unless I absolutely need them because they can introduce a host of difficult-to-solve problems like imnplementing cross-context links, searching, etc. If it's possible to do what you want with resource groups, it's usually a better choice, IMO.

      I would only use contexts for multi-language sites or multiple sub-sites coexisting under one MODX install.

      YMMV
        Did I help you? Buy me a beer
        Get my Book: MODX:The Official Guide
        MODX info for everyone: http://bobsguides.com/modx.html
        My MODX Extras
        Bob's Guides is now hosted at A2 MODX Hosting
        • 9207 ☆ A M B ☆
        • 2,475 Posts
        +1 to Bob's answer. Contexts are not good for that kind of organizations because they hit a bit harder.

        I usually only use contexts when I have conceptually different sites, but I want those sites to share resources (like templates, snippets, assets).