This refers to the Global Backgrounds MIGX TV..

http://hub.ddgc-staging.qaraqter.modxcloud.com/status-grid

When adding a tiled overview in a full-width layout for example, the optimal output should be completely borderless. This will add to the visual "tightness" of the functionality.

Right now, there's still padding on the top and bottom of the section, and on the bottom of the overviews (due to the nested class).

Die is nog niet zoals bij CT. Vooral de padding aan de boven- en onderkant vallen direct op. Zichtbaar op http://ddgc-staging.qaraqter.modxcloud.com/proberen/aanvraag/

Ik kan in de editor 'Lead text' wel selecteren, maar de klasse wordt daarmee niet ingesteld. Headings werken wel. De formatting van deze stijl komt ook niet mee in MODX (waarschijnlijk omdat 'ie 'm niet pakt).

500kb for CSS is simply too much. Maybe something like UnCSS can help grind the code and remove unused styles. But also per project disabling of components should become routine.

Uh oh, could not load the input type headingimageinput

ContentBlocks bug, most probably.

http://docs.modx.pro/en/components/pdotools/snippets/pdoneighbors

At first, I thought it would be handy to maintain the Romanesco SUI theme in its own repo, separate from Soil. For better portability and to keep styling and structure apart a bit still (so the styling could be updated separately for example).

But after a few months in practice, it seems to be more bothersome than handy. It's a lot of extra work to keep pulling and committing edits to the theme for every project, and I'm having a hard time keeping track of which of the theme a project is using, and if the latests edits are pushed already, etc. etc. It's one repository too many.

So since we're going to pull directly from Soil as an upstream repository anyway, we might as well include the Semantic UI theme in this repo. Changes can be submitted back to the Soil repo via pull requests.

This also takes care the problem that styling issues are not always just related to the theme alone. Sometimes it also involves classnames or HTML structure for example, so better to have it all in 1 repo from now on.

Create tags for stable releases too, so people can choose to use these instead of the latest one.

De marges op http://ddgc-staging.qaraqter.modxcloud.com/hrm-software zijn nog niet ideaal.

This potentially breaks some components after a build, since a newer version might have been installed on gitify install, which would then be overwritten by files from an older version.

Possible solution is to work with package versions in the .gitify file. Only thing is: modmore packages (which cause the most problems in this case) don't support adding the version to the package name.

The specified directory is not a directory.: /var/www/romanesco-soil/uploads/img/background/

Die zouden volgens mij in een eigen map moeten komen, nietwaar?

Otherwise, the front-end pattern library won't work.

Ok, so the ID's for the MODX elements remain generic, so there won't be any problems when the package is being built. But the ID's for all the ContentBlocks elements required by PatternLab will have to be fixed. Looking at the properties column for CB resource, it seems it's only looking for CB ID's there: layouts and fields. So if we do the same thing as with the Collections (create a pool of reserved ID's), things should be OK..

And if we don't enter this threshold in the database of the development install (Nursery), maybe it will become easier to create and transfer new elements to the base install with the threshold (Soil). Hmm....

How can this be controlled with Gitify? Create a collection with ID = 20 as some kind of closer?

Wait for pl release first, currently at rc1..

Add enlargement as option (FancyBox), add responsive options maybe.. There's a whole lot that can be done here.

• Field option for fluid image
• Field option for bordered image
• Field option for overruling thumbnail size

See https://c0379.paas1.fra.modxcloud.com/contact/

Probably the ID's are no longer properly matched..

It needs to have the same padding as that of the padded segments inside, it seems..

See: http://hoehler-alsalmy.loc/projects/

Add enlargement as option (FancyBox), add responsive options maybe.. There's a whole lot that can be done here.

This seems to be caused by the fact that the HTML for the nested layouts is not directly inside the configuration of the content block anymore, but in a chunk instead..

So this code in the Template field doesn't work in some cases:

[[$cbLayoutSidebarContentNested?
    &main=`[[+main]]`
    &sidebar=`[[+sidebar]]`
    &sidebar_width=`[[+sidebar_width]]`
    &padding=`[[+padding]]`
    &alignment=`[[+alignment]]`
    &divider=`[[+divider]]`
]]

But placing the content of the cbLayoutSidebarContentNested chunk here directly solves any parsing issue you might encounter.

I triple checked the generated HTML in the content field, and the backticks all seem to be in the right place. But somewhere inside the above chunk call, it stumbles over the backticks anyway apparently..