Source code for official Yii website
Switch branches/tags
Nothing to show
Clone or download
Failed to load latest commit information.
apidoc Merge pull request #318 from yiisoft-contrib/extension-docs Apr 4, 2018
assets improve search key navigation and behavior Oct 26, 2018
commands Fix query Sep 13, 2018
components Hacky way to fill user forum ids Sep 26, 2018
config Corrected Uzbek language name Oct 25, 2018
controllers add additional header to fix #403 Oct 3, 2018
data guide WIP Nov 17, 2014
docs make search JS ready for launch Oct 6, 2017
env update production config templates Sep 7, 2018
jobs add versions to extension docs Apr 4, 2018
mail #169: Implemented email verification (#222) Sep 11, 2017
migrations keep source email in auth table and show it in admin Sep 19, 2018
models Hacky way to fill user forum ids Sep 26, 2018
notifications Common interface for pair objectType and objectId (#241) Oct 30, 2017
runtime initial import. Nov 7, 2014
scripts Add sitemap (#171) Oct 17, 2016
shots Pageres: Install command added to readme Dec 22, 2015
tests Added Codeception tests for contact and security forms (#226) Oct 5, 2017
views Don't display forum URL if user isn't registered at the forum Sep 26, 2018
web Update AuthController.php (#398) Sep 26, 2018
widgets User Contributed Notes Display DateTime Design (#362) Jun 12, 2018
.editorconfig Highlight style changed to 'github'. Front jumbo stage initial Dec 18, 2015
.gitignore Added Codeception tests for contact and security forms (#226) Oct 5, 2017 Update Nov 21, 2015
Makefile added extension documentation to offline docs Mar 29, 2018 Update (#361) Jun 9, 2018
codeception.yml Added Codeception tests for contact and security forms (#226) Oct 5, 2017
composer.json replace forum badges with discourse Sep 3, 2018
composer.lock update yiisoft/yii2-apidoc Oct 25, 2018
config.yml improve search key navigation and behavior Oct 26, 2018
gulpfile.js implement HTML, CSS and JS for Discourse Header Aug 9, 2018
init Replaces mcrypt by openssl (#187) May 2, 2017
init.bat project layout adjustment Nov 9, 2014
package.json gulp: touch generated files to update timestamp Apr 4, 2018 Minify-css deprecated in favor of cssnano. Jan 11, 2016
yarn.lock gulp: touch generated files to update timestamp Apr 4, 2018
yii.bat initial import. Nov 7, 2014
yii_test Added Codeception tests for contact and security forms (#226) Oct 5, 2017
yii_test.bat Added Codeception tests for contact and security forms (#226) Oct 5, 2017 Website

This project contains the source code for the Website.

If you want to contribute please get in touch with us using the issue tracker. We will set up some contribution guidelines soon.


Before you start, make sure you have installed composer and Node.js. If you are on Debian or Ubuntu you might also want to install the libnotify-bin package, which is used by Gulp to inform you about its status.

If you intend to use the Pageres client to generate screen shots for testing purposes, you need to install the pageres.cli tool globally:

npm install --global pageres-cli

And then you can use the script at the root of the source directory to generate screen shots.

Installation instructions

# clone the project
git clone


# install the composer asset plugin globally, if you haven't done so before
composer global require "fxp/composer-asset-plugin:^1.4.2"

# install the dependent composer packages
composer install

# install gulp globally if you haven't done so before
yarn global add gulp-cli

# install dependent NPM modules
yarn install

# initialize the application, choose "development"

Configure database connection in config/params-local.php. You may copy-paste and adjust components.db from config/params.php. Make sure to configure the following properties:

'api.baseUrl' => '/doc/api',
'guide.baseUrl' => '/doc/guide',
'components.db' => [
    // copy from params.php and adjust to your environment
'components.elasticsearch' => [
    // copy from params.php and adjust to your environment
// only if you want to test github auth:
'authclients' => [
    'github' => [
        'class' => 'yii\authclient\clients\GitHub',
        'clientId' => '...', // register an oauth app on github and enter details here
        'clientSecret' => '...',
        'scope' => 'user:email',
'siteAbsoluteUrl' => 'http://yiiframework.local',

 * @see
 * After creating an app you need to fill accessToken and accessTokenSecret:
 * Open App -> Keys and Access Tokens -> You Access Token -> Create my access token
'twitter.consumerKey' => '',
'twitter.consumerSecret' => '',
'twitter.accessToken' => '',
'twitter.accessTokenSecret' => ''

Continue with the following commands:

# run migrations
./yii migrate

# fill RBAC
./yii rbac/up

# build contributors page (this may take some time as it downloads a lot of user avatars from github)
./yii contributors/generate

# build js/css files
gulp build

# If you're on Windows you have to manually symlink or copy
# %appdata%/npm/node_modules/browser-sync to your app's node_modules

# The next step is for building the API documentation and the Guide files.
# It is optional for the site to be working but you will have no API docs and Guide.
# This step includes cloning the Yii 1 and Yii 2 repositories and a lot of computation,
# so you might want to skip it on the first install.
# This also requires an instance of elasticsearch to be configured and running
# (if you do not have it, it will still run, but the site search will not work).
# It also assumes you have pdflatex installed for building PDF guide docs.
# You may also build only parts of the docs, run  make help  for the available commands.
make docs

# populate the search index by running
./yii search/rebuild

Web Server Setup

Define a host name yiiframework.local that points to localhost.

Define a virtual host yiiframework.local which uses as its document root.

If you are using Apache, add the following configuration for the folder to hide the entry script:

RewriteEngine on

# if a directory or a file exists, use it directly
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

# otherwise forward it to index.php
RewriteRule . index.php

Data Import

For importing data from the old website, the following steps are necessary:

  • import data by running ./yii import command
  • rebuild user badges by running ./yii badge/rebuild
  • calculate user ranking ./yii user/ranking.

If you don't have that data, you can work with dummy content:

  • To fill the database with dummy content, you may run the command ./yii fake-data. You may run it multiple times to generate more data.
  • rebuild user badges by running ./yii badge/rebuild.
  • calculate user ranking ./yii user/ranking.

To assign users extra permissions use ./yii rbac/assign.

Cron jobs

The following commands need to be set up to run on a regular basis:

command interval Purpose
yii sitemap/generate daily regenerate sitemap.xml
yii contributors/generate weekly update contributors list on team page
yii badge/update hourly update badges for users in badge_queue
yii cron/update-packagist hourly update packagist extension data
yii user/ranking daily update user ranking

Additionally, queue/listen should run as a daemon or queue/run as a cronjob.


This section covers notes for deployment on a server, you may not need this for your dev env. OS is assumed to be debian Stretch.

apt-get install texlive-full git nodejs make


The contributors list and the avatar thumbnails is generated by a console command:

./yii contributors/generate

It will connect to Github via the API and fetch a list of contributors, generate data/contributors.json and thumbnail images of the user avatars in data/avatars and finally invoke Gulp to generate a sprite image and Sass code.

It would be a good idea to set up a Cron job to run that once in a while - perhaps once each month.

If you generate a personal Github token (from your Github profile settings section) you can tell the contributors/generate function to make use of it by creating a file in the data directory (@app/data) called github.token with the token pasted into it (one line, no line-break). That should solve most issues related to the API rate limit imposed by Github.


  commands/           contains console commands (controllers)
  config/             contains application configurations
  controllers/        contains Web controller classes
  data/               contains important data generated by different commands
  env/                contains environment-dependent files
          fonts/      contains fonts
          scss/       contains Sass source files
          js/         contains JS source files
  mail/               contains view files for e-mails
  models/             contains model classes
  node_modules/       contains installed NPM packages
  runtime/            contains files generated during runtime
  scripts/            contains shell scripts
  vendor/             contains dependent 3rd-party packages
  views/              contains view files for the Web application
  web/                contains the entry script and Web resources



  • During development, run gulp to watch view, Sass and JS file changes and automatically build target CSS/JS files. This command will also launch a browser window which is connected to browsersync.
  • At any time, run gulp build to manually rebuild target CSS/JS files from source Sass/JS files.
  • If you only want to watch for changes, you can issue the command gulp watch
  • To build the assets for production, specify the production flag: gulp build --production

CSS Files

  • Use Sass files to define CSS styles.
  • All Sass files should be put under assets/src/scss and listed in assets/src/scss/all.scss.
  • Usually each controller corresponds to a single Sass file whose name is the same as the controller ID. For example, the GuideController has a Sass file named _guide.scss.
  • All Sass source files, except all.scss should have a leading underscore in the name. Sass will ignore files starting with an underscore so that only one CSS file will be produced (all.css).
  • For information about where each file should be put, please consult the master include file all.scss.

JS Files

  • All JS files should be put under assets/src/js and listed in config.yml.
  • Usually each controller corresponds to a single JS file whose name is the same as the controller ID. For example, the GuideController has a JS file named guide.js.