/scribe-scripture-editor

A Bible translation editor for everyone.

Primary LanguageJavaScriptMIT LicenseMIT

Contributors Issues MIT License


Logo

Scribe Scripture Editor (Scribe SE)

A Bible translation editor for everyone.
Report Issue · Feature Request

Table of Contents

About The Project

Scribe Scripture Editor is a free and open-licensed desktop application that is designed to support the Bible translator with drafting and checking scripture in both text and audio formats as well as provides support for translating Open Bible Stories in different modes. The features include multi-project support, revision control (cloud sync), audio recording and seamless basic USFM editing. It has a modular architecture and is poised to grow and support the evolving needs on the ground.

Built With

Getting Started

It is relatively easy to setup the application locally for development.

Prerequisites

This is an example of how to list things you need to use the software and how to install them.

Installation

  1. Fork and clone this repository
  2. Install dependencies with yarn install
  3. Start the application with yarn start
  4. Checkout the web version with yarn dev Runs the app in the development mode.
    Open http://localhost:3000 to view it in the browser.

Roadmap

See the projects page for a list of proposed features and known issues we are working on.

Contributing

If you'd like to contribute, please fork the repository and commit changes in your fork. Pull requests are warmly welcome.

We really value our contributors whether they helped fix a bug, built a feature, tested out the app or contributed in some other way.

The process for submitting pull requests.

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/NewFeature)
  3. Create logs as you start making changes
Logger level:
Production => warn
Development => debug

Usage: logger.[level]("<filename>, <message>")
  1. Add nessesary propTypes for all the properties passed to react component (https://github.com/facebook/prop-types)
  2. After adding features make sure you write test for that using:
  1. Run yarn lint:fix for code to adapt our linting rules
  2. Run yarn build for build checks
  3. Commit your Changes (git commit -m 'Add some NewFeatures')
  4. Push to the Branch (git push origin feature/NewFeature)
  5. Open a Pull Request and make sure all checks have passed

License

This project is licensed under the MIT License. See LICENSE for more details.

Contact

Let us know if you face any bugs/problems by opening an issue on GitHub. We'll do our best to be prompt in our response.

Acknowledgements

  • Supported by the Open Components Ecosystem.
  • Developed and maintained by Bridgeconn