Skip to content
This repository has been archived by the owner on May 28, 2024. It is now read-only.

Load library details from API #36

Open
dillonfagan opened this issue Aug 7, 2023 · 1 comment
Open

Load library details from API #36

dillonfagan opened this issue Aug 7, 2023 · 1 comment
Assignees
Labels
📡 API Requires changes to the API refactor Cleaning up code
Milestone

Comments

@dillonfagan
Copy link
Member

dillonfagan commented Aug 7, 2023

In order to support custom branding for other tool libraries, the frontend needs to load most of its details from the API.

Required Data

  • Name
  • Website Link (Home)
  • Donate Link (Wish List)
  • "How to Borrow" Link
  • Social Links (Footer)
  • Open Hours (How to Borrow)
  • Color Scheme**
  • Logo
  • SEO information

**While planned, Color Scheme's higher complexity means it will be pushed to the second iteration of this feature.

@dillonfagan dillonfagan added the refactor Cleaning up code label Aug 7, 2023
@dillonfagan dillonfagan self-assigned this Aug 13, 2023
@dillonfagan dillonfagan changed the title Pull open hours into a config file Load open hours from API Aug 13, 2023
@dillonfagan dillonfagan added the 📡 API Requires changes to the API label Aug 13, 2023
@dillonfagan dillonfagan changed the title Load open hours from API Load library details from API Aug 15, 2023
@dillonfagan dillonfagan added this to the v0.13 milestone Aug 15, 2023
@dillonfagan dillonfagan modified the milestones: v0.13, v0.14 Sep 13, 2023
@dillonfagan
Copy link
Member Author

As a make-it-work, we should begin by simply moving the PVD Things branding info to the API, even it's hard-coded or static. Then, we can follow that up with configurability from the Librarian app.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
📡 API Requires changes to the API refactor Cleaning up code
Projects
None yet
Development

No branches or pull requests

2 participants