scratchfoundation/scratch-www
1
0
Fork 0
mirror of https://github.com/scratchfoundation/scratch-www.git synced 2024-11-21 10:18:13 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
Standalone web client for Scratch
587 commits 218 branches 1 tag 460 MiB
JavaScript 83.4%
SCSS 15.8%
HTML 0.7%
EJS 0.1%
Find a file
Ray Schamp 19f469db48 Upgrade and quiet sass-linter 
These warnings were annoying me because the noise makes it easy to miss real issues.

The `no-mergeable-selectors` rule is one that we do want to have, but right now it asks that you merge selectors in different `@media` blocks.  When the next release happens we should put that back.

https://github.com/sasstools/sass-lint/issues/307

Similarly, we want `force-element-nesting` but there is a problem with that because there's no easy way to have a nested selector in a list of selectors.
https://github.com/sasstools/sass-lint/issues/575

Finally, until they implement per-line overrides, we have to silence `class-name-format` because we don't have control over the ReactModal class names.  It's a useful rule to keep class names consistent though.  Per-line ignores should be coming soon: https://github.com/sasstools/sass-lint/issues/70
2016-03-23 18:34:54 -04:00
bin Refactor build-locales a bit 2016-03-23 08:22:09 -04:00
server Use redux for session handling 2016-03-18 11:51:22 -04:00
src Upgrade and quiet sass-linter 2016-03-23 18:34:54 -04:00
static Use redux for session handling 2016-03-18 11:51:22 -04:00
test Refactor build-locales a bit 2016-03-23 08:22:09 -04:00
.eslintrc Add lint exception for formatMessage injection 2015-10-16 11:05:39 -04:00
.gitignore Updates based on feedback 2016-01-14 08:32:43 -05:00
.sass-lint.yml Upgrade and quiet sass-linter 2016-03-23 18:34:54 -04:00
.travis.yml Swap environments for CD. Resolves GH-351 2016-03-03 09:57:41 -05:00
CONTRIBUTING.md Revise focus of CONTRIBUTING, README 2016-01-28 13:07:58 -05:00
custom-locales.json Add languages to custom locales 2016-03-21 08:04:52 -04:00
languages.json Add nynorsk to dropdown 2016-03-16 11:55:54 -04:00
LICENSE Update license and add trademark notice 2016-01-31 13:07:21 -05:00
Makefile Refactor build-locales a bit 2016-03-23 08:22:09 -04:00
package.json Upgrade and quiet sass-linter 2016-03-23 18:34:54 -04:00
README.md Add new travis badge to readme 2016-02-18 15:16:49 -05:00
TRADEMARK Update license and add trademark notice 2016-01-31 13:07:21 -05:00
webpack.config.js Use redux for session handling 2016-03-18 11:51:22 -04:00

README.md

scratch-www

Standalone web client for Scratch

Build Status

Where am I?

Physically? No idea.

Digitally? You’re at Scratch’s open source web client!

We’re working to update the Scratch website to use a new codebase, contained in this repository.

We’re currently building Scratch using React and SCSS. Here are some resources to help you get acquainted with how we’re working on the Scratch codebase:

Before Getting Started

To Build

npm install
npm run build

To Run

npm start

During development, npm start watches any update you make to files in either ./static or ./src and triggers a rebuild of the project. In development the build is stored in memory, and not served from the ./build directory.

When running npm start, here are some important log messages to keep an eye out for:

  • webpack: bundle is now VALID. – the bundle has been loaded into memory and is now viewable in the browser. This will show up both once npm start has completed its setup, and also once updates you make to files have been re-compiled for viewing in the browser.
  • webpack: bundle is now INVALID. – if you see this, then it means you have made updates to files that are still being compiled for browser viewing. Pages will still be viewable, but they will not see any updates you made yet.

Once running, open http://localhost:8333 in your browser. If you wish to have the server reload automatically, you can install either nodemon or forever.

To stop

Use ^C to stop the node process npm start starts.

Configuration

npm start can be configured with the following environment variables

Variable Default Description
API_HOST https://api.scratch.mit.edu Hostname for API requests
NODE_ENV null If not production, app acts like development
PORT 8333 Port for devserver (http://localhost:XXXX)
FALLBACK '' Pass-through location for old site

NOTE: Because by default API_HOST=https://api.scratch.mit.edu, please be aware that, by default, you will be seeing and interacting with real data on the Scratch website.

To Test

npm test

Current issues with the development

We're currently in the process of transitioning into this web client from Scratch's existing structure. As we transition, there are going to be some issues along the way that relate to how this client needs to interact with the existing infrastructure to work properly in production.

On top of migrating to using this as our web client, Scratch is also transitioning into using a new API backend, Scratch REST API. As that is also currently in development and incomplete, we are set up to fall back to using existing Scratch endpoints if an API endpoint does not exist – which is where the FALLBACK comes in.

Most of the issues we have currently revolve around the use of FALLBACK. This variable is used to specify what url to fall back onto should a request fail within the context of this webclient, or when using the API_HOST. If not specified in the process, it will not be used, and any request that is not made through the web client or the API will be unreachable.

Setting FALLBACK=https://scratch.mit.edu allows the web client to retrieve data from the Scratch website in your development environment. However, because of security concerns, trying to send data to Scratch through your development environment won't work. This means the following things will be broken for the time being:

  • Login on the splash page (In the process of being fixed)
  • Some update attempts to production data made through a development version of the web client

Additionally, if you set FALLBACK=https://scratch.mit.edu, be aware that clicking on links to parts of the website not yet migrated over (currently such as Explore, Discuss, Profile, etc.) will take you to the Scratch website itself.