Hello Team,

I had build your own radar with local csv file attached it and it displays data from csv file.
Now i dont see the option.
Attached is the screenshot having this feature. Kindly let me know how do i enable this feature?

Reason having this feature is we dont have to upload our data in google sheets and expose it. We would like to have the data in the csv format.

Thanks and Regards,
Arjun.M

getting the below error when running npm run dev:

ERROR in ./~/xmlhttprequest/lib/XMLHttpRequest.js
Module not found: Error: Cannot resolve module 'child_process' in C:\Users\TheLetter3\Documents\GitHub\thoughtworks\build-your-own-radar\node_modules\xmlhttprequest\lib
 @ ./~/xmlhttprequest/lib/XMLHttpRequest.js 15:12-36 

I've noticed issues are not being responded to in a timely manner for this project. Is it still actively supported? I have several pull requests I would like to discuss if you are available. thanks

Hi
Tried to run 'docker run -p 8080:8080 -v $PWD:/app -w /app -it node:7.3.0 /bin/sh -c 'npm install && npm run dev'' on fedora 27 without any previous installation of npm. Clean installation of fedora 27.
Got an errors.

npm ERR! Linux 4.13.9-200.fc26.x86_64
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "dev"
npm ERR! node v7.3.0
npm ERR! npm v3.10.10
npm ERR! path /app/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open

npm ERR! enoent ENOENT: no such file or directory, open '/app/package.json'
npm ERR! enoent ENOENT: no such file or directory, open '/app/package.json'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR! /app/npm-debug.log

Dor

Are there environment settings that need to be changed in webpack.config.js?

In the README.md, under "More complex usage", there is mention of skipping the Google Sheet:

or you can also insert all your data straight into the code.

Please provide an example of how to bypass the GoogleSheetInput and populate the data in code.

It seems that the order of the rings in the produced radar depends on the data in the sheet. If the first row is hold then the innermost ring will be hold, the second row is adopt the second innermost ring will that etc.

As the order of the ThoughtWorks radar is, from centre outwards: adopt, trial, assess, hold I think it would make sense for this tool to enforce that order as well.

If a quadrant doesn't have element in one ring (like assess), the print option will generate an empty page.

Locally Running

npm install
npm run dev

and visiting

http://localhost:8080/

and pasting in any google sheet that works with the default thoughtworks BYOR site,
it hangs forever with the screen saying:

Building your radar...

Your Technology Radar will be available in just a few seconds

Note: this happens on the master branch without any changes

Hello,

I was trying create my own radar by using an endpoint which spits out a csv content . The Radar is rendering well but the header of the Radar is always showing as CSV . How will I customize it to display my own radar name?

Kindly help...thank you.

Regards
Arun

The radar does not fit within the browser window at many aspect ratios.
Environment: Google Chrome 63 on Windows 10.
Data set: the sample data set provided at https://docs.google.com/spreadsheets/d/1waDG0_W3-yNiAaUfxcZhTKvl7AUCgXwQw8mdPjCz86U/edit#gid=0

Expected: the radar sizes itself so that content fits within the browser window.
Actual:

1. On the overview page, the bottom of the radar is cut off (see attachment).
2. On the quadrant page, the list of technologies underlaps the radar, and the radar is cut off at the bottom (see attachment).

It would be nice to have a search option in the radar.

Hello Team,

When we try to run "npm run dev" We get the following error both running from npm install and as well running as a docker container.

Error as follows
ERROR in .//xmlhttprequest/lib/XMLHttpRequest.js
Module not found: Error: Cannot resolve module 'child_process' in /root/aim_radar/build-your-own-radar/node_modules/xmlhttprequest/lib
@ .//xmlhttprequest/lib/XMLHttpRequest.js 15:12-36
Child html-webpack-plugin for "index.html":
chunk {0} index.html 541 kB [rendered]
[0] .//html-webpack-plugin/lib/loader.js!./src/index.html 1.03 kB {0} [built]
[1] .//lodash/lodash.js 540 kB {0} [built]
[2] (webpack)/buildin/module.js 251 bytes {0} [built]
Child extract-text-webpack-plugin:
chunk {0} extract-text-webpack-plugin-output-filename 30.4 kB [rendered]
[0] .//css-loader?sourceMap!.//sass-loader!./src/stylesheets/base.scss 28.9 kB {0} [built]
[1] ./~/css-loader/lib/css-base.js 1.51 kB {0} [built]
webpack: Failed to compile.

Can someone help in fixing this issue for me.

Nodejs version v7.3.0

Thanks and REgards,
ARjun.M

Apologies for my idiocy - How do I get this to run? I can't get the index page to show me anything (just a blank page every time).

Hi ,

Could you please let me if I can use S3 storage of a CSV file and use it in BYOR ?

Regards
Arun

About 40-60% of the time when hitting the radar URL, even with no recent changes to the underlying Google sheet, we will receive the standard "Oops page" (see below). If you review your logs for yesterday, you will likely see the errors. This can be reproduced by creating a sheet (seems to happen more often on larger documents - over 100 entries) and then pressing F5. The radar page will alternate between showing the radar and sending the error. During that time, no changes are being made to the sheet. I though perhaps it was Google's syncing across servers, however, even an hour later with no changes to the sheet, this behavior continues. I would be happy to share my Google sheet ID offline for you to replicate. Note our Google sheet has a second tab, I will remove that tab and see if that resolves the issue.

