Page History
...
Q: Theme per collection/community/site – we should support out of the box. (Ivan)
Q: Angular components (?)
A: Can be moved around, HTML-like snippets. (Tim) Creating new components is simple (Art)
Q: Architecture diagram? What components are being used? (Pascal)
A: Tomcat, Node.js, don’t need to be on the same server
Q: What other components are there in the UI? E.g. SASS compiler?
A: SASS->CSS, TypeScript->JS, NPM does that. Node implementation of SASS compiler.
Q: Next directions for JS? (Terry)
A: E.g. React. (Tim) First page rendering on the server really speeds up the user experience. (Art)
Q: Browser compatibility? In relation to server-side rendering. (Kim)
A: HTML and CSS
Q: Backward compatibility (e.g. input form declaration file) (Terry)
A: Migration or backward compatibility will be considered. To be decided, still just a POC. (Tim) New formats are an opportunity to solve some current issues. Important that we tested that we can use JSON to dynamically adapt submission form. Opens customizability options. (Andrea)