All Projects → buildkite → Frontend

buildkite / Frontend

Licence: mit
🌏 The front-end application code for https://buildkite.com

Programming Languages

javascript
184084 projects - #8 most used programming language
es6
455 projects

Projects that are alternatives of or similar to Frontend

Vue Relay
🖖 🔛 🗂 A framework for building GraphQL-driven Vue.js applications.
Stars: ✭ 105 (-20.45%)
Mutual labels:  graphql, relay, frontend
Rpg Boilerplate
Relay (React), Postgres, and Graphile (GraphQL): A Modern Frontend and API Boilerplate
Stars: ✭ 62 (-53.03%)
Mutual labels:  graphql, relay
Graphql Query Test Mock
Easily mock GraphQL queries in your Relay Modern / Apollo / any-other-GraphQL-client tests.
Stars: ✭ 49 (-62.88%)
Mutual labels:  graphql, relay
Graphbrainz
A fully-featured GraphQL interface for the MusicBrainz API.
Stars: ✭ 130 (-1.52%)
Mutual labels:  graphql, relay
Learnrelay
Learn Relay - A comprehensive introduction to Relay (created by Graphcool)
Stars: ✭ 887 (+571.97%)
Mutual labels:  graphql, relay
Relay Fullstack
☝️🏃 Modern Relay Starter Kit - Integrated with Relay, GraphQL, Express, ES6/ES7, JSX, Webpack, Babel, Material Design Lite, and PostCSS
Stars: ✭ 986 (+646.97%)
Mutual labels:  graphql, relay
Tkframework
react + relay + redux + saga + graphql + webpack
Stars: ✭ 83 (-37.12%)
Mutual labels:  graphql, relay
Graphene
GraphQL framework for Python
Stars: ✭ 6,964 (+5175.76%)
Mutual labels:  graphql, relay
React Transmit
Relay-inspired library based on Promises instead of GraphQL.
Stars: ✭ 1,335 (+911.36%)
Mutual labels:  graphql, relay
Relay Northwind App
A complex React, Relay, GraphQL demo app. Online demo:
Stars: ✭ 104 (-21.21%)
Mutual labels:  graphql, relay
Graphql Sequelize Crud
Automatically generate queries and mutations from Sequelize models
Stars: ✭ 129 (-2.27%)
Mutual labels:  graphql, relay
Hackatalk
TalkTalk renewal. Open source chat app built-in expo managed work flow
Stars: ✭ 123 (-6.82%)
Mutual labels:  graphql, relay
Graphql Config
One configuration for all your GraphQL tools (supported by most tools, editors & IDEs)
Stars: ✭ 883 (+568.94%)
Mutual labels:  graphql, relay
Magiql
🌐 💫 Simple and powerful GraphQL Client, love child of react-query ❤️ relay
Stars: ✭ 45 (-65.91%)
Mutual labels:  graphql, relay
Lighthouse Utils
An add-on to Lighthouse to auto-generate CRUD actions from types https://github.com/nuwave/lighthouse
Stars: ✭ 26 (-80.3%)
Mutual labels:  graphql, relay
Cynthesize Frontend
Frontend written in Angular 7 and deployed GraphQL for Cynthesize. Development build: https://cynthesize-develop.netlify.com
Stars: ✭ 65 (-50.76%)
Mutual labels:  graphql, frontend
Js Graphql Intellij Plugin
GraphQL language support for WebStorm, IntelliJ IDEA and other IDEs based on the IntelliJ Platform.
Stars: ✭ 686 (+419.7%)
Mutual labels:  graphql, relay
Adrenaline
Simple Relay alternative
Stars: ✭ 720 (+445.45%)
Mutual labels:  graphql, relay
Graphql Relay Js
A library to help construct a graphql-js server supporting react-relay.
Stars: ✭ 1,331 (+908.33%)
Mutual labels:  graphql, relay
Graphql Live Query
Realtime GraphQL Live Queries with JavaScript
Stars: ✭ 112 (-15.15%)
Mutual labels:  graphql, relay

Buildkite Frontend (Archived) 📦

For a few years we experimented with developing the Buildkite frontend in an open source repository. In the beginning when our team was small, maintenance of this codebase was easy and it's integration with our main application was minimal.

Over time our team has grown, and so has the size and importance of this codebase. After many weeks of discussion, we decided to stop development in this repoistory, and move it back into our main application (creating a monolith).

The biggest reasons we moved it back were:

  • Day to day development was complicated between our backend application and the frontend code. It was difficult to document and communicate to new members of the team why this seperation existed and what the benefits were. The idea was eventually the code here become a seperate entity that could run indepently of the backend application - but we never got around to it. So the code here ended up becoming an akward dependency of our main application that we managed with git submodules (which caused great sadness).
  • Maintaining 2 PRs for features was annoying (we had a backend and a frontend PR for the same feature. Keeping them both in sync was mostly busywork for little benefit)
  • Our deployment & testing processes were simplified by unifying the codebases
  • We didn't have to worry about "have you got the latest version of the frontend" type problems in development
  • We don't need to concern ourselves with potentially disclosing any feature experiements we may be shipping to production that'd require frontend changes

We're keeping this code public for historical reasons, but the repo will be achived and no longer be developed in.

It's been a few weeks since we made the move, and we've been way more productive with the unifided codebases, and our day to day development experience is simpler. We're sad to no longer have the code be open source, because it brought us joy to have it out in the open, but we hope the increased rate of feature development in Buildkite makes up for that.

If you'd like to keep in sync with the changes we're making - we're posting more and more to our public changelog here: http://buildkite.com/changelog

License

See LICENSE.txt (MIT)

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].