We are loving this tool, thank you for building it!

Oops! It seems like there are some problems with loading your data. Document is missing one or more required headers or they are misspelled. Check that your document contains headers for "name", "ring", "quadrant", "isNew", "description".
Please check FAQs for possible solutions.

Hello Team,

Are there are any plans to run BYOR in Kubernetes Environment ?

Thanks and Regards,
Arjun.M

Hi,

I am trying to serve a CSV file through Nginx for building a radar in Mozilla Firefox browser.
In #66 @viveksoundrapandi mentioned

@sgarap as firefox supports preflight requests for CORS requests, it initiates a preflight request which gets failed as the server[in this case gist.github.com] does not set the response header Access-Control-Allow-Methods explicitly. It only responds with Access-Control-Allow-Origin: * which is not enough for firefox to allow a preflight request. However, it will work in chrome as pre-flight requests are not released yet .

In short: the server hosting the csv must allow CORS origin and methods in the response headers.

I am now trying to deliver my CSV file through Nginx.
I saw from Browser's network that, for loading a CSV file, an OPTIONS request is sent first and then a GET request.

When CSV file was delievered from Amazon S3, OPTIONS request response has following headers with status code 200.

Access-Control-Allow-Methods: GET
Access-Control-Allow-Origin: *
Content-Length: 0
Date: Fri, 21 Dec 2018 10:39:28 GMT
Server: AmazonS3
Vary: Origin, Access-Control-Request-Headers, Access-Control-Request-Method
access-control-allow-headers: user-agent
x-amz-id-2: 4YSKkFE/SeReYxZlmQjjSw2bUBDlkx22mt+DVmKkyE3dRT2HXw/9NNIaPw8aD8BJnWXDrhiDNVQ=
x-amz-request-id: 6465E930BF1268F6

From Nginx Server, i tried returning a similar response headers for OPTIONS request.

Nginx Server Config:

location /images/ {
		autoindex on;
		
	if ($request_method = OPTIONS ) {
        add_header Content-Length 0;
        add_header Content-Type text/plain;
		add_header Access-Control-Allow-Origin *;
		add_header Access-Control-Request-Method GET;
		add_header Access-Control-Request-Headers *;
		add_header Access-Control-Allow-Methods GET;
		add_header access-control-allow-headers *;
        return 200;
    }

	}

Repose Headers in Browser with status code 200:

Access-Control-Allow-Methods: GET
Access-Control-Allow-Origin: *
Access-Control-Request-Headers: *
Access-Control-Request-Method: GET
Connection: keep-alive
Content-Length: 0
Content-Type: application/octet-stream
Date: Fri, 21 Dec 2018 11:07:01 GMT
Server: nginx/1.10.3 (Ubuntu)
access-control-allow-headers: *

But still, a subsequent GET request is not made to get the CSV data and html page with following message is displayed.

Oops! It seems like there are some problems with loading your data. Document is missing one or more required headers or they are misspelled. Check that your document contains headers for "name", "ring", "quadrant", "isNew", "description".
Please check FAQs for possible solutions.

Can you please let me know what should be done so that i can build a radar from CSV data delivered from Nginx.
Note: Same CSV delivered from S3 is working absolutely fine.

It is possible to see on the upper left side that the Framework list overlays the title of "infrastructure".

We also lost the "moved up and moved down" which in my opinion should be centered at the top of of the circle or at bottom.

I have been playing arround with the code but there are fixed offsets that mess all, not all is calculated. If I have time I will get this working and make a PR.

Hi guys,

I tried to host the radar on my own server by doing the npm install. But it seems like the module node-sass is not compatible with the latest version.

See the error below:

ERROR in ENOENT: no such file or directory, scandir '/var/www/html/apps/build-your-own-radar/node_modules/node-sass/vendor'
 @ ./src/stylesheets/base.scss 4:14-127

ERROR in ./src/stylesheets/base.scss
Module build failed: Error: ENOENT: no such file or directory, scandir '/var/www/html/apps/build-your-own-radar/node_modules/node-sass/vendor'
    at Error (native)
    at Object.fs.readdirSync (fs.js:952:18)
    at Object.getInstalledBinaries (/var/www/html/apps/build-your-own-radar/node_modules/node-sass/lib/extensions.js:121:13)
    at foundBinariesList (/var/www/html/apps/build-your-own-radar/node_modules/node-sass/lib/errors.js:20:15)
    at foundBinaries (/var/www/html/apps/build-your-own-radar/node_modules/node-sass/lib/errors.js:15:5)
    at Object.module.exports.missingBinary (/var/www/html/apps/build-your-own-radar/node_modules/node-sass/lib/errors.js:45:5)
    at module.exports (/var/www/html/apps/build-your-own-radar/node_modules/node-sass/lib/binding.js:15:30)
    at Object.<anonymous> (/var/www/html/apps/build-your-own-radar/node_modules/node-sass/lib/index.js:14:35)

The same error is also given here:

ERROR in ./src/stylesheets/base.scss

Can you please help?

From what I saw, at the moment, the first ring correspond to the first value found. I would like a way to specify the ring order. The quadrant order would be nice too.

