Repository files navigation

This project was transfered to WordPress:

• WordPress/openverse-frontend: The gateway to the Openverse. Openverse is a search tool for CC-licensed and public domain content across the internet.

For additional context see:

• 2020-12-07:Upcoming Changes to the CC Open Source Community — Creative Commons Open Source
• 2021-05-03:CC Search to Join WordPress - Creative Commons
• 2021-05-10:Welcome to Openverse – Openverse — WordPress.org
• 2021-12-13:Dear Users of CC Search, Welcome to Openverse - Creative Commons

CC Search is the official web application for theCreative Commons Catalog API. CC Search is an interface to search for content that is licensed under Creative Commons licenses or marked with public domain tools. This repositiory contains all the front-end code.

The application is avaliable atsearch.creativecommons.org.

The frontend app is built usingVue.JS andNuxtJS. You canlearn more about the migration to Nuxt.js here.

The user interface is powered byVocabulary, Creative Common's design system. If you have an issue with colors or a specific ui component, it should probably go in that repository.

Run the following commands in order to have the code up and running on your machine:

# installs dependenciesnpm install# Builds and serves assets with hot-reloadnpm run dev

Alternatively, you can use Docker to build and run the application. You just have to run:

docker-compose up

You should now have the application running and accessible athttp://localhost:8443.

You don't need to have the CC Search API running locally to be able to run the frontend application. It's configured to communicate, by default, with theAPI that's already publicly available. If you wish, you can change the URL of the API that's used during development by setting theAPI_URL environment variable.

You can run the unit tests by executing:

npm runtest

If you want to make your local development server accessible to the internet (for testing or showing someone something you're working on), you can usengrok. Follow the documentation on thengrok site to install it and set it up. Once you have it installed, get the development server for CC Search running and in a separate window/tab, run:

# The extra parameters are required to ensure that ngrok redirects to the HTTPS version of the site# and that the host header matches one that is accepted by the server# (ngrok's default hostname is randomly generated and is not whitelisted).ngrok http http://localhost:8443 -host-header="localhost:8443"

If you need to run a HTTP version (for example, if you're testing against third-party websites that do not accept the self-signed cerificate generated by the dev server), run the dev server usingnpm run dev and use the following command to startngrok:

ngrok http 8443 -host-header="localhost:8443"

The code in this repository is formatted usingprettier. If you have prettier setup in your code editor it should work out of the box; otherwise you can use thenpm run lintfix script to format and fix lint errors in your code. Checks are run to lint your code and validate the formatting on git precomit usinghusky.

You will need to fix any linting issues before comitting. We reccommend formatting your JavaScript files on save in your text editor. You can learn how to do this in Visual Studio Codehere.

CC Search usesCalVer for version numbering, in theYYYY.M.Micro format. This format is intentionally compatiable with NPM'ssemver parser.Micro is bumped whenever there are multiple releases in a month, for example2020.07.1 is the first release in July 2020, while2020.07.2 is the second.

Details about how to deploy the frontend code can be found on theCC Wiki (Accessible to CC Staff only).