Go to file
Nathaniel Catchpole 688e42fd92 Issue #2683421 by xjm, alexpott, hussainweb: Remove incremental and rollback options from the UI (and add them back when they are more stable) 2016-03-22 19:17:36 +09:00
core Issue #2683421 by xjm, alexpott, hussainweb: Remove incremental and rollback options from the UI (and add them back when they are more stable) 2016-03-22 19:17:36 +09:00
modules Issue #2532148 by timmillwood, davidwbarratt: Modules cannot be put in ./modules/vendor 2015-07-27 13:32:52 +01:00
profiles Issue #2568439 by anchal29, hussainweb, priya.chat, r_sharma08, drupal.ninja03, anil280988, snehi, tedbow, joyceg, amit.drupal, jhodgdon: profiles/README.txt incorrectly states that installation profiles do not 'have any effect on' already running sites 2015-12-23 01:34:24 +00:00
sites Issue #2536682 by eporama, r_sharma08, snehi, rakesh.gectcr, chegor, Prashant.c: default.settings.php database instructions need to be user friendly 2016-02-17 15:56:50 +09:00
themes Issue #2115737 by darol100, rhuffstedtler, andythomnz, jemandy, ijf8090, zealfire, er.pushpinderrana, jhodgdon: Make the text in modules, themes, and profiles README.txt files more user-friendly 2015-06-02 23:25:18 +01:00
.csslintrc Issue #2222049 by LewisNyman, Michael Hodge Jr, sqndr: Add a .csslintrc file that's in line with our CSS standards. 2014-09-08 15:11:43 +01:00
.editorconfig Issue #2654894 by felribeiro, webflo: Use an indent of 4 spaces for composer.json 2016-02-02 15:10:10 +09:00
.eslintignore Issue #2380389 by webflo, Mile23, davidwbarratt, timmillwood, hussainweb, tstoeckler, bojanz, yched, MKorostoff, alexpott, webchick: Use a single vendor directory in the root 2015-09-30 12:58:08 -07:00
.eslintrc Issue #2660034 by naveenvalecha: Move .eslintrc into core/.eslintrc 2016-02-02 15:02:07 +00:00
.gitattributes Issue #2380389 by webflo, Mile23, davidwbarratt, timmillwood, hussainweb, tstoeckler, bojanz, yched, MKorostoff, alexpott, webchick: Use a single vendor directory in the root 2015-09-30 12:58:08 -07:00
.htaccess Issue #2408321 by mfb, D34dMan, C_Logemann, serg2, walterebert, sanduhrs, John Morahan: Support RFC 5785 by whitelisting the .well-known directory 2016-02-29 09:32:03 +09:00
README.txt Issue #2491155 by mikeburrelljr, Mac_Weber, opdavies: Update drupal.org and kernel.org URLs in core modules (Follow-up to 2489912) 2015-05-24 15:08:46 -05:00
autoload.php Issue #2380389 by webflo, Mile23, davidwbarratt, timmillwood, hussainweb, tstoeckler, bojanz, yched, MKorostoff, alexpott, webchick: Use a single vendor directory in the root 2015-09-30 12:58:08 -07:00
composer.json Issue #2654894 by felribeiro, webflo: Use an indent of 4 spaces for composer.json 2016-02-02 15:10:10 +09:00
composer.lock Issue #2638856 by bojanz, webflo, SiliconMind: Unable to install modules with core dependencies via composer 2016-03-14 10:49:22 +00:00
example.gitignore Issue #1475510 by timmillwood, hussainweb, davidwbarratt, alexpott, Mile23, pfrenssen, claudiu.cristea, webchick, catch, Crell, patcon, RobLoach, kim.pepper, dawehner, neclimdul, Mixologic, gagarine, sun, nod_, effulgentsia, drumm, Sylvain Lecoy, jhedstrom, katbailey, xjm, klausi, Seldaek, Barryvdh: Remove external dependencies from the core repo and let Composer manage the dependencies instead 2016-03-14 08:10:45 +09:00
index.php Issue #2389811 by znerol, mpdonadio, alexpott, hussainweb, neclimdul: Move all the logic out of index.php (again) 2015-06-03 18:06:46 +01:00
robots.txt Issue #2364343 by damien_vancouver, criz, ksenzee, joegraduate, Neograph734, droplet, pounard, jp.stacey, ciss: Fix robots.txt to allow Google access to CSS, JavaScript and image files 2016-02-29 16:18:01 +09:00
update.php Issue #2646410 by claudiu.cristea, dawehner: Container cannot be saved to cache 2016-02-29 14:18:08 +09:00
web.config Issue #2392153 by mparker17, hussainweb, chris.smith, alexpott, dawehner: Disallow composer.json and composer.lock from being indexed 2016-01-18 14:53:59 +00:00