Hi, I have massive problems with the instance running at https://radar.thoughtworks.com.
Does anybody have the same problems? No matter if I use a google sheet or provide a CSV file on my own web server, every time this error appears in the java script console:
[Error] Origin https://radar.thoughtworks.com is not allowed by Access-Control-Allow-Origin.
[Error] Failed to load resource: Origin https://radar.thoughtworks.com is not allowed by Access-Control-Allow-Origin. (radar.csv, line 0)
[Error] Fetch API cannot load [...]/radar.csv. Origin https://radar.thoughtworks.com is not allowed by Access-Control-Allow-Origin.

Hi,

This radar tool has been really useful, but I found the behavior when there are too many blips for a certain quadrant/ring very confusing. I was surprised to find that not all my blips were showing up and saw that in radar.js blips that are not successfully placed without a collision after 100 attempts are silently dropped. It might be good to give a warning when a blip is dropped or just set an explicit cap on number of blips for each section.

Hi, this is a question as opposed to an issue.

How are blips positioned within the ring? It isn't immediately obvious to me how you can position a blip to be closer to the Adopt ring as opposed to the Assess ring if the blip is placed in the trial ring?

Looking at this project I see a lot of contributions to the release branch, from thoughtworks it seems, which has diverged significantly from master. I also see several PRs, some recent, which seem ready to be merged to master.

If I'm going to try to deploy this, which branch should I be using?
Can I expect changes on release to be merged with master any time soon? Ever?

Some doc in the README.md or a HOW_TO_CONTRIBUTE.md might go a long way.

Hello,

I would like to add logos to the radar. I have created in sheet with 5 instead of 4 columns. In the fifth column I have inserted the links to my logos. Unfortunately I am very inexperienced. I want to see the small logo above the description.

<p><img src="my-logo-example,.jpg" style="width: 100px;height: 100px;"> <br><br>This is the description. You can use basic html such as the <strong>strong tag to emphasise keywords and phrases</strong> and insert <a href="https://www.thoughtworks.com">anchor links to documentation and referance material</a>.</p>

Something like this - i made this in the browser html. But my dream is that when i add my google sheet the logos will come automated. I think its something in the radar.js but i am not sure.

Hello. This project has no dependency on jQuery however one (or some) of the GTM tags seem to be using jQuery. So gtm.js expects jQuery to be available. Since jQuery is not available an error is being thrown at runtime.

This can be prevented in two ways:

• change the GTM tags to use plain JavaScript
• add jQuery as a dependency in the project (not recommended because this project has no dependency on jQuery so doesn't make much sense)

I am new to web development so maybe this is a fairly easy one:

How do I deploy an own radar modified and built with this framework on a server?
I was thinking about something like Azure, but I am not bound to that.

Thanks in advance!

Quadrant labels on top navigation pane do not follow the order in Google Sheet

System: macOS High Sierra

Installing the package with npm installor sudo npm install fails with following error:

> [email protected] install /Users/USER/dev/build-your-own-radar/node_modules/fsevents
> node install

node-pre-gyp ERR! Completion callback never invoked! 
node-pre-gyp ERR! System Darwin 17.7.0
node-pre-gyp ERR! command "/usr/local/Cellar/node/11.6.0/bin/node" "/Users/USER/dev/build-your-own-radar/node_modules/fsevents/node_modules/node-pre-gyp/bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /Users/USER/dev/build-your-own-radar/node_modules/fsevents
node-pre-gyp ERR! node -v v11.6.0
node-pre-gyp ERR! node-pre-gyp -v v0.10.0
node-pre-gyp ERR! This is a bug in `node-pre-gyp`.
node-pre-gyp ERR! Try to update node-pre-gyp and file an issue if it does not help:
node-pre-gyp ERR!     <https://github.com/mapbox/node-pre-gyp/issues>

> [email protected] postinstall /Users/USER/dev/build-your-own-radar/node_modules/cypress
> node index.js --exec install

Installing Cypress (version: 3.1.3)

internal/streams/legacy.js:57
      throw er; // Unhandled stream error in pipe.
      ^

Error: EACCES: permission denied, open '/Users/USER/dev/build-your-own-radar/node_modules/cypress/cypress.zip'
npm WARN [email protected] requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] install: `node install`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 6

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: `node index.js --exec install`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/USER/.npm/_logs/2019-03-05T09_57_52_217Z-debug.log

The last lines in the log file regarding the warn and the error don't deliver much information either:

3315 warn [email protected] requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.
3316 warn optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
3317 warn optional SKIPPING OPTIONAL DEPENDENCY: [email protected] install: `node install`
3317 warn optional SKIPPING OPTIONAL DEPENDENCY: Exit status 6
3318 verbose optional SKIPPING OPTIONAL DEPENDENCY:
3318 verbose optional Failed at the [email protected] install script.
3318 verbose optional SKIPPING OPTIONAL DEPENDENCY: This is probably not a problem with npm. There is likely additional logging output above.
3319 verbose stack Error: [email protected] postinstall: `node index.js --exec install`
3319 verbose stack Exit status 1
3319 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
3319 verbose stack     at EventEmitter.emit (events.js:188:13)
3319 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
3319 verbose stack     at ChildProcess.emit (events.js:188:13)
3319 verbose stack     at maybeClose (internal/child_process.js:978:16)
3319 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)
3320 verbose pkgid [email protected]
3321 verbose cwd /Users/USER/dev/build-your-own-radar
3322 verbose Darwin 17.7.0
3323 verbose argv "/usr/local/Cellar/node/11.6.0/bin/node" "/usr/local/bin/npm" "install"
3324 verbose node v11.6.0
3325 verbose npm  v6.5.0
3326 error code ELIFECYCLE
3327 error errno 1
3328 error [email protected] postinstall: `node index.js --exec install`
3328 error Exit status 1
3329 error Failed at the [email protected] postinstall script.
3329 error This is probably not a problem with npm. There is likely additional logging output above.
3330 verbose exit [ 1, true ]

