You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/blog/entries/ssr-ccsearch/contents.lr
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ While easier to implement initially, when we needed to ship the initial versions
20
20
21
21
2. Empty HTML page: When the initial HTML sent by the server is empty, meaning no visual elements, any internet bots that parse a page HTML wouldn't work properly, that is: SEO, social media websites (when users share a link to CC Search on Twitter or Facebook, those nice previews wouldn't work), the Web Archive, etc..
22
22
23
-
So on -date- we deployed our first release of CC Search with Server Side Rendering. You can see the work that went into it on this [Pull Request on Github](https://github.com/creativecommons/cccatalog-frontend/pull/411).
23
+
So on July 26th we deployed our first release of CC Search with Server Side Rendering. You can see the work that went into it on this [Pull Request on Github](https://github.com/creativecommons/cccatalog-frontend/pull/411).
24
24
25
25
My goal with this blog post will be to explain some of the challenges that we faced while both coding the SSR support on the VueJS codebase and also the operations side with deployment and maintenance.
0 commit comments