README.txt

CONTENTS OF THIS FILE
---------------------

 * About Drupal
 * Configuration and features
 * Installation profiles
 * Appearance
 * Developing for Drupal
 * More information

ABOUT DRUPAL
------------

Drupal is an open source content management platform supporting a variety of
websites ranging from personal weblogs to large community-driven websites. For
more information, see the Drupal website at https://www.drupal.org, and join
the Drupal community at https://www.drupal.org/community.

Legal information about Drupal:
 * Know your rights when using Drupal:
   See LICENSE.txt in the "core" directory.
 * Learn about the Drupal trademark and logo policy:
   https://www.drupal.com/trademark

CONFIGURATION AND FEATURES
--------------------------

Drupal core (what you get when you download and extract a drupal-x.y.tar.gz or
drupal-x.y.zip file from https://www.drupal.org/project/drupal) has what you
need to get started with your website. It includes several modules (extensions
that add functionality) for common website features, such as managing content,
user accounts, image uploading, and search. Core comes with many options that
allow site-specific configuration. In addition to the core modules, there are
thousands of contributed modules (for functionality not included with Drupal
core) available for download.

More about configuration:
 * Install, upgrade, and maintain Drupal:
   See INSTALL.txt and UPGRADE.txt in the "core" directory.
 * Learn about how to use Drupal to create your site:
   https://www.drupal.org/documentation
 * Follow best practices:
   https://www.drupal.org/best-practices
 * Download contributed modules to /modules to extend Drupal's functionality:
   https://www.drupal.org/project/modules
 * See also: "Developing for Drupal" for writing your own modules, below.


INSTALLATION PROFILES
---------------------

Installation profiles define additional steps (such as enabling modules,
defining content types, etc.) that run after the base installation provided
by core when Drupal is first installed. There are two basic installation
profiles provided with Drupal core.

Installation profiles from the Drupal community modify the installation process
to provide a website for a specific use case, such as a CMS for media
publishers, a web-based project tracking tool, or a full-fledged CRM for
non-profit organizations raising money and accepting donations. They can be
distributed as bare installation profiles or as "distributions". Distributions
include Drupal core, the installation profile, and all other required
extensions, such as contributed and custom modules, themes, and third-party
libraries. Bare installation profiles require you to download Drupal Core and
the required extensions separately; place the downloaded profile in the
/profiles directory before you start the installation process.

More about installation profiles and distributions:
 * Read about the difference between installation profiles and distributions:
   https://www.drupal.org/node/1089736
 * Download contributed installation profiles and distributions:
   https://www.drupal.org/project/distributions
 * Develop your own installation profile or distribution:
   https://www.drupal.org/developing/distributions


APPEARANCE
----------

In Drupal, the appearance of your site is set by the theme (themes are
extensions that set fonts, colors, and layout). Drupal core comes with several
themes. More themes are available for download, and you can also create your own
custom theme.

More about themes:
 * Download contributed themes to /themes to modify Drupal's appearance:
   https://www.drupal.org/project/themes
 * Develop your own theme:
   https://www.drupal.org/documentation/theme

DEVELOPING FOR DRUPAL
---------------------

Drupal contains an extensive API that allows you to add to and modify the
functionality of your site. The API consists of "hooks", which allow modules to
react to system events and customize Drupal's behavior, and functions that
standardize common operations such as database queries and form generation. The
flexible hook architecture means that you should never need to directly modify
the files that come with Drupal core to achieve the functionality you want;
instead, functionality modifications take the form of modules.

When you need new functionality for your Drupal site, search for existing
contributed modules. If you find a module that matches except for a bug or an
additional needed feature, change the module and contribute your improvements
back to the project in the form of a "patch". Create new custom modules only
when nothing existing comes close to what you need.

More about developing:
 * Search for existing contributed modules:
   https://www.drupal.org/project/modules
 * Contribute a patch:
   https://www.drupal.org/patch/submit
 * Develop your own module:
   https://www.drupal.org/developing/modules
 * Follow programming best practices:
   https://www.drupal.org/developing/best-practices
 * Refer to the API documentation:
   https://api.drupal.org/api/drupal/8
 * Learn from documented Drupal API examples:
   https://www.drupal.org/project/examples

MORE INFORMATION
----------------

 * See the Drupal.org online documentation:
   https://www.drupal.org/documentation

 * For a list of security announcements, see the "Security advisories" page at
   https://www.drupal.org/security (available as an RSS feed). This page also
   describes how to subscribe to these announcements via email.

 * For information about the Drupal security process, or to find out how to
   report a potential security issue to the Drupal security team, see the
   "Security team" page at https://www.drupal.org/security-team

 * For information about the wide range of available support options, visit
   https://www.drupal.org and click on Community and Support in the top or
   bottom navigation.