mirror of
https://github.com/nextcloud/documentation.git
synced 2026-01-03 02:09:45 +07:00
core typos
This commit is contained in:
@@ -88,8 +88,8 @@ Statuscodes
|
||||
~~~~~~~~~~~
|
||||
The statuscode can be any of the following numbers:
|
||||
|
||||
* **100** - successfull
|
||||
* **100** - successful
|
||||
* **996** - server error
|
||||
* **997** - not authorized
|
||||
* **998** - not found
|
||||
* **999** - unknown error
|
||||
* **999** - unknown error
|
||||
|
||||
@@ -6,19 +6,19 @@ Themes can relate to the following topics of owncloud:
|
||||
|
||||
* Theming the web-frontend
|
||||
* Theming the owncloud Desktop client
|
||||
This documentation contains only the Web-frontend adaptions so far.
|
||||
This documentation contains only the Web-frontend adaptations so far.
|
||||
|
||||
Getting started
|
||||
---------------
|
||||
A good idea getting starting with a dynamically created website is to inspect it with **webdeveloper tools**, that are found in almost any browser. They show the generated HTML and the CSS Code, that the client/browser is recieving:
|
||||
With this facts you can easyly determine, where the following object-related attributes for the phenomenons are settled:
|
||||
A good idea getting starting with a dynamically created website is to inspect it with **web developer tools**, that are found in almost any browser. They show the generated HTML and the CSS Code, that the client/browser is receiving:
|
||||
With this facts you can easily determine, where the following object-related attributes for the phenomenons are settled:
|
||||
|
||||
* place
|
||||
* colour
|
||||
* links
|
||||
* graphics
|
||||
|
||||
In owncloud standard theme everything is held very simple. This allows you quick adpating. In an unchanged ownCloud version css files and the standard pictures reside in /owncloud/themes/default folder.
|
||||
In owncloud standard theme everything is held very simple. This allows you quick adapting. In an unchanged ownCloud version CSS files and the standard pictures reside in /owncloud/themes/default folder.
|
||||
The next thing you should do, before starting any changes is:
|
||||
Make a backup of your current theme(s) e.g.:
|
||||
|
||||
@@ -43,7 +43,7 @@ Structure
|
||||
|
||||
The folder structure of a theme is exactly the same as the main ownCloud
|
||||
structure. You can override js files, images and templates with own versions.
|
||||
css files are loaded additionally to the default files so you can override css
|
||||
CSS files are loaded additionally to the default files so you can override CSS
|
||||
properties.
|
||||
|
||||
|
||||
@@ -55,14 +55,14 @@ A new logo which you may want to insert can be added as follows:
|
||||
Figure out the path of the old logo
|
||||
-----------------------------------
|
||||
|
||||
Replace the old pictue, which postition you found out as described under 1.3. by adding an extension in case you want to re-use it later.
|
||||
Replace the old picture, which position you found out as described under 1.3. by adding an extension in case you want to re-use it later.
|
||||
|
||||
Creating an own logo
|
||||
--------------------
|
||||
|
||||
If you want to do a quick exchange like (1) it's important to know the size of the picture before you start creating an own logo:
|
||||
|
||||
* Go to the place in the filesystem, that has been shown by the webdeveloper tool/s
|
||||
* Go to the place in the filesystem, that has been shown by the web developer tool/s
|
||||
* You can look up sizing in most cases via the file properties inside your file-manager
|
||||
* Create an own picture/logo with the same size then
|
||||
|
||||
@@ -73,15 +73,15 @@ The (main) pictures, that can be found inside ownCloud standard theming are the
|
||||
|
||||
Inserting your new logo
|
||||
-----------------------
|
||||
Inserting a new logo into an existing theme is as simple as replacing the old logo with the new (genreated) one.
|
||||
Inserting a new logo into an existing theme is as simple as replacing the old logo with the new (generated) one.
|
||||
You can use: scalable vector graphics (.svg) or common graphics formats for the internet such as portable network graphics (.png) or .jepg
|
||||
Just insert the new created picture by using the unchanged name of the old picture.
|
||||
|
||||
changing the default colours
|
||||
----------------------------
|
||||
|
||||
With a web-developer tool like Mozilla-Inspector, you also get easyly displayed the color of the background you klicked on.
|
||||
On the top of the login page you can see a case- destinguished setting for different browsers:
|
||||
With a web-developer tool like Mozilla-Inspector, you also get easily displayed the color of the background you clicked on.
|
||||
On the top of the login page you can see a case- distinguished setting for different browsers:
|
||||
|
||||
.. code-block::
|
||||
|
||||
@@ -96,17 +96,17 @@ On the top of the login page you can see a case- destinguished setting for diffe
|
||||
background: linear-gradient(top, #33537a 0%,#1d2d42 100%); /* W3C */
|
||||
|
||||
|
||||
The different backround-assignements indicate the headers for a lot of different browser types. What you most likely want to do is change the #35537a (lighter blue) and #ld2d42 (dark blue) color to the colours of our choice. In some older and other browsers, there is just one color, but in the rest showing gradients is possible.
|
||||
The different background-assignments indicate the headers for a lot of different browser types. What you most likely want to do is change the #35537a (lighter blue) and #ld2d42 (dark blue) color to the colours of our choice. In some older and other browsers, there is just one color, but in the rest showing gradients is possible.
|
||||
The login page background is a horizontal gradient. The first hex number, #35537a, is the top color of the gradient at the login screen. The second hex number, #ld2d42 is the bottom color of the gradient at the login screen.
|
||||
The gradient in top of the normal view after login is also defined by these css-settings, so that they take effect in logged in situation as well.
|
||||
The gradient in top of the normal view after login is also defined by these CSS-settings, so that they take effect in logged in situation as well.
|
||||
Change these colors to the hex color of your choice:
|
||||
As usual:
|
||||
|
||||
* the first two figures give the intensity of the red channel,
|
||||
* the second two give the green intensity and the
|
||||
* tird pair gives the blue value.
|
||||
* third pair gives the blue value.
|
||||
|
||||
Save your css-file and refresh to see the new login screen.
|
||||
Save your CSS-file and refresh to see the new login screen.
|
||||
The other major color scheme is the blue header bar on the main navigation page once you log in to ownCloud.
|
||||
This color we will change with the above as well.
|
||||
Save the file and refresh the browser for the changes to take effect.
|
||||
@@ -117,7 +117,7 @@ Testing the new theme out
|
||||
There are different options for doing so:
|
||||
|
||||
* If you're using a tool like the Inspector tools inside Mozilla, you can test out the CSS-Styles immediately inside the css-attributes, while looking at them.
|
||||
* If you have a developing/testing server as desciribed in 1. you can test out the effects in a real environment permanently.
|
||||
* If you have a developing/testing server as described in 1. you can test out the effects in a real environment permanently.
|
||||
|
||||
|
||||
.. _GitHub themes repository: https://github.com/owncloud/themes
|
||||
@@ -127,7 +127,7 @@ Notes for Updates
|
||||
=================
|
||||
|
||||
In case of theming it is recommended to the user,
|
||||
not to perform these adaptions inside the folder /themes/default.
|
||||
not to perform these adaptations inside the folder /themes/default.
|
||||
|
||||
Please perform the following steps, to avoid conflicts with other upcoming updates:
|
||||
|
||||
|
||||
@@ -31,7 +31,7 @@ Then you can simply run the created test with phpunit.
|
||||
|
||||
.. note:: If you use owncloud functions in your class under test (i.e: OC::getUser()) you'll need to bootstrap owncloud or use dependency injection.
|
||||
|
||||
.. note:: You'll most likely run your tests under a different user than the webserver. This might cause problems with your PHP settings (i.e: open_basedir) and requires you to adjust your configuration.
|
||||
.. note:: You'll most likely run your tests under a different user than the web server. This might cause problems with your PHP settings (i.e: open_basedir) and requires you to adjust your configuration.
|
||||
|
||||
An example for a simple test would be:
|
||||
|
||||
@@ -78,7 +78,7 @@ To do this, you'll need to provide the ``--bootstrap`` argument when running PHP
|
||||
|
||||
phpunit --bootstrap tests/bootstrap.php apps/myapp/tests/testsuite.php
|
||||
|
||||
If you run the test under a different user than your webserver, you'll have to
|
||||
If you run the test under a different user than your web server, you'll have to
|
||||
adjust your php.ini and file rights.
|
||||
|
||||
:file:`/etc/php/php.ini`::
|
||||
|
||||
Reference in New Issue
Block a user