General Community > Off-Topic
Thoughts about contributing & WB releases
Yetiie:
Very good idea.
Just my two cents: to create a goal for whole websitbaker project will be alittle bit complicated ... because the development team has their own planning and as I learned over the last years ...
But the way to improve WB by realising concrete and limited single projects in little teams could be very effective.
######## To be concrete:
My most done suggestion at the moment is a WB-Bootstrap project.
The theme grows up here on WB too.
Means: Making the elements of bootstrap easy accessable to WB.
Done as best-practise-demonstration and/or as starter-template.
Other ideas are:
>>> Standardizse the css for modules ... this has to to with the backend theme ... the idea is a modular css with defined elements which should be used for modules. Standardizing elements means: defne html- und css-structure (classes). On this way it would be possible to have en even look for the modules and to be able to change the look to another design by styling the same elements only with css.
>>> a mulitchanger-module ... not as easy, but multichangers become more and more popular and replaces the picture changers and it would kick the possibilities of WB forward.
-----------
... just as some ideas!
Yetiie:
And one other information:
The last two or three days in a thread one of the development team mentioned, for a wb project he would open a place on the resporitory (as I hd understood that) ... could be a good place to collect and coordinate ... :-)
pcwacht:
+1 for the standardization of modules
This will give faster development - simular look etc.
Hmm, not just +1, I'll give it a +100 :)
John
Stefek:
--- Quote from: Yetiie on April 20, 2015, 12:32:19 AM ---
>>> Standardizse the css for modules ... this has to to with the backend theme ... the idea is a modular css with defined elements which should be used for modules. Standardizing elements means: defne html- und css-structure (classes). On this way it would be possible to have en even look for the modules and to be able to change the look to another design by styling the same elements only with css.
--- End quote ---
Yetiie,
this is rather easy. But it begins with the backend-theme itself.
Once you have the backend-modules (like settings, page-settings etc.) and some of the packaged modules (like news, form-module etc.) reworked you end up with the necessary HTML structure for way over 80% of all modules. This HTML structure and its CSS definitions then can be easily applied in the modules developed by the community.
So yes. Doable. And long overdue.
--- Quote from: Yetiie on April 20, 2015, 12:32:19 AM --->>> a mulitchanger-module ...
--- End quote ---
What do you mean by that?
Stefek
Yetiie:
@pcwacht
Thx for support. I think we are in the same direction ... :-)
And for wb it would be indeed a very big chance to doing it.
@Stefek
Once more same direction :-)
Indeed. Exactly that's the way to do it!
But to be honest: Based on the experience with the new backend theme this IMHO only really makes sense with(!) little support of the development team :-( The problem to style this special page on the backend is, that the code is hard coded by php (very old code from the beginning of the cms, someone reported from about the 80th). And the modules in the html code are not separated which makes it very hard and could not be a very special work only (i.e. spaces or placements in the inner of the module area can not be set).
>>> But: The solution could be very easy:
A workarround without writing module code output completely new (which indeed is not possible for the team at the moment) would be to ad the output of an simple div-container arround any module-output with some special classes (i.e. class: module-area, maybe(!) if not to much work class with module-name).
>>> Chance:
This could be done for 2.8.4 with very little engagment as it is a very small and neutral changing of the code output and without risk as neutral divs does not affect working code.
>>> Situation:
The development team especially the responsible member for the core in the german forum made VERY CLEAR that there will not be done any changes on the output code (as writing backend templates in later future wb versions will become very easy so bakcend development is not necessary to this up to now).
>>> What could be done:
Nothing is fix and maybe someone is able to change his mind. Even if there are a lot of supporters for this idea - maybe the development team changes their mind.
Possible realisation
In this case I would be on board: as the first step I would do the basic and adapt the new backend theme to 2.8.4 so it could be used up from the mostly beginning (I don't know the actual timing ... three month, one year :? actual they are working on next SP for .3 I believe). Then we could do a team to define standard elements and add it step for step to the template. Someone does the documentation ...
... and step for step a little team could improve wb a lot without need of wb development team.
Ok, - to start a little coming up of the development team would be needed. That could be the most difficult thing I am affraid.
So: the question is: Are here ...
... some more who would support the idea?
... some who would like maybe to engage themself?
(Especially help on documentation would be very helpful. Maybe the new wiki could be a good/right place for it.)
--------
NOTE: Just to be sure. Don't be anxious. As the layout works up to now the modules do not have to be change if the maintainers don't like it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version