17e7eb2d7f
1. app.component.ts: <subscribe> and <invite> components added (floating buttons on the right side of each page for communities). 2. community.component.html: 3. community.component.ts: a. 'projectsCalculated' and 'contentProvidersCalculated' fields added, to calculate tootlip after both requests complete b. added methods for building tootips c. 'activeTab' set to 'summary'. 4. affiliations.component.html: minor phrasing changes (e.g. title). 5. curators.component.html: shortview changed. 6. results.component.ts: Title changed | 'View all' moved to the bottom. 7. customization.component.ts: Changed '--portal-main-color' from '#4C9CD5' to '#4687E6' | Changed '--portal-dark-color' from '#24857F' to '#2D72D6'. 8. invite.component.html: shortview changed. 9. invite.component.ts: 'properties' field as input (get it is called from app.component). 10. invite.module.ts & inviteBasic.module.ts: InviteBasicModule created to declare InviteComponent without routing and login guard | InviteModule imports InviteBasicModule and adds routing and login guar$ 11. subscribe.component.ts: Changes for subscribe button and members | 'properties' field as input (get it is called from app.component). 12. connect-custom.css: css for subscribe and invite buttons and for tooltip with 'community-page-tooltip' class. 13. customization.css: class 'communityBackground' added and css for 'subtitle' class inside 'communityBackground'. git-svn-id: https://svn.driver.research-infrastructures.eu/driver/dnet40/modules/uoa-connect-portal/trunk@58549 d315682c-612b-4755-9ff5-7f18f6832af3 |
||
---|---|---|
deploy | ||
src | ||
README.md | ||
angular.json | ||
package.json | ||
prerender.ts | ||
server.ts | ||
static.paths.ts | ||
tsconfig.json | ||
webpack.server.config.js |
README.md
Angular Universal & Anguar-CLI minimal starter
This demo is built following the Angular-CLI Wiki guide
We're utilizing packages from the Angular Universal @nguniversal repo, such as ng-module-map-ngfactory-loader to enable Lazy Loading.
Static or Dynamic
This repo demonstrates the use of 2 different forms of Server Side Rendering.
Static Also known as "prerendering"
- Happens at build time
- Renders your application and replaces the dist index.html with a version rendered at the route
/
.
Dynamic
- Happens at runtime
- Uses
ngExpressEngine
to render you application on the fly at the requested url.
Installation
npm install
oryarn
Development (Client-side only rendering)
- run
npm run start
which will startng serve
(project served at the standard: localhost:4200)
Production
Depending on whether you're publishing dynamic or static prerendering, run the build command, and then serve up your dist folder assets.
NOTE: To deploy your Static site to a static hosting platform you will have to deploy the
dist/browser
folder, rather than the usualdist
ie: npm run build:dynamic
or npm run build:static
. All of the files that need to be served will be found within the /dist
folder.
Testing Universal (dynamic or static) builds -Locally-
Dynamic : npm run start:dynamic
Compiles your application and spins up a Node Express to dynamically serve your Universal application on http://localhost:4000
.
Static : npm run start:static
- Compiles your application and prerenders your applications files, spinning up a demo http-server so you can view it on
http://127.0.0.1:8080