Codebase of the website remotearchitects.club, a platform for architecture professionals to share their experiences working remotely.

Built With

Nuxt.js - Vue.js framework
Tailwind CSS - CSS framework
XState - state management
Apollo GraphQL - pulling from a Hasura GraphQL API
Jest - unit testing
Cypress.io - integration tests
Travis CI - CI/CD

Hosted on

Netlify - front end, static hosting (this repo)
Heroku (with Postgres addon) - Hasura back end

Other integrations

Metabase - database intelligence
Forest Admin - administration dashboard
Mailchimp - mailing list, fed by a Netlify Function

Build Setup

# install dependencies
$ yarn install

# serve with hot reload at localhost:3000
$ yarn dev

# build for production and launch server
$ yarn build
$ yarn start

# generate static project
$ yarn generate

# run unit tests
$ yarn test

# run integration tests
$ yarn cy:run

For detailed explanation on how things work, check out Nuxt.js docs.

Git branching system

I follow the "3-flow" branching system:

There are three branches in origin: master, candidate, release
Normal development happens on master. All new commits are rebased.
Features that are incomplete are put behind feature toggles, ideally dynamic toggles that can be changed without a redeploy
To cut a release, master is merged into candidate with a --no-ff merge commit
Any bugs found during a candidate’s QA phase are fixed in candidate and then merged into master with a --no-ff merge commit
When a candidate is released to production, it’s push --forced to the tip of release
Any production hotfixes happen in release and are then merged into candidate which is then merged into master.

<<<<<<< HEAD

Versioning

I use SemVer for versioning. For the versions available, see the tags on this repository.

200b49edbc496838a52f7e2d0d59290f2ca5eb3c

Author

Daniel da Rocha - Creator and Full-stack Developer - danrocha

License

This project is licensed under the MIT License.

gtalarico / frontend-nuxt