Breath your Welsh Project
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

byw - Breathe your Welsh Project


Build Status


The Breathe your Welsh project is a community driven action to help increase the visibility of the Welsh language. The project is based around an original idea by Peter Allen on the Welsh forum.

Project Structure

This repository is destined to hold the source for a client side React / Redux app with the server side implementation being on AWS as a Serverless S3 / Lambda combination. The index.html page is initially rendered during the build phase in development and then rendered client side.

The development source code should be placed into the client folder. NPM scripts should be used to package everything up ready for upload to S3. This automates the build process and ensures all the dependencies are present. These scripts can be run from the project root folder, with the scripts themselves being in the build-settings folder.

The s3-build folder should not be manually altered as it is cleared for every build and therefore any changes will not be persisted. This is an intentional design decision to enforce and check that the S3 upload has no missing dependencies.

+---- client // Client source files that are built into the s3-build folder
|    |
|    +---- app // Client code that is browserified
|    |    |
|    |    + core // Project wide components and utils
|    |    |    |
|    |    |    +---- model // Model methods
|    |    |    |   
|    |    |    |
|    |    |    +---- redux // Redux specific code
|    |    |         |
|    |    |         +---- actions
|    |    |         +---- middleware
|    |    |         +---- reducers
|    |    |
|    |    +---- pages // Page components
|    |
|    +---- assets // Static assets that are to be copied to S3
|    |
|    +---- css // Individual css files that are concatenated and striped of unused classes
|              // then inlined
+---- s3-build // Files for sync to static S3 hosting. Do not update this folder manually
+---- static-api // dev static file to mock api
|     |
|     +---- public
|           |
|           +---- data // mock data source of original website data
+---- build-settings // Build scripts
+---- existing-data // dev means to use data from existing website datasource


Community contributions are welcome. In order to contribute check out the project structure above.

Contributing most appreciated on:

Currently we are actively seeking contributions from the community for the following areas:

  • SVG Graphics for things such as icons and some page elements
  • Informational content

Contributing workflow

A suggestion on how to go about proposing a change to this project:

  1. Fork this project to your account.
  2. [Create a branch][branch] for the change you intend to make.
  3. Make your changes to your fork.
  4. Send a pull request from your fork’s branch to the master branch.


A familiarity with following concepts would be useful:

  • Javascript
  • Git
  • Nodejs
  • npm
  • React / Redux

Clone the project to your local file system and run:

npm install

To get a build folder run. Once this has been created it can be served up during development:

npm run build

The package has the http-serve as a dependency to allow for local development. This will serve the files out of the s3-build folder. To use run:

npm run serve-build

Build Process

The build script first of all runs browserify over the client app so that it can be rendered by a local node instance. This is to enable a rendered html page to be uploaded to S3.

The build script also browserifies the client app and bundles it as well as copying over all the static assets.

There is an eslintrc file included to enforce style guidlines.


External services that the app fetches out to

Map tiling: