forkcms  5.5.2
About: Fork is an CMS "for beginners and professionals" with an "intuitive and user friendly interface".
  Fossies Dox: forkcms-5.5.2.tar.gz  ("inofficial" and yet experimental doxygen-generated source code documentation)  

Some Fossies usage hints in advance:

  1. To see the Doxygen generated documentation please click on one of the items in the "quick index" bar above or use the side panel at the left which displays a hierarchical tree-like index structure and is adjustable in width.
  2. If you want to search for something by keyword rather than browse for it you can use the client side search facility (using Javascript and DHTML) that provides live searching, i.e. the search results are presented and adapted as you type in the Search input field at the top right.
  3. Doxygen doesn't incorporate all member files but just a definable subset (basically the main project source code files that are written in a supported language). So to search and browse all member files you may visit the Fossies forkcms-5.5.2.tar.gz contents page and use the Fossies standard member browsing features (also with source code highlighting and additionally with optional code folding).
forkcms Documentation

Fork CMS

Build Status Latest Stable Version License Code Coverage Slack Status Documentation Status

Installation

  1. Make sure you have composer installed.
  2. Run composer create-project forkcms/forkcms . in your document root.
  3. Browse to your website
  4. Follow the steps on-screen
  5. Have fun!

Dependencies

Remark: If you are using GIT instead of composer create-project or the zip-file from http://www.fork-cms.com, you should install our dependencies. The dependencies are handled by composer

To install the dependencies, you can run the command below in the document-root:

composer install -o

Security

If you discover any security related issues, please email core@.nosp@m.fork.nosp@m.-cms..nosp@m.com instead of using the issue tracker.

SSL

If you want to activate https redirection, go into the .htaccess file and uncomment the lines about https.

Bugs

If you encounter any bugs, please create an issue on Github. If you're stuck or would like to discuss Fork CMS, talk to us on slack!

Running the tests

We use phpunit as a test framework. It's installed when using composer install. To be able to run them, make sure you have a database with the same credentials as your normal database and with the name suffixed with _test.

Because we support multiple php versions it gave some issues. Therefore we use the bridge from symfony.

Running the tests:

composer test

Running only the unit tests or the functional tests

 composer test -- --testsuite=functional
 composer test -- --testsuite=unit

Styling the backend

The backend uses Bootstrap in combination with Sass. To make changes, you should make the changes into the scss-files, and regenerate the real css with gulp build.

Yarn

We use yarn to install our dependencies. For now we have a gulp-script that moves everything to the correct directories. So if you change the dependencies, make sure you run gulp build.

Discussion

The Fork CMS team