Does someone know what causes this error?

Hello Team,

Is it possible to Change the tab Languages in the webpage to someother Name?
If so kindly let me know since we have the data which represents someother field and not Languages.

Thanks and Regards,
Arjun.M

After pulling and running the docker image, when I try to access it from browser as localhost:8080, i am getting 403 forbidden Error.

I would like to have a link for each quadrant.
The reason is that I would like to show a rotating dashboard, which each of the four quadrants. To do that, I would need a deep link to each of them.

Hi,

This isn't actually an issue, I'm just looking for someone to shed some light as to how the selectQuadrant function works in src/graphing/radar.js.

For example, the differences between adjustX, translateX, and moveRight - these variables seem to have identical-sounding names, although obviously they do all represent different things.

And how exactly are these values calculated? Seeing an expression like (-1 * (1 - adjustY) * (size / 2 - 7) * (scale - 1)) - ((1 - adjustY) / 2 * (1 - scale / 2) * size) without any documentation is scary!

Thanks you.

I'am trying to make this radar composed of 6 quadrants, but i cannot make the blimps appear correctly when i divide the circle in 6 slices

This is not an issue. Just a question. What file should be edited to be able to add multiple Google Sheets to the code? The docs say you can add Google Sheets to the code.

I've done some minor changes to the codebase. After running npm test, everything is green, so I wanted to build a new docker image.

I'm trying a fairly simple command:

docker build --no-cache . -t my-own-radar

When I tried this, it failed with some syntax issue with change.js. Looking around, found out that this is a known issue fixed recently. Fair enough, I applied that small code change to my local node_modules and changed the .dockerignore file to take them into account instead of ignoring.

Looked like that fixed it, only to fall into another broken dependency, this time with punycode. The error is a bit generic:

ERROR in main.50f6e5b170f4e0ae33ca.js from UglifyJs
SyntaxError: Unexpected token: name (length) [./~/punycode/punycode.js:55,0]

I'm worried that even if I manage to fix this one, there will be more like this coming.

How are you building the docker image that is uploaded to Docker Hub?

Hi,
Would it be possible to embed a generated radar in a different webpage?
My wish would be to import a certain javascript to a existing site rather than using iframes or web components. For instance, in the same way timeline library works:
https://github.com/NUKnightLab/TimelineJS3

Would that be possible?

In the company I work at, we want use this radar. The problem is, we have a Google Drive, which is managed inside our internal network. So I forked this repository, and extended it with a Google OAuth implementation. Now everyone, which has an internal company-"Google Account" can view the radar, if the "spreadsheet share"-settings are set correctly.
This fork is currently on our internal git repository.

We would like to contribute this back to the community. The question I have; how should we proceed? We could create a pull request, but maybe some users do not want any Google Authentication and prefer the way it is now?

Do you have any suggestions?

Trying to host 'build-your-own-radar' on a server, it keeps failing with below errors:

Commands tried:

1. npm run dev
2. npm rebuild node-sass && npm run dev
3. npm install && npm rebuild node-sass && npm run dev

Let me know what can be done to resolve this error?

Error Log:

[email protected] dev C:\users\dave\development\build-your-own-radar
webpack-dev-server --mode development --inline

i ｢wds｣: Project is running at http://0.0.0.0:8080/
i ｢wds｣: webpack output is served from /
i ｢wds｣: Content not from webpack is served from C:\users\dave\development\build-your-own-radar\dist
× ｢wdm｣: Hash: 714ac5ccf39ffc08cfff
Version: webpack 4.28.1
Time: 5398ms
Built at: 03/21/2019 4:15:43 PM
Asset Size Chunks Chunk Names
common.714ac5ccf39ffc08cfff.js 366 KiB common [emitted] common
error.html 1.07 KiB [emitted]
images/favicon.ico 1.12 KiB [emitted]
images/logo.png 5.52 KiB [emitted]
images/radar_legend.png 5.92 KiB [emitted]
images/search-logo-2x.svg 1.68 KiB [emitted]
images/tech-radar-landing-page-wide.png 16.1 KiB [emitted]
images/tw-logo.png 3.64 KiB [emitted]
index.html 732 bytes [emitted]
main.714ac5ccf39ffc08cfff.js 5.96 MiB main [emitted] main
Entrypoint main = main.714ac5ccf39ffc08cfff.js
Entrypoint common = common.714ac5ccf39ffc08cfff.js
[0] multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/site.js 40 bytes {main} [built]
[13] multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/common.js 40 bytes {common} [built]
[./node_modules/loglevel/lib/loglevel.js] C:/Users/dave/development/build-your-own-radar/node_modules/loglevel/lib/loglevel.js 7.68 KiB {main} {common} [built]
[./node_modules/strip-ansi/index.js] C:/Users/dave/development/build-your-own-radar/node_modules/strip-ansi/index.js 161 bytes {main} {common} [built]
[./node_modules/url/url.js] C:/Users/dave/development/build-your-own-radar/node_modules/url/url.js 22.8 KiB {main} {common} [built]
[./node_modules/webpack-dev-server/client/index.js?http://0.0.0.0:8080] (webpack)-dev-server/client?http://0.0.0.0:8080 7.78 KiB {main} {common} [built]
[./node_modules/webpack-dev-server/client/overlay.js] (webpack)-dev-server/client/overlay.js 3.58 KiB {main} {common} [built]
[./node_modules/webpack-dev-server/client/socket.js] (webpack)-dev-server/client/socket.js 1.05 KiB {main} {common} [built]
[./node_modules/webpack/hot sync ^./log$] (webpack)/hot sync nonrecursive ^./log$ 170 bytes {main} {common} [built]
[./node_modules/webpack/hot/emitter.js] (webpack)/hot/emitter.js 75 bytes {main} {common} [built]
[./src/common.js] 199 bytes {main} {common} [built]
[./src/images/favicon.ico] 64 bytes {main} {common} [built]
[./src/images/logo.png] 61 bytes {main} [built]
[./src/images/radar_legend.png] 69 bytes {main} [built]
[./src/site.js] 172 bytes {main} [built]
+ 1129 hidden modules

WARNING in C:/Users/dave/development/build-your-own-radar/node_modules/base64-js/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\dave\development\build-your-own-radar\node_modules\base64-js\index.js
  Used by 1 module(s), i. e.
  C:\Users\dave\development\build-your-own-radar\node_modules\buffer\index.js
• C:\users\dave\development\build-your-own-radar\node_modules\base64-js\index.js
  Used by 1 module(s), i. e.
  C:\users\dave\development\build-your-own-radar\node_modules\buffer\index.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/base64-js/index.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/buffer/index.js
  @ ./node_modules/htmlparser2/lib/WritableStream.js
  @ ./node_modules/htmlparser2/lib/index.js
  @ ./node_modules/sanitize-html/dist/index.js
  @ ./src/util/inputSanitizer.js
  @ ./src/util/factory.js
  @ ./src/site.js
  @ multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/site.js

WARNING in C:/Users/dave/development/build-your-own-radar/node_modules/buffer/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\dave\development\build-your-own-radar\node_modules\buffer\index.js
  Used by 27 module(s), i. e.
  C:\users\dave\development\build-your-own-radar\node_modules\htmlparser2\lib\WritableStream.js
• C:\users\dave\development\build-your-own-radar\node_modules\buffer\index.js
  Used by 10 module(s), i. e.
  C:\users\dave\development\build-your-own-radar\node_modules\chance\chance.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/buffer/index.js
  @ ./node_modules/htmlparser2/lib/WritableStream.js
  @ ./node_modules/htmlparser2/lib/index.js
  @ ./node_modules/sanitize-html/dist/index.js
  @ ./src/util/inputSanitizer.js
  @ ./src/util/factory.js
  @ ./src/site.js
  @ multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/site.js

WARNING in C:/Users/dave/development/build-your-own-radar/node_modules/buffer/node_modules/isarray/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\dave\development\build-your-own-radar\node_modules\buffer\node_modules\isarray\index.js
  Used by 1 module(s), i. e.
  C:\Users\dave\development\build-your-own-radar\node_modules\buffer\index.js
• C:\users\dave\development\build-your-own-radar\node_modules\buffer\node_modules\isarray\index.js
  Used by 1 module(s), i. e.
  C:\users\dave\development\build-your-own-radar\node_modules\buffer\index.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/buffer/node_modules/isarray/index.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/buffer/index.js
  @ ./node_modules/htmlparser2/lib/WritableStream.js
  @ ./node_modules/htmlparser2/lib/index.js
  @ ./node_modules/sanitize-html/dist/index.js
  @ ./src/util/inputSanitizer.js
  @ ./src/util/factory.js
  @ ./src/site.js
  @ multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/site.js

WARNING in C:/Users/dave/development/build-your-own-radar/node_modules/core-util-is/lib/util.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\dave\development\build-your-own-radar\node_modules\core-util-is\lib\util.js
  Used by 10 module(s), i. e.
  C:\Users\dave\development\build-your-own-radar\node_modules\stream-browserify\node_modules\readable-stream\lib_stream_readable.js
• C:\users\dave\development\build-your-own-radar\node_modules\core-util-is\lib\util.js
  Used by 1 module(s), i. e.
  C:\users\dave\development\build-your-own-radar\node_modules\verror\lib\verror.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/core-util-is/lib/util.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/stream-browserify/node_modules/readable-stream/lib/_stream_readable.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/stream-browserify/node_modules/readable-stream/readable-browser.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/stream-browserify/index.js
  @ ./node_modules/request/request.js
  @ ./node_modules/request/index.js
  @ ./node_modules/tabletop/src/tabletop.js
  @ ./src/util/factory.js
  @ ./src/site.js
  @ multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/site.js

WARNING in C:/Users/dave/development/build-your-own-radar/node_modules/ieee754/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\dave\development\build-your-own-radar\node_modules\ieee754\index.js
  Used by 1 module(s), i. e.
  C:\Users\dave\development\build-your-own-radar\node_modules\buffer\index.js
• C:\users\dave\development\build-your-own-radar\node_modules\ieee754\index.js
  Used by 1 module(s), i. e.
  C:\users\dave\development\build-your-own-radar\node_modules\buffer\index.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/ieee754/index.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/buffer/index.js
  @ ./node_modules/htmlparser2/lib/WritableStream.js
  @ ./node_modules/htmlparser2/lib/index.js
  @ ./node_modules/sanitize-html/dist/index.js
  @ ./src/util/inputSanitizer.js
  @ ./src/util/factory.js
  @ ./src/site.js
  @ multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/site.js

WARNING in C:/Users/dave/development/build-your-own-radar/node_modules/inherits/inherits_browser.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\dave\development\build-your-own-radar\node_modules\inherits\inherits_browser.js
  Used by 47 module(s), i. e.
  C:\Users\dave\development\build-your-own-radar\node_modules\stream-http\lib\response.js
• C:\users\dave\development\build-your-own-radar\node_modules\inherits\inherits_browser.js
  Used by 4 module(s), i. e.
  C:\users\dave\development\build-your-own-radar\node_modules\htmlparser2\lib\WritableStream.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/inherits/inherits_browser.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/stream-http/lib/response.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/stream-http/index.js
  @ ./node_modules/request/request.js
  @ ./node_modules/request/index.js
  @ ./node_modules/tabletop/src/tabletop.js
  @ ./src/util/factory.js
  @ ./src/site.js
  @ multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/site.js

WARNING in C:/Users/dave/development/build-your-own-radar/node_modules/process/browser.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\dave\development\build-your-own-radar\node_modules\process\browser.js
  Used by 16 module(s), i. e.
  C:\Users\dave\development\build-your-own-radar\node_modules\stream-http\lib\response.js
• C:\users\dave\development\build-your-own-radar\node_modules\process\browser.js
  Used by 11 module(s), i. e.
  C:\users\dave\development\build-your-own-radar\node_modules\tabletop\src\tabletop.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/process/browser.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/stream-http/lib/response.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/stream-http/index.js
  @ ./node_modules/request/request.js
  @ ./node_modules/request/index.js
  @ ./node_modules/tabletop/src/tabletop.js
  @ ./src/util/factory.js
  @ ./src/site.js
  @ multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/site.js

WARNING in C:/Users/dave/development/build-your-own-radar/node_modules/safe-buffer/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\dave\development\build-your-own-radar\node_modules\safe-buffer\index.js
  Used by 39 module(s), i. e.
  C:\Users\dave\development\build-your-own-radar\node_modules\string_decoder\lib\string_decoder.js
• C:\users\dave\development\build-your-own-radar\node_modules\safe-buffer\index.js
  Used by 5 module(s), i. e.
  C:\users\dave\development\build-your-own-radar\node_modules\request\lib\helpers.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/safe-buffer/index.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/string_decoder/lib/string_decoder.js
  @ ./node_modules/htmlparser2/lib/WritableStream.js
  @ ./node_modules/htmlparser2/lib/index.js
  @ ./node_modules/sanitize-html/dist/index.js
  @ ./src/util/inputSanitizer.js
  @ ./src/util/factory.js
  @ ./src/site.js
  @ multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/site.js

WARNING in C:/Users/dave/development/build-your-own-radar/node_modules/setimmediate/setImmediate.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\dave\development\build-your-own-radar\node_modules\setimmediate\setImmediate.js
  Used by 1 module(s), i. e.
  C:\Users\dave\development\build-your-own-radar\node_modules\timers-browserify\main.js
• C:\users\dave\development\build-your-own-radar\node_modules\setimmediate\setImmediate.js
  Used by 1 module(s), i. e.
  C:\users\dave\development\build-your-own-radar\node_modules\timers-browserify\main.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/setimmediate/setImmediate.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/timers-browserify/main.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/stream-browserify/node_modules/readable-stream/lib/_stream_writable.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/stream-browserify/node_modules/readable-stream/writable-browser.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/stream-browserify/index.js
  @ ./node_modules/request/request.js
  @ ./node_modules/request/index.js
  @ ./node_modules/tabletop/src/tabletop.js
  @ ./src/util/factory.js
  @ ./src/site.js
  @ multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/site.js

WARNING in C:/Users/dave/development/build-your-own-radar/node_modules/timers-browserify/main.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\dave\development\build-your-own-radar\node_modules\timers-browserify\main.js
  Used by 2 module(s), i. e.
  C:\Users\dave\development\build-your-own-radar\node_modules\stream-browserify\node_modules\readable-stream\lib_stream_writable.js
• C:\users\dave\development\build-your-own-radar\node_modules\timers-browserify\main.js
  Used by 2 module(s), i. e.
  C:\users\dave\development\build-your-own-radar\node_modules\request\lib\helpers.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/timers-browserify/main.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/stream-browserify/node_modules/readable-stream/lib/_stream_writable.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/stream-browserify/node_modules/readable-stream/writable-browser.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/stream-browserify/index.js
  @ ./node_modules/request/request.js
  @ ./node_modules/request/index.js
  @ ./node_modules/tabletop/src/tabletop.js
  @ ./src/util/factory.js
  @ ./src/site.js
  @ multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/site.js

WARNING in (webpack)/buildin/global.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\dave\development\build-your-own-radar\node_modules\webpack\buildin\global.js
  Used by 19 module(s), i. e.
  C:\Users\dave\development\build-your-own-radar\node_modules\node-libs-browser\node_modules\punycode\punycode.js
• C:\users\dave\development\build-your-own-radar\node_modules\webpack\buildin\global.js
  Used by 11 module(s), i. e.
  C:\users\dave\development\build-your-own-radar\node_modules\lodash\core.js
  @ (webpack)/buildin/global.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/node-libs-browser/node_modules/punycode/punycode.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/url/url.js
  @ (webpack)-dev-server/client?http://0.0.0.0:8080
  @ multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/site.js

WARNING in (webpack)/buildin/module.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\dave\development\build-your-own-radar\node_modules\webpack\buildin\module.js
  Used by 2 module(s), i. e.
  C:\Users\dave\development\build-your-own-radar\node_modules\node-libs-browser\node_modules\punycode\punycode.js
• C:\users\dave\development\build-your-own-radar\node_modules\webpack\buildin\module.js
  Used by 5 module(s), i. e.
  C:\users\dave\development\build-your-own-radar\node_modules\lodash\core.js
  @ (webpack)/buildin/module.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/node-libs-browser/node_modules/punycode/punycode.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/url/url.js
  @ (webpack)-dev-server/client?http://0.0.0.0:8080
  @ multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/site.js

WARNING in C:/Users/dave/development/build-your-own-radar/node_modules/xtend/immutable.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

• C:\Users\dave\development\build-your-own-radar\node_modules\xtend\immutable.js
  Used by 1 module(s), i. e.
  C:\Users\dave\development\build-your-own-radar\node_modules\stream-http\index.js
• C:\users\dave\development\build-your-own-radar\node_modules\xtend\immutable.js
  Used by 1 module(s), i. e.
  C:\users\dave\development\build-your-own-radar\node_modules\sanitize-html\dist\index.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/xtend/immutable.js
  @ C:/Users/dave/development/build-your-own-radar/node_modules/stream-http/index.js
  @ ./node_modules/request/request.js
  @ ./node_modules/request/index.js
  @ ./node_modules/tabletop/src/tabletop.js
  @ ./src/util/factory.js
  @ ./src/site.js
  @ multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/site.js

ERROR in ./src/stylesheets/base.scss (./node_modules/mini-css-extract-plugin/dist/loader.js!./node_modules/css-loader/dist/cjs.js??ref--5-2!./node_modules/postcss-loader/src??postcss!./node_modules/sass-loader/lib/loader.js!./src/stylesheets/base.scss)
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/sass-loader/lib/loader.js):
Error: Cannot find module 'node-sass'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
at Function.Module._load (internal/modules/cjs/loader.js:508:25)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
at Object.sassLoader (C:\users\dave\development\build-your-own-radar\node_modules\sass-loader\lib\loader.js:46:72)
at runLoaders (C:\Users\dave\development\build-your-own-radar\node_modules\webpack\lib\NormalModule.js:301:20)
at C:\Users\dave\development\build-your-own-radar\node_modules\loader-runner\lib\LoaderRunner.js:364:11
at C:\Users\dave\development\build-your-own-radar\node_modules\loader-runner\lib\LoaderRunner.js:230:18
at runSyncOrAsync (C:\Users\dave\development\build-your-own-radar\node_modules\loader-runner\lib\LoaderRunner.js:143:3)
at iterateNormalLoaders (C:\Users\dave\development\build-your-own-radar\node_modules\loader-runner\lib\LoaderRunner.js:229:2)
at Array. (C:\Users\dave\development\build-your-own-radar\node_modules\loader-runner\lib\LoaderRunner.js:202:4)
at Storage.finished (C:\Users\dave\development\build-your-own-radar\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:43:16)
at provider (C:\Users\dave\development\build-your-own-radar\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:79:9)
at C:\Users\dave\development\build-your-own-radar\node_modules\graceful-fs\graceful-fs.js:90:16
at FSReqWrap.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:53:3)
@ ./src/stylesheets/base.scss 2:14-249
@ ./src/common.js
@ multi (webpack)-dev-server/client?http://0.0.0.0:8080 ./src/common.js
Child html-webpack-plugin for "error.html":
1 asset
Entrypoint undefined = error.html
[./node_modules/html-webpack-plugin/lib/loader.js!./src/error.html] 1.24 KiB {0} [built]
[./node_modules/lodash/lodash.js] 527 KiB {0} [built]
[./node_modules/webpack/buildin/global.js] 472 bytes {0} [built]
[./node_modules/webpack/buildin/module.js] 497 bytes {0} [built]
Child html-webpack-plugin for "index.html":
1 asset
Entrypoint undefined = index.html
[./node_modules/html-webpack-plugin/lib/loader.js!./src/index.html] 900 bytes {0} [built]
[./node_modules/lodash/lodash.js] 527 KiB {0} [built]
[./node_modules/webpack/buildin/global.js] 472 bytes {0} [built]
[./node_modules/webpack/buildin/module.js] 497 bytes {0} [built]
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js??ref--5-2!node_modules/postcss-loader/src/index.js??postcss!node_modules/sass-loader/lib/loader.js!src/stylesheets/base.scss:
Entrypoint mini-css-extract-plugin = *
[./node_modules/css-loader/dist/cjs.js?!./node_modules/postcss-loader/src/index.js?!./node_modules/sass-loader/lib/loader.js!./src/stylesheets/base.scss] ./node_modules/css-loader/dist/cjs.js??ref--5-2!./node_modules/postcss-loader/src??postcss!./node_modules/sass-loader/lib/loader.js!./src/stylesheets/base.scss 528 bytes {mini-css-extract-plugin} [built] [failed] [1 error]

ERROR in ./src/stylesheets/base.scss (./node_modules/css-loader/dist/cjs.js??ref--5-2!./node_modules/postcss-loader/src??postcss!./node_modules/sass-loader/lib/loader.js!./src/stylesheets/base.scss)
Module build failed (from ./node_modules/sass-loader/lib/loader.js):
Error: Cannot find module 'node-sass'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
    at Function.Module._load (internal/modules/cjs/loader.js:508:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.sassLoader (C:\users\dave\development\build-your-own-radar\node_modules\sass-loader\lib\loader.js:46:72)

i ｢wdm｣: Failed to compile.

Hello Team,

When i try to Build the docker image with the Dockerfile Getting " Invalid Reference Format " Error.

Sending build context to Docker daemon 1.262MB
Step 1/12 : FROM node:7.10.1 as source
invalid reference format

Thanks and Regards,
Arjun.M

Steps to Repro:
1] Copy the data from your current example here https://docs.google.com/spreadsheets/d/1YXkrgV7Y6zShiPeyw4Y5_19QOfu5I6CyH5sGnbkEyiI/pubhtml
2] Publish to web
3] Note that the new pub to web URL format no longer contains the sheet id.

I used both my corporate and personal accounts and both produced a Web pubhtml URL format that did not work.

I was able to get it to work with that same sheet by using the Google Sheet URL itself and copying the sheet ID from it directly. See http://stackoverflow.com/questions/11339500/how-to-fetch-the-id-of-a-google-spread-sheet-via-google-apps-script

Your package.json says that this project is under the isc license but the license.md says this is agpl. Could you update whichever is incorrect?

Thanks for open-sourcing the Radar!

What do you think about supporting local Markdown files as an input? Along with the wwwthoughtworks/build-your-own-radar Docker image, it would be a very simple way to get a Radar (or many radars) up. For example, I could setup a Git repo with:

.
|__ Dockerfile
|__ data
    |__ 2017-01
    |   |__ languages.md
    |   |__ platforms.md
    |   |__ tools.md
    |   |__ techniques.md
    |__ 2017-07
        |__ languages.md
        |__ platforms.md
        |__ tools.md
        |__ techniques.md

With the Dockerfile being a simple:

FROM wwwthoughtworks/techradar
COPY data /data

Some of the advantages I can think of:

• easy to browse and view on Github
• easier to edit long HTML blip descriptions than in a spreadsheet
• supports pull-requests for updating the Radar, where you can even preview the HTML snippets

The Markdown files could look something like this:

Languages and frameworks

Python 3

Python 3 introduced many useful features that are not backward compatible with Python 2.x. It also removed numerous Python 2.x features that were maintained for backward compatibility, making Python 3 easier to learn and use and more consistent with the rest of the language.

Jest

Our teams are delighted with the results of using Jest for front-end testing. It provides a ‘zero-configuration’ experience and has out-of-the-box features such as mocking and code coverage. You can apply this testing framework not only to React applications, but also to other JavaScript frameworks. One of Jest's often hyped features is UI snapshot testing. Snapshot testing would be a good addition to the upper layer of the test pyramid, but remember, unit testing is still the solid foundation.

Another option is one Markdown file per blip, with a YAML front-matter to specify the quadrant / ring / status. This would be easier to parse but likely harder to maintain, compared to all blips in 1 file (for example trying to find an existing blip).

What do you think?

I can run in my own machine, but I'm pretty confused how can I deploy in a web server. I try to generate npm run build, and copy dist folder, but is not working... Any clues?

When you paste a URL for a protected sheet into the form and click "build my radar" you are presented a Google auth form. I click on the account that has access to the protected sheet, and I receive the error, "Sign in with Google temporarily disabled for this app".

I clone the repository, did npm install and startet with npm run dev.

When building a radar by URL (my own or your example "https://docs.google.com/spreadsheets/d/1waDG0_W3-yNiAaUfxcZhTKvl7AUCgXwQw8mdPjCz86U/edit")
it always ends in "Oops! It seems like there are some problems with loading your data. ...".

With the hosted version https://radar.thoughtworks.com everything works fine, even with my own google sheets.

Hello - Is there a setting I can tweak so that the width of the ring is at least the width of its text label? Currently the text is getting overlapped with the next ring since there are not many blips in that ring. The issue does not happen when using a larger screen size/monitor

In the original radar, there are question mark to get the description of each ring. I would like to be able to add those with my own description for each statuses.

Hello @mohamednajiullah, i'm a graphic designer. I would like to know if you would be interested in having me make a logo for this project. If you accept, i will make a logo for this project and it's free.