Prosilver templates phpbb3

Find out how to get involved in phpBB development. Google Summer of Code is an annual program in which Google awards stipends to students participating in coding projects for free and open source software projects. Discuss and view Extensions that are available for download. Discuss and view Styles that are available for download. Discussions on all things phpBB: features, future, etc.

On this page, you will find some basic as well as more advanced instructions which can help you in creating your own style for phpBB 3.

The focus will be on creating a new style, based on an existing style. Besides the fact that this is the most likely scenario for most style authors, it also creates a better understanding of the template-engine and style-system as a whole in more diverse situations.

We strongly advise you to follow the same structure, as this will minimize the chances of "file not found" problems. Since creating a completely new style is a massive undertaking and requires a lot of skill, in which case you won't need this guide anyway , we need to choose an existing style to use as a "base".

As you will probably spend many hours creating your new style, choosing the right "base" style is essential. You want a solid foundation for your style. The easiest choice is obviously to use the default phpBB 3. Choosing a style like prosilver which has all the current template events in place will also ensure that extensions will function properly. Read more on this subject in the template events section. The first thing that needs to be done is creating the file structure for your new style.

See the file structure section to see what a basic skeleton looks like. When you have created all the required directories template, theme, images and the style.

The most important file of any style as far as installation goes is the style. It provides information to your phpBB board about how to install and process the style. It generally looks like this:. Most of this is pretty self explanatory. The most important values for our purposes are the name and parent fields, which indicate template inheritance.

Let's say that we want to create a style based on prosilver. Our style. Instead of using prosilver as a "base" parent , we could also use another popular style which in turn inherits from prosilver. The code of any website needs certain elements for it to work properly. Besides these elements, phpBB 3.

If you are using a valid 3. The phpBB 3. So if you don't include this variable in your template, many extensions will break since their front-end styling relies on these files. Since version 3. Besides the fact that jQuery can be very handy for style authors, many extensions will utilize it too and depend on it being active. Therefore you should always include the instructions that load jQuery into your template. For more information on how to use the various template tags and conditionals, we advise you to take a look at our Development Wiki.

At this time, there are no dedicated entries yet specifically for 3. With the introduction of the extension system in phpBB 3. This greatly simplifies the installation, updating, and removal processes of functionality for styles. Many extensions will use these template events in order to add functionality to phpBB.

If you want your style to become popular, you should definitely try to include as much of the "default" template events as possible. Since prosilver is still the default style for phpBB 3. Including these events in roughly the same location as prosilver will ensure that future extensions will work with your style. Template inheritance is arguably the most useful thing about phpBB's template-engine for style authors.

If you base a new style on an existing one, but you only want to change a few templates, you don't have to copy them all. This would create a lot of identical copies of files on your server, and things would get cluttered pretty soon. It would also become very tedious to merge all the changes to the templates, if the "parent" style were to receive an update.

Enter template inheritance , requiring nothing more than a single line in your style. By specifying a "parent" in your style. The nice thing about this is that the process is completely transparent after template compilation and comes at practically no extra costs during runtime.

This process can go multiple levels deep. So you can base your own child style on a child of a child of a child of a parent, like the branches of a tree hence the " styles tree ".

Many styles start off by modifying existing styles such as prosilver , because creating a completely new style from scratch is an extremely time consuming undertaking.

The following example will show how easy and useful it is. Well the first thing to remember is that you only want to change these 2 parts now. You will likely want to change more and more parts as time progresses. So the best course of action would be to create a "child" style of style X we'll called it style Y.

Is that all? Not quite. You will notice that no theme assets CSS and images have been loaded. We will address this issue in the asset inheritance section. The biggest obstacle for most style authors is the fact that the inheritance tree only works for templates, not CSS. So how do we use template inheritance, but also "inherit" the theme assets of the "parent"?

There are multiple ways of doing this, and it will depend on whether or not you plan to make really significant changes to the CSS files. We'll try to explain the different ways of "inheriting" theme assets from other styles, and their pros and cons. While this is the easiest method, it is strongly discouraged to use it, especially if you plan on releasing your style publicly, for the following reasons:.

If you only want to make changes to a few of the parent's CSS files, you might not want to duplicate all the assets, since that would just clutter your new style. It is possible to only copy a few assets and make changes to them, without having identical copies scattered around the server. In your new style's stylesheet.

Variables output to the user are enclosed in curly braces e. While language and template variables are automatically set, you will need to manually set other kinds of data you want to use in your template file. Those have been expanded vastly since phpBB2, so that they should be worth a look for everybody.

While block variables were phpBB2's only way to have conditionals and loops in templates, they are now back as loops exclusively. MODs should come with prosilver and subsilver versions of the templates final verdict pending. Try to follow the design of the original templates, for instance use tables in prosilver only for tabular data like the memberlist and not to design forms. Using the phpBB3. Like the other Ubuntu-related style from which this style derived, two panels replace prosilver's navbars.

Available in several languages using Latin alphabet. The st…. Naruto Shippuuden Fixed width for fans of Naruto. Rock'n Roll Simple style for forums that music content in general.

Style colors: …. Hexagon Based on prosilver style and inspired by material design. Like my work? Consider donating. Every donation is appreciated. New version of phpbb arrived? The style isn't validated for it yet?