You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 27, 2023. It is now read-only.
We are working to make the site completely static and delivered from the privly-applications repo. This means we should not need any templating on privly-web.
At this point we have moved enough templating that I am downgrading this to "normal". This issue is higher priority than this one as it will further decrease the importance of removing templating.
To work on this issue, you should select a page from the views directory. If the page does not need to have something like a confirmation token (which must be rendered in a template) and if the content server does not need to change the page (different countries may require different terms of service and privacy pages), then it can be ported to the pages directory of the Privly-Applications repository. I would recommend starting with the registration and confirmation pages of Devise, but others may be easier to start with.
So, you want all static pages to be hosted on privly-applications. privly-web should fetch those pages when necessary. Am I right? BTW, I am not sure about how to run privly-application so that privly-web can fetch necessary pages from it.
We are working to make the site completely static and delivered from the privly-applications repo. This means we should not need any templating on privly-web.
See also: privly/privly-applications#108
The text was updated successfully, but these errors were encountered: