Giter Site home page Giter Site logo

creativecommons / chooser Goto Github PK

View Code? Open in Web Editor NEW
94.0 21.0 124.0 21.61 MB

The new and improved CC license selection tool.

Home Page: https://chooser-beta.creativecommons.org

License: MIT License

JavaScript 39.07% Vue 30.73% HTML 0.67% Shell 0.17% SCSS 3.21% CSS 25.89% Dockerfile 0.26%
creative-commons vuejs open-source cc-licenses vue hacktoberfest

chooser's Introduction

GitHub contributors GitHub Sponsors GitHub npm Libraries.io dependency status for latest release, scoped npm package npm GitHub issues GitHub Repo stars GitHub forks

Chooser

The Creative Commons License Chooser is meant to help people learn about CC licenses, and select the license that best fits their needs. The new version in this repo places greater importance on usability, and an educational experience of the six CC licenses.

About

Repository containing the source code for the new Creative Commons License Chooser. The new chooser is still in beta, and a beta deployment can be found here.

This site is built using Vue.js (and vue-cli).

Roadmap

Tasks, issues, and discussion related to the release of the new chooser are tracked with the Launch Milestone.

Code of conduct

CODE_OF_CONDUCT.md:

The Creative Commons team is committed to fostering a welcoming community. This project and all other Creative Commons open source projects are governed by our Code of Conduct. Please report unacceptable behavior to [email protected] per our reporting guidelines.

Contributing

See CONTRIBUTING.md.

Using Docker

Containers

The docker-compose.yml file defines the following containers:

  1. chooser-web - simple NGINX container serving docs/
  2. chooser-node - Node14 container

Docker desktop required

Before proceeding, ensure you have Docker installed on your local machine. If not, download and install Docker Desktop by visiting Docker's official website and follow the installation instructions.

Startup containers

The containers can be started with:

docker compose up

(See Docker Compose overview | Docker Docs for more information on managing containes with docker compose.)

Initial setup

Before the chooser-node container can be used effectively, a clean install of NPM packages from package-lock.json is required:

docker compose exec chooser-node npm ci

This step generally only needs to be done once.

Run Node development server

  1. Startup containers (see above)
  2. Complete initial setup (see above)
  3. Run Node development server
    docker compose exec chooser-node npm run serve

Create production (standalone) build

  1. Startup containers (see above)
  2. Complete initial setup (see above)
  3. Run Node development server
    docker compose exec chooser-node npm run build
    • (this automatically copies the generated files from dist/ to docs/)

The chooser is deployed to GitHub Pages. The source files for the beta deployment are contained in the ./docs/ dir, and are live. Any changes to this directory's contents will be automatically deployed, so please take care when making modifications to this location.

Create standalone (production) build

  1. Startup containers (see above)
  2. Complete initial setup (see above)
  3. Run Node development server
    docker compose exec chooser-node npm run build
    • (this automatically copies the generated files from dist/ to docs/)

The chooser is deployed to GitHub Pages. The source files for the beta deployment are contained in the ./docs/ dir, and are live. Any changes to this directory's contents will be automatically deployed, so please take care when making modifications to this location.

For an embedded standalone build (no header nor footer), run:

docker compose exec chooser-node VUE_APP_CC_OUTPUT=embedded npm run build

(please don't commit embedded builds to docs/)

Create a web component build

  1. Startup containers (see above)
  2. Complete initial setup (see above)
  3. Run Node development server
    docker compose exec chooser-node npm run build-component

This will create a file in the dist/ folder named license-chooser.min.js. It can be used to load the web-component in any JS project. There is also a sample demo.html created.

To be able to use the file it should either be rendered statically from the integrater's web-app or be published on a CDN. Following code can be used to integrate this in other apps.

Note: the Chooser component depends on Vue 2.x, as can be seen in the following example.

<script src="https://cdn.jsdelivr.net/npm/[email protected]"></script>
<script src="https://unpkg.com/@creativecommons/chooser/dist/license-chooser.js"></script>

<license-chooser></license-chooser>

For an embedded web component build (no header nor footer), run:

docker compose exec chooser-node VUE_APP_CC_OUTPUT=embedded npm run build-component

Perform unit tests on standalone or embedded build

  1. Startup containers (see above)
  2. Complete initial setup (see above)
  3. Run unit tests
    docker compose exec chooser-node npm run test:unit

Perform unit tests on web-component build

  1. Startup containers (see above)
  2. Complete initial setup (see above)
  3. Create a web component build (see above)
  4. Run unit tests
    docker compose exec chooser-node npm run test-component
    • It starts a server with the dist/demo.html on which tests can be run.

Perform Cypress tests

  1. Startup containers (see above)
  2. Run Cypress tests
    docker run -it -v $PWD:/e2e -w /e2e -e CYPRESS_baseUrl=http://host.docker.internal:8888 cypress/included:latest
    • (This will download the cypress/included image when first run)

CSS Build

The Chooser uses PostCSS plugin for PurgeCSS to make CSS bundle size smaller. It automatically removes unused CSS based on the classes found in the final built bundle. Some styles for dynamic components or dynamically-imported files can also be removed. If you find that the built site misses some styles, you can manually add the necessary classes or Regex expressions to the safelist array in the postcss.config.js file.

Embedded screenshot

The site can be built in two different modes: embedded and standalone. Embedded mode removes the header and footer from the application, resulting in the following appearance:

Application built in embedded mode

To build into embedded mode, set the environment variable VUE_APP_CC_OUTPUT=embedded on your server before building. If VUE_APP_CC_OUTPUT is unset or set to a different value, the app will build in the default standalone mode, with its own header and footer.

chooser's People

Contributors

acagastya avatar alessandrodolci avatar bobulous avatar cc-creativecommons-github-io-bot avatar cognitive137 avatar cronus1007 avatar dependabot[bot] avatar dhruvkb avatar dijitali avatar fkohrt avatar gawandeabhishek avatar hemanth-hk avatar jackiebinya avatar jordanruetz avatar kgodey avatar muluhgodson avatar neeraj-2 avatar obulat avatar onyijne avatar pollett21 avatar possumbilities avatar priscilauchoa avatar rohan-goel avatar shailee-m avatar shuence avatar soustab10 avatar tanmay1201 avatar timidrobot avatar yaya-usman avatar zackkrida avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

chooser's Issues

Instances of "chooser" related language in CC repos

There are a small number of places that the word "chooser" is mentioned in the descriptions and names of various CC repos. For each of these, it may be worth looking at whether or not the language should be changed.

This list may or may not be exhaustive, and is mostly meant to track these instances :)

Some things I didn't catch in last review

Hey Olga, I missed some things in the last review. I was on mobile and everything looked good so I approved. Please submit another PR with the following fixes:

  • Please add the following tags for mobile home screen shortcut icons:
    • <link rel="icon" type="image/png" href="https://d15omoko64skxi.cloudfront.net/wp-content/uploads/2016/05/cc-site-icon-300x300.png" sizes="192x192">
    • <link rel="apple-touch-icon-precomposed" href="https://d15omoko64skxi.cloudfront.net/wp-content/uploads/2016/05/cc-site-icon-300x300.png">
  • Change og:title content to "Choose a License"
  • Add <meta property="of:type" content="website">
  • Please change og:description to "Want to license your work with Creative Commons, but not sure where to start, or which license is right for you? Use our license chooser!"
  • Change og:url to https://beta-chooser.creativecommons.org
  • The og:image content currently points to a screenshot for the CC WP plugin, please change to the CC logo for now.
  • Change twitter:site to creativecommons.org
  • There's a typo in the noscript section, "hello doesn't work properly"

Modals have no Margins on Mobile and Tablet Breakpoints

Describe the bug
There are no left or right margins on mobile and tablet breakpoints when using Bulma modals.

This issue is already known and being tracked: jgthms/bulma#2387, there is (sort of) a fix, but it's hacky and not ideal.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]
  • Bulma Version 0.7.4

Write tests for IconSelector component

