ucsdlib / damspas-rd

A Digital Collections application based on Hyrax
MIT License
3 stars 2 forks source link

Remove local pages implementation, replace with Hyrax default #89

Closed mcritchlow closed 7 years ago

mcritchlow commented 7 years ago

Decision

per @gamontoya - We should try it out (Hyrax out of the box) at first and revisit.

Tasks:

Descriptive summary

Currently, out of the box, Hyrax provides a mechanism for defining new pages. This is how the About, Help, Contact, pages are defined. As well as specific sections on the default homepage. We could potentially choose to use this for our local pages needs, in place of the custom implementation we created.

I think we need input from @gamontoya and others on what we really need from these pages. For example, how often are end users going to really create "new" pages? Has that feature actually been helpful? It would seem that hasn't been used in damspas.

Note: Matt can give Gabriela a demo to show the UI/UX of each.

Rationale

Pros for local implementation:

Pros for Hyrax implementation:

Related work

53

gamontoya commented 7 years ago

@mcritchlow Where are we at with this ticket?

mcritchlow commented 7 years ago

@gamontoya we need to discuss still. maybe make part of our 1-1 agenda for next week?

gamontoya commented 7 years ago

Background:

Sufia/Hyrax has its own static page feature that we can use.

Pros and Cons:

We could ditch the pages things entirely and have them built out in the app as HTML pages but updates or changes would require a deploy.

Decision:

We should try it out (Hyrax out of the box) at first and revisit.