Skip to content
This repository has been archived by the owner on Dec 1, 2021. It is now read-only.

Pre rendering of vue-templates #7

Open
Borange opened this issue Apr 15, 2019 · 4 comments
Open

Pre rendering of vue-templates #7

Borange opened this issue Apr 15, 2019 · 4 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@Borange
Copy link

Borange commented Apr 15, 2019

Hi,

Great example of working with Content Delivery API and a frontend framework. Played around with it a little bit. I was thinking are there any plans of making the vue files prerendered or adding SSR (server side rendering, for instance NUXT.js) for the frontend part? Or is the Razor-views still to go. I was thinking of when I curl the adress there are not so much content, you need javascript enabled to view the output.

Very best,
Per

@seriema
Copy link
Contributor

seriema commented Apr 17, 2019

Hi,

That would be a good idea. There are so many ways to do that, and as long it's something a controller can return then it should be fine with the current setup. I'm not sure how to pick the "right" SSR approach as a sample "for everyone using Episerver". Perhaps you can help? We do allow contributions to our repository (by signing a CLA, handled by a Github bot when creating a PR), so we'd love some contribution from our partner developers.

Best regards,
JP
Team Lead, CMS UI, Episerver

@seriema seriema added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed labels Apr 17, 2019
@jtonvang
Copy link

We have two SPA-implementations based on Music Festival up and running (one using Vue and one ported to ReactJS) and SSR is one of the things we haven't found a good approach for - the reason being that the Episerver DXC SLA does not cover Node.js, which most frameworks and plugins for SSR depend on (including NUXT.js).

@seriema
Copy link
Contributor

seriema commented May 14, 2019

@jtonvang We will have to look into the SLA. I'll bring it up internally.

About the react port you did, would you mind contributing it back? I created an issue for it: #9 .

@jtonvang
Copy link

@seriema Great, I think support for NodeJS will probably be expected by many going forward. If you need reference, our support ticket where we were told it's not supported is: #301149

As for contributing our ReactJS port, this is something we would love to do. I'm going on paternity leave after this week, and this will obviously take a bit of time, but I'll see if I can spare a few evenings in between for this :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants