We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 34000
    • 77 Posts
    Hi All, and welcome back [ ...to me smiley ]

    Looking into the possibilites of converting a Newspaper website to a MODX site.
    Just as a point of reference, there is this old article explaining how someone used Google Docs in their workflow, granted they pushed it to Wordpress in this article.

    Anyone know if anything similar was ever discussed using MODX, this article is a little over a year old.

    I think the articles now are being aggregated with something called JazBox, would maybe need to actually interface with that rather than Google Docs.
    Just seeing who's out there that may have any useful tips, at this early stage.
    My boss retired who was pretty much solely responsible for the current version of our online news, which will need updating someday. That code is all .asp [ugh ...tears]...
    A new day is being ushered in that's the good news.
    Thanks for any tips. [ed. note: tzmedia last edited this post 14 years, 2 months ago.]
      MODx Revo 2.1 and done!
      • 39932
      • 483 Posts
      I think a newspaper site is very feasible utilizing ModX. Of course, it would depend on the article load for your media. You should check out the Articles addon. It allows you to create Articles pages that are categorized in Containers. I would also check out FormIt (for front-end editing, if you need it) and MigX (depending on your needs). You can see what is available for Add-Ons at http://rtfm.modx.com/display/ADDON/Home.

      Aside from that, if you haven't used ModX before, get used to the idea of Chunks and Template Variables (TVs). The power of ModX vs other platforms is that ModX doesn't input its own code for you and therefore is completely customizable without having to do anything to the back-end.
        Website: Extended Dialog Development Blog: on Extended Dialog
        Add-ons: AJAX Revolution, RO.IDEs Editor & Framework (in works) Utilities: Plugin Compatibility List
        Tutorials: Create Cross-Context Resources, Cross-Context AJAX Login, Template-Based Actions, Remove Extensions from URLs

        Failure is just another word for saying you didn't want to try. "It can't be done" means "I don't know how".
        • 34000
        • 77 Posts
        Thanks for your reply fuzziL.
        I hadn't realized there was a reply, and was about to simplify the question to...

        Does anybody know of any daily publication website, or other periodical issues-based publication monthly even... using MODX?

        I must admit I hadn't thought about the newer Articles publisher being of any use here.
        Awesome tip.

        It would be great to get in touch with any of the pros, who may of done something similar to a 'Daily' and especially, any recent solutions using articles and/or 'vive la Revolution'!
        Thanks again Mr. ...Logic (Don) [ed. note: tzmedia last edited this post 14 years, 2 months ago.]
          MODx Revo 2.1 and done!
          • 39932
          • 483 Posts
          I am not aware of any daily publication website, myself.

          I'm not sure what the real concerns are here, since content is aggregated and distributed under so many methods. If you are simply talking about scanning the paper and serving that way, I could see issues with that. You'd have to find the right scanning/OCR software, then determine a format to distribute it with, etc. Since you are talking GoogleDocs here, that doesn't sound like a concern.

          Not accounting for specific styling, a news media site is not any different than a blog, except its frequency and the source of content. All can be accounted for using MODX. By using the tutorial to create a blog, you could easily abstract how to convert it to newspaper media. The primary mitigating factor with MODX would be the number of pages (depending on the number of articles per day you are creating). Even then, the number is large enough to account for years of distribution and can be offset in any number of ways.

          The article you reference says it all
          “A lot of what took us so long to roll this out has been because of the complexity of the site, not the complexity of the setup."
          . This is the absolute truth.

          Before asking questions like this, it is best to have a strategy in mind. Know how you want to do something and we can all throw out some answers for you. Otherwise, we're just simply brainstrorming. Questions you should be able to answer:

          What is your client's production process now?

          What do they want their production flow to be?

          What about their current process is unsatisfactory? (cost? number of steps? knowledge requirement? training time?)

          What are their goals in changing the process?

          Once you have these answers, it will be much easier to assist. Otherwise, all I can do is throw out ideas. That said, MODX is super-fast to develop any-type of site in (in my experience).

            Website: Extended Dialog Development Blog: on Extended Dialog
            Add-ons: AJAX Revolution, RO.IDEs Editor & Framework (in works) Utilities: Plugin Compatibility List
            Tutorials: Create Cross-Context Resources, Cross-Context AJAX Login, Template-Based Actions, Remove Extensions from URLs

            Failure is just another word for saying you didn't want to try. "It can't be done" means "I don't know how".