New Pecha.org's UI need to be changed from Sefaria's way of UI.
Key Concepts
UI :
Pecha.org :
Sefaria :
Context
We have just deployed a latest instance of sefaria with url named pecha.org. The pecha.org is used for displaying Buddhist text. Current sefaria UI (deployed as pecha.org) need lots of change to fit pecha.org user's preference. So we need series of UI modification such as disable some of sefaria's feature, change text direction from rtl to ltr, replace sefaria logo with pecha.org logo etc.
Outputs
The first phase of output should look like the old pecha.org's UI (with each classified feature committed on separate feature branch)
Inputs
First we need to test on locally run pecha.org. Then test on staging.pecha.org for deployment test. Finally push on production-master branch for final production.
Timeline
Specify the expected delivery date for the project.
References
Include any relevant links or resources for additional context or information.
RFW00146: Modify New Pecha.org's UI
Summary
New Pecha.org's UI need to be changed from Sefaria's way of UI.
Key Concepts
UI : Pecha.org : Sefaria :
Context
We have just deployed a latest instance of sefaria with url named pecha.org. The pecha.org is used for displaying Buddhist text. Current sefaria UI (deployed as pecha.org) need lots of change to fit pecha.org user's preference. So we need series of UI modification such as disable some of sefaria's feature, change text direction from rtl to ltr, replace sefaria logo with pecha.org logo etc.
Outputs
The first phase of output should look like the old pecha.org's UI (with each classified feature committed on separate feature branch)
Inputs
First we need to test on locally run pecha.org. Then test on staging.pecha.org for deployment test. Finally push on production-master branch for final production.
Timeline
Specify the expected delivery date for the project.
References
Include any relevant links or resources for additional context or information.