af Hans Doenitz 12 måneder siden
46
Mere som dette
could be realized through automation workflows
need a running odoo-database
testing on odoo-test-db should be available
customization of existing odoo-models
custom odoo-models
general paradigm/strategy/style of odoo-implementation, either of (choose main-strategy)
service-provider
political orgs (> Mozaik)
educational ERP (openeducat or cybrosis)
will provide several proposals for new/extended functionality
editors
later maybe: own solution integrated into theaterpedia / crearis
github-codespaces
stackblitz or alike
nuxt.studio
requires github-login
invalidation-types
aggregation-logic
?nitro?
redis-cache
build and serve up to 100 websites
express-server (vuestorefront-code)
on the server automatic deployment of individual folders per repo
config-files
possibility to extend certain fragments of nuxt-/app-config
folders
assets
layout
my-components
content
pages
[.nuxt-logic > through nuxt-build-process]
server-setup standardized with symlink-logic or something similar
2-3 different update-channels (centralized package-solution for automated updating)
[freezed / manual channel]
standard-channel
beta-channel
up to 100 websites administrated on one server
typically 10-20 nginx server blocks (one for every database)
login for editors, admins, executives typically via single-sign-on through github
auth for customers managed through odoo-databases
every database
or regio
working together through
...
or public agenda
or quarterly gathering
a central board
several small-to-medium actors all from the same region
supporter
freelancer
organisation
either: bigger organisation or connected organisations (aka: dasei + theaterpedia) > running several websites
running multiple databases on the same server
[yet to be implemented: event + blogging]
multilanguage + multicompany-functionality
fully abstracts postgresql
beta-features
*blogging
post
forms-based interactions
exposed via odoo-webcontrollers
or iframe / client-side-rendering
either api-style
login & checkout
limited
auth-model
order
cart
company + organisation
user + customer
category
product
*event
maybe: customer-login/auth
views/reports
forms
themes are based on a theme-family and can be switched with live-preview
switched through config > theme-family needs rebuild on the server to render
we extend the theming-capabilities of existing storefront-ui-components
example 2: overline-headline
example 1: post-it
specific for the needs of cultural networking
theming/tailwind-config
typography (prose-components through tailwind-typography)
base-components
images supported through assets + cloudinary
videos through vimeo (preferred) + youtube
standardized implementation inspired by "composable commerce"
based on nuxt-content
based on vuestorefront-sdk
4 ready-made templates with own documentation + public accessible reference-implementation
project
blog
hubsite (with shop)
course
4 different themes
logged-in users and customers can access deeper information-context of one or several domains
accesses content from within the whole theaterpedia-server (across multiple odoo-databases)
can be rendered as project-site, courses, blog or hubsite/shop-portal for mixed purposes
less "commercial" than common-sense-web2-social-media-style
no third actor/mediator controlling
unbound from hidden marketing, tracking, monetization
direct checkout
distinct workflows for organisation and information
payment
taking away the strict boundaries between actors and companies
creative commons as foundation for cooperation in regions and topics
based on open knowledge and open source
together-mode as standard-mode of cultural creation
