Uploaded image for project: 'Magnolia pages module'
  1. Magnolia pages module
  2. PAGES-187

Present an SPA running on an external server

    XMLWordPrintable

Details

    • Story
    • Resolution: Obsolete
    • Major
    • None
    • None
    • None
    • None
    • SPA Editor 2, SPA Editor 3, SPA Editor 4, SPA Editor 5, SPA Editor 6, SPA Editor 7
    • 8

    Description

      Usually, when developing frontend projects, developers may run a local Node server with live reload. Magnolia does not necessarily need to serve the page. Also for production projects, it's not uncommon for SPAs to be compiled/deployed as static resources on CDNs.

      Start with the assumption that an SPA page is presented/served externally, on a different server. Could be Node for (local) development, nginx for production, etc.

      Log potential limitations or benefits vs. rendering by Magnolia.

      ideas:

      • first denominator: mgnl:template property
      • action in page-editor? maybe too complex with availability
      • url config in template definition?
      • open up support in pages app

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                sang.ngo Sang Ngo Huu
                mgeljic Mikaël Geljić
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoD

                    Time Tracking

                      Estimated:
                      Original Estimate - Not Specified
                      Not Specified
                      Remaining:
                      Time Spent - 11.5d Remaining Estimate - 0.25d
                      0.25d
                      Logged:
                      Time Spent - 11.5d Remaining Estimate - 0.25d
                      11.5d