holzweg / hwboot Goto Github PK

IMHO, it should be better to have that kind of stuff in a License.md file than in the files themselves

The recent ezpublish upgrade brings a new theme (ezdemo) with bootstrap. I'm not yet fond of the way it is implemented there, and further, a lot of modules (like gallery etc...) are implemented based on the YUI- library, which i see no reason for.

I'll try to gather some information on ez's roadmap and their ideas of using bootstrap in the future, any comments on that would be helpful.

The first subitems (in case of dropdown menu integration with double_top as the top menu) are under the eZ toolbar (on z axis) so they are not visible & clickable

Bootstrap development follow-up

Solution 1

• configure bootstrap as a git submodule (in lib/bootstrap for instance), set on a specific commit. Might be simple in terms of upgrades but it might introduce some bugs in case of buggy releases... Depends if we want to always be on the bleeding edge or not
• write a script to create some symlinks to maintain the relation between the eZ Publish extension structure and the bootstrap clone => might be a problem for Windows users but do we care about them ? :p

Solution 2

• write a script that checkouts a specific branch/tag of bootstrap and then copy it in the good folders

Solution 3

• do it manually (which is not a bad solution since it takes less than 1 hour ...)

Common needs

• a script that
  • updates variables.less and other bootstrap-related files
  • adds hwboot specific files

Questions

• should it be shell based ? php based ?
• if php based, should we think of something in the admin interface to make it updatable by anybody ?
• ....

For instance, canonical_link.tpl, is overriding the default one (in ezwebin) but it's exactly the same.
I'm not sure if there was a reason that made you add this template in your hwboot design, so I did not remove it myself.

There might be other templates in this case.

In order to make templates more readable, I think that you should remove the comments that are in the templates.
Although they might help you in your development, they are too much related to HW standards and might differ from an IDE template to another.
For copyright purpose, just use a single License file as suggested in #1.

... in a similar way to https://github.com/alafon/albootstrapdesign?

...need to be done!
See an example of how the forms could look like at My Profile->Edit Profile.