Git Wired is a tool for Developers and Managers to visualize the current state of completeness of a project by individually recognizing the state of each wireframe element. It serves as a simple wireframe visualization of GitHub Project Issues for features in relation to one another. It also provides visuals for quickly conveying the completeness of a project, as well as other custom states of features based on the card column (note: see Known Issues about Card Columns).
The intention is merely a tool for organization, especially on smaller and simpler projects where communication is less formal and features may be forgotten or overlooked. This app will not allow you to add special and specific characteristics to the elements, such as sizes, fonts, or colors, but expects that this type of information is stored in a project card. This is not intended to be a comprehensive wireframe, but rather a quick visual of the basic structure and the state of completeness.
- Git Wired
- Git Wired API (and Repo)
- Fork or clone this repo:
git clone git@github.com:JoelSmith123/git_wired_fe.git <name of your choice>
Note: This app was created with Create React App. - Install Dependencies:
npm install
- Build Application:
npm run build
- To see the app in action locally:
npm start
then go to:http://localhost:8080/
This app obtains data through:
- Sign in with Github via
Login
. Note: There is no register button. - Upon signing in, you will be redirected to your profile page.
- On Profile Page, you can start a new wireframe by selecting repo/project/template type information from dropdown menus from left to right.
- Due to constraints of a 10-day MVP, several preconceived page types are built. These templates sometimes allow you to add nested elements, but the overall structure of a template cannot be changed. Templates also allow you to pair Github Issue/Card Numbers with each element, as well as other helpful information such as a display label and a custom description.
- Due to inconsistencies in quality of data in Github Cards & Issues APIs, we were unable to implement card column data (via /Cards) with card content data (ie Title, Body, State) (via /Issues). Unfortunately, none of the various IDs on cards and issues were the same, so data could not be linked. We valued card content data more, especially considering open/closed/pending state is available there. Our MVP can filter by these states, and display information about the issue, but cannot filter by card column.
npm test
- Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
- Implement Fabric.js for creating/editing wireframe.
This is envisioned to allow for:
- a drag & drop UX,
- independence of feature elements that appear nested (they would not be nested, but rather positioned in overlap),
- production of a stringified object with attributes that can be passed to and from Fabric allowing re-render and could be stored in database as is,
- complete wireframe flexibility --> no more page templates!
To contribute, see the setup instructions.
- Open Issues
- Create a new branch describing the feature. If you close an issue, include it's number in the branch name.
- Please describe all changes in the Pull Request (to
Master
), and all relative issue cards/actions. - Please use the Pull Request Template as the baseline for communication - feel free to add more!
- Please update the
README
if anything is affected.
- FE Project Board
- BE Project Board
- FE Core Features:
- [ ]
Git Wired FrontEnd:
Git Wired BackEnd:
- Facebook's Create React App
- JavaScript
- Mocha
- Chai
- Fabric.js
- Fabric is dependent on Cairo installed to your local system.