Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Front-end portability #92

Closed
pbuttigieg opened this issue Oct 5, 2023 · 2 comments
Closed

Front-end portability #92

pbuttigieg opened this issue Oct 5, 2023 · 2 comments

Comments

@pbuttigieg
Copy link
Collaborator

The site should be portable - a partner should be able to clone the code and spin up their own front end, just changing some config files for colour themes, links to logos / images / branding, etc.

New instantiations of the site will have to point (via (a) config file(s)) to their input sources for records and other data.

Front-end devs should sync carefully with back-end devs to make sure that new instances are stable and can stably connect to their sources within the ODIS Architecture. This issue will be cross-linked to a demonstration case with IOC Africa.

@pbuttigieg pbuttigieg changed the title Portability of the front end Front-end portability Oct 5, 2023
@pbuttigieg
Copy link
Collaborator Author

@jmckenna @fils - The input files would be SOLR indices? Or would they be KG/RDF? I'm assuming the former

dev-marcoC added a commit that referenced this issue Feb 1, 2024
dev-marcoC added a commit that referenced this issue Mar 4, 2024
…ed Carousel, page with JSON-LD for empty URL, refinements, and general bug fixes
@it-iode it-iode closed this as completed Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants