Theaterpedia
technical description (public draft)

summary / short-facts

aim of the project

why not everything on odoo?

why not fullstack javascript?

what makes theaterpedia different?

website-template

top-features

can be rendered as project-site, courses, blog or hubsite/shop-portal for mixed purposes

accesses content from within the whole theaterpedia-server (across multiple odoo-databases)

logged-in users and customers can access deeper information-context of one or several domains

4 ready-made templates with own documentation + public accessible reference-implementation

4 different themes

course

hubsite (with shop)

blog

project

implementation

based on vuestorefront-sdk

based on nuxt-content

standardized implementation inspired by "composable commerce"

multimedia

videos through vimeo (preferred) + youtube

images supported through assets + cloudinary

ux: creais-ui

always acts as frontend on odoo

merges code from