Describe the solution you'd like
e2e and unit tests need to be written for the IconSelector.vue component (./src/components/IconSelector.vue). Please write e2e tests in a new file named IconSelector.js in ./test/e2e/specs/, and unit tests in a new file named IconSelector.specs.js in ./test/unit/specs/.

The frameworks being used are (Jest)[https://jestjs.io/] for unit testing, and the (nightwatch.js)[https://nightwatchjs.org/] for e2e testing.

Additional context
Please comment on this issue to tell us that you're interested in working on it before getting started!

Feedback Form

Before the blog post, a Google Form needs to be made to take user feedback about the new chooser. A Vue component will also need to be made for linking to this form.

Write tests for HTMLGenerator component

Describe the solution you'd like
e2e and unit tests need to be written for the HTMLGenerator.vue component (./src/components/HTMLGenerator.vue). Please write e2e tests in a new file named HTMLGenerator.js in ./test/e2e/specs/, and unit tests in a new file named HTMLGenerator.specs.js in ./test/unit/specs/.

The frameworks being used are (Jest)[https://jestjs.io/] for unit testing, and the (nightwatch.js)[https://nightwatchjs.org/] for e2e testing.

Additional context
Please comment on this issue to tell us that you're interested in working on it before getting started!

Write tests for HelpSection component

Describe the solution you'd like
e2e and unit tests need to be written for the HelpSection.vue component (./src/components/HelpSection.vue). Please write e2e tests in a new file named HelpSection.js in ./test/e2e/specs/, and unit tests in a new file named HelpSection.specs.js in ./test/unit/specs/.

The frameworks being used are (Jest)[https://jestjs.io/] for unit testing, and the (nightwatch.js)[https://nightwatchjs.org/] for e2e testing.

Additional context
Please comment on this issue to tell us that you're interested in working on it before getting started!

UI Improvements

Before the launch of the chooser, some improvements to the chooser's UI need to be made. Some ideas of things to do include:

  • Guiding users better - clearer action items
  • Further integration with CC vocabulary
  • Further rounds of usability testing
  • Declutter

When using npm run serve on fresh clone, get dependency not found error.

Describe the bug
When using a fresh clone of the repo, on the WIP-Redesign and AttributionDetails branches, and running npm run serve, after running npm i, I get

ERROR  Failed to compile with 1 errors
This dependency was not found:

* @fortawesome/free-solid-svg-icons in ./src/main.js

To install it, you can run: npm install --save @fortawesome/free-solid-svg-icons

This package probably just got lost from package.json in the transition to Vue cli, no big deal :)

To Reproduce
Steps to reproduce the behavior:

  1. Clone repo, and switch to AttributionDetails or WIP-Redesign branch
  2. Run npm i
  3. Run npm run serve
  4. See error

Desktop (please complete the following information):

  • OS: Windows 10 1809 17763.914
  • npm version: 6.4.1
  • node version: 10.15.3

Add unit and e2e tests for AttributionDetailsStep component

Unit and e2e tests need to be written for the AttributionDetailsStep component. Unit tests are done with Jest, and e2e tests are done with nightwatch.

Please remember to test the following things:

  • That individual parts of the component are present when appropriate. (unit and e2e)
  • That any computed props and methods work properly, if there are any. (unit)
  • Any common interactions between the user and component, if there are any. (e2e)
  • Any other functionality unique to the component being tested!

Additional Context

Removing the "Free Cultural Works" Designation

Why are we dragging forward the Free Cultural Works designation in the license chooser?

Ostensibly, the chooser is used by novice users who need to be taken step by step through each of the considerations involved in choosing a CC license. Why confuse that already daunting process with this icon and link? The icon and link appear with no context in the "Your License" pane on the right. Providing the necessary context for them would only further complicate things for novice users. In teaching 1000s of people about Creative Commons over the years I have seen many people get confused when they encounter the FCW icon / link in the middle of the license chooser process.

We have a rare opportunity to remove a large source of confusion from the license selection process. I believe we should remove the icon and link.

Add unit and e2e tests for FirstStep component

Unit and e2e tests need to be written for the FirstStep component. Unit tests are done with Jest, and e2e tests are done with nightwatch.

Please remember to test the following things:

  • That individual parts of the component are present when appropriate. (unit and e2e)
  • That any computed props and methods work properly, if there are any. (unit)
  • Any common interactions between the user and component, if there are any. (e2e)
  • Any other functionality unique to the component being tested!

Additional Context

Add unit and e2e tests for CopyrightWaiverStep component

Unit and e2e tests need to be written for the CopyrightWaiverStep component. Unit tests are done with Jest, and e2e tests are done with nightwatch.

Please remember to test the following things:

  • That individual parts of the component are present when appropriate. (unit and e2e)
  • That any computed props and methods work properly, if there are any. (unit)
  • Any common interactions between the user and component, if there are any. (e2e)
  • Any other functionality unique to the component being tested!

Additional Context

Rewrite Unit/ e2e tests

The current unit and e2e tests were written before the current Outreachy internship round, and need to be updated for the current codebase. We need unit tests for components and utils, but some components won't need tests because they mock Vocabulary components, and will be deprecated soon.

Unit tests are done with Jest, and e2e tests are done with nightwatch.

This task is partially blocking #77. The reason for the block was that the tests written at the time the PR was created were old and would always fail. Once we've got some tests updated, we can merge it.

The components that need tests are:

  • AttributionDetailsStep (#112)
  • CopyrightWaiverStep (#113)
  • DropdownStep (#114)
  • FirstStep (#115)
  • HelpSection (#116)
  • LicenseCode (#117)
  • LicenseCopy (#122)
  • LicenseDetailsCard (#118)
  • LicenseDropdown (#120)
  • LicenseUseCard (#121)
  • Step (#123)
  • Stepper (#126)
  • App (#124)
  • All methods in ./src/utils/license-utilities.js (#125)

Note that this specific issue is not up for grabs, and is meant to track meta discussion about the larger task of creating tests as a whole.

SA Checkbox Unresponsive to Styling, Check Missing

Describe the bug
There is a check box on the page for toggling SA. The checkbox background is currently a light green color, and the check icon is missing. This checkbox is not responsive to even inline styling.

Expected behavior
The checkbox should be the normal CC orange (same color as the switch to the left), and the check icon should be showing.

Screenshots
Broken sa-check

Desktop (please complete the following information):

  • OS: [e.g. iOS] Windows 10 Pro 1809 17763.557
  • Browser [e.g. chrome, safari] Chrome
  • Version [e.g. 22] 75.0.3770.100 (64-bit)

Additional context
Possibly related to this issue in the repo for the checkbox styling library. I've tried the fix reccomended in this issue, but the check still didn't show. This is unrelated to the color.

Write tests for SelectedLicense component

Describe the solution you'd like
e2e and unit tests need to be written for the SelectedLicense.vue component (./src/components/SelectedLicense.vue). Please write e2e tests in a new file named SelectedLicense.js in ./test/e2e/specs/, and unit tests in a new file named SelectedLicense.specs.js in ./test/unit/specs/.

The frameworks being used are (Jest)[https://jestjs.io/] for unit testing, and the (nightwatch.js)[https://nightwatchjs.org/] for e2e testing.

Additional context
Please comment on this issue to tell us that you're interested in working on it before getting started!

SA IconSelector value resets on hide, but chooser is not updated

Describe the bug
The SA IconSelector works, except for when it is toggled with the ND IconSelector. At this point, the component's state resets to default, but the change is not emitted to the parent Chooser component.

This can be temporarily solved by removing the conditional rendering from the sa IconSelector component, but it's not ideal, and not a permanent fix.

To Reproduce
Steps to reproduce the behavior:

  1. Click SA Selector
  2. Click ND Selector to add ND to selected license
  3. Click ND Selector to remove ND to selected license
  4. See error (SA Selector state reset to default, state reset not emitted to the Chooser component)

change the chooser so it links to license translation in same language as chooser

Right now, when you view the license chooser page in a language like Finnish for which we have an official translation, the chooser still links to the English version of the license.

Is it possible to change that so it links to the official translation in that same language? This is not a super high-priority, but seems like something we should eventually fix if we can.

Vocabulary styles being overriden by custom styling

Due to issues with specificity, styling provided by CC Vocabulary is being overriden by styling from other third-party libraries and custom written CSS, leading to a different UI than what is expected. This is causing components to look broken or erratically styled.

To Reproduce
Steps to reproduce the behavior:

  1. Check out the branch from PR #30
  2. Run the development server

Expected behavior
The components should render like the examples in the Vocabulary styleguide.

Screenshots
image
^ Broken Footer and Locale
image
^ Expected Footer and Locale

Desktop (please complete the following information):

  • OS: Linux (Fedora 30)
  • Browser: Firefox
  • Version: 68

Dependency issues with vue-vocab and vocab on fresh clone of yes-no-change branch

Describe the bug
The versions of both vocabulary and vue-vocabulary required in package.json are not in the npm registry. I tried manually updating both to most current (0.0.0-alpha.30 for both), and then started getting import and dependency not found errors. One of these errors was specifically for @creativecommons/vocabulary/css/vocabulary.css.

My guess is that you were working with vocab versions that have since been deprecated, and (for some reason) taken off of npm, and that there are now breaking changes in 0.0.0-alpha.30, which breaks imports and other dependency related stuff :/

To Reproduce
Steps to reproduce the behavior:

  1. Clone repo
  2. Switch to yes-no-change branch
  3. Run npm i
  4. See error

Desktop (please complete the following information):

  • OS: Win 10 Pro 1809 17763.973
  • npm version: 6.13.6
  • node version: 12.14.1

Add unit and e2e tests for DropdownStep component

Unit and e2e tests need to be written for the DropdownStep component. Unit tests are done with Jest, and e2e tests are done with nightwatch.

Please remember to test the following things:

  • That individual parts of the component are present when appropriate. (unit and e2e)
  • That any computed props and methods work properly, if there are any. (unit)
  • Any common interactions between the user and component, if there are any. (e2e)
  • Any other functionality unique to the component being tested!

Additional Context

Prep repo for outside contributors

There are some small bits and bobs around the repo that should be done before we open it up to outside contributors. These are the ones I've noticed:

  • Update npm script names in root README and ./tests/ README
  • Delete Feedback.vue (deprecated)
  • Delete LicenseIconography.vue (deprecated)
  • Deleting old unit and e2e tests and snapshots, but leave a couple of both as examples for contributors.

Changes to NC IconSelector not updating LicenseDescription when ND is selected

Describe the bug
When the ND IconSelector is selected, the NC IconSelector properly updates the selected license, but not the LicenseDescription

To Reproduce
Steps to reproduce the behavior:

  1. Go to https://chooser-beta.creativecommons.org/
  2. Click on ND icon selector
  3. See IconDescription update
  4. Click on NC icon selector
  5. See IconDescription not update

Expected behavior
The IconDescription should update and show the proper Adapt, Share, and Description content.

Desktop (please complete the following information):

  • OS: Windows 10 Pro 1809 17763.678
  • Browser 76.0.3809.132 (Official Build) (64-bit)

Internationalization

The chooser needs to be available in languages other than english before it's launched. This translation with be done with Transifex. Transifex integration needs to be coordinated with CC Engineering before it goes live.

Use HTTPS links for the license chooser

Feedback through info@
In the license selection page [Choose a License] where it spits out html metadata, can you modify it so that it generates the links in https (it currently gives http, but changing that to https doesn't break anything)?

Screen Shot 2020-10-21 at 09 16 11

No Tests Written... yet!

Currently, there are no tests written for the chooser. This issue is to track discussion related to implementing tests.

Write tests for CopyButton component

Describe the solution you'd like
e2e and unit tests need to be written for the CopyButton.vue component (./src/components/CopyButton.vue). Please write e2e tests in a new file named CopyButton.js in ./test/e2e/specs/, and unit tests in a new file named CopyButton.specs.js in ./test/unit/specs/.

The frameworks being used are (Jest)[https://jestjs.io/] for unit testing, and the (nightwatch.js)[https://nightwatchjs.org/] for e2e testing.

Additional context
Please comment on this issue to tell us that you're interested in working on it before getting started!

Todo for next round of cleanup

This is a thread of little bits and pieces here and there to be fixed. I will take care of this in my next round of cleanup.

Write tests for LicenseDescription component

Describe the solution you'd like
e2e and unit tests need to be written for the LicenseDescription.vue component (./src/components/LicenseDescription.vue). Please write e2e tests in a new file named LicenseDescripion.js in ./test/e2e/specs/, and unit tests in a new file named LicenseDescription.specs.js in ./test/unit/specs/.

The frameworks being used are (Jest)[https://jestjs.io/] for unit testing, and the (nightwatch.js)[https://nightwatchjs.org/] for e2e testing.

Additional context
Please comment on this issue to tell us that you're interested in working on it before getting started!

Error: Cannot find module 'webpack-cli/bin/config-yargs'

Describe the bug
When trying to build by running npm run dev the webpack server fails with the following error:

$ npm run dev

> [email protected] dev /home/user/projects/cc-chooser
> webpack-dev-server --inline --progress --config build/webpack.dev.conf.js

internal/modules/cjs/loader.js:589
    throw err;
    ^

Error: Cannot find module 'webpack-cli/bin/config-yargs'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:587:15)
    at Function.Module._load (internal/modules/cjs/loader.js:513:25)
    at Module.require (internal/modules/cjs/loader.js:643:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.<anonymous> (/home/user/projects/cc-chooser/node_modules/webpack-dev-server/bin/webpack-dev-server.js:84:1)
    at Module._compile (internal/modules/cjs/loader.js:707:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:718:10)
    at Module.load (internal/modules/cjs/loader.js:605:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:544:12)
    at Function.Module._load (internal/modules/cjs/loader.js:536:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] dev: `webpack-dev-server --inline --progress --config build/webpack.dev.conf.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] dev 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!     /home/user/.npm/_logs/2019-11-11T18_03_07_465Z-debug.log

To Reproduce
Steps to reproduce the behavior:

  1. clone the repo
  2. run npm i
  3. run npm run dev

Expected behavior
It should build and run a server with the buld

Desktop (please complete the following information):

  • OS: 4.15.0-58-generic #64-Ubuntu
  • Node: v12.13.0
  • NPM: 6.12.0

Styling and text bugs when dist bundle is served

Describe the bug
When the chooser's dist bundle is served, there are some visual bugs. This issue serves as a thread for tracking and fixing them.

To Reproduce
Steps to reproduce the behavior:

  1. Clone repo
  2. npm i
  3. npm run build
  4. Start an HTTP(S) server from build
  5. See bugs

Observed on:

  • Chrome Versions: 79.0

Footer Component Not Rendering

Describe the bug
The footer component is not rendering

To Reproduce
Steps to reproduce the behavior:

  1. Go to site
  2. Scroll to bottom of page
  3. See that footer is not rendering

Desktop (please complete the following information):

  • OS: Windows 10 Pro 1809 17763.678
  • Browser: Chrome 76.0.3809.100 64-Bit

Additional context
In console, two errors are shown:

[Vue warn]: Error in render: "TypeError: _vm.$t is not a function"

found in

---> <Footer>
            <App> at src/App.vue
                <Root>

and

TypeError: _vm.$t is not a function
    at eval (vocabulary.common.js?b546:10811)
    at Proxy.renderList (vue.esm.js?efeb:2639)
    at Proxy.Footervue_type_template_id_3f430c69_scoped_true_render (vocabulary.common.js?b546:10811)
    at VueComponent.Vue._render (vue.esm.js?efeb:3551)
    at VueComponent.updateComponent (vue.esm.js?efeb:4069)
    at Watcher.get (vue.esm.js?efeb:4482)
    at new Watcher (vue.esm.js?efeb:4471)
    at mountComponent (vue.esm.js?efeb:4076)
    at VueComponent.Vue.$mount (vue.esm.js?efeb:9057)
    at VueComponent.Vue.$mount (vue.esm.js?efeb:11953)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.