core_upgrader: Create upgrade path from v10.1 to v11

1 vote

Vote

Raised 0% of 30 credits
(30 credits = 5 hours or $214.59)

We put out v10.1, but decided to never have it leave beta, due to limited development resources and a desire to focus on v11.

We can't screw over people who decided to go to the beta, so we have to have some kind of upgrade path for these users.
That may just be an upgrade script they can run.

Suggested by Chris Graham on 27th June 2019

catalogues: Copy fields from another catalogue

0 votes

Vote

Raised 0% of 12 credits
(12 credits = 2 hours or $86.59)

Add a feature to copy in fields from one catalogue, to another catalogue, or a new catalogue.

Suggested by Chris Graham on 25th June 2019

core: Rep-image and thumbnail refresh

1 vote

Vote

Raised 0% of 18 credits
(18 credits = 3 hours or $128.76)

Currently the default is for rep-images to be sized to thumbnail size when you upload them (resize_rep_image function).

This makes little sense for multiple reasons:
1) Rep-image size is not necessarily going to have anything to do with thumbnail size. For example, the image in the corner of a news art…

Suggested by Chris Graham on 17th June 2019

core: Support BinaryAST (on hold)

0 votes

Vote

Raised 0% of 600 credits
(600 credits = 100 hours or $4,291.85)

Firefox is experimenting with pre-parsed JavaScript, as an optimisation.

https://blog.cloudflare.com/binary-ast/

It's very early-days, but we could potentially ship a binary-AST compiler as a part of Composr.

Suggested by Chris Graham on 10th June 2019

core: Support CSS and JS source map linking/generation

0 votes

Vote

Raised 0% of 120 credits
(120 credits = 20 hours or $858.37)

See https://www.html5rocks.com/en/tutorials/developertools/sourcemaps/

Suggested by Chris Graham on 10th June 2019

core: Support web packaging

1 vote

Vote

Raised 0% of 6,000 credits
(6,000 credits = 1,000 hours or $43,297.16)

Implement automatic creation and signing of .sxg files, so edge CDN servers (e.g. hosted by Google) can preload pages to users.

https://developers.google.com/web/updates/2018/11/signed-exchanges

Suggested by Chris Graham on 10th June 2019

core: Ensure we are using web font loader with Google Fonts

0 votes

Vote

Raised 0% of 12 credits
(12 credits = 2 hours or $86.59)

We must not have any Google Fonts blocking the critical rendering path.

Google does provide a solution for this:
https://www.lockedownseo.com/load-google-fonts-asynchronously-for-page-speed/

Suggested by Chris Graham on 10th June 2019

core: Performance-centric image overhaul

1 vote

Vote

Raised 0% of 48 credits
(48 credits = 8 hours or $343.35)

We can do responsive images simply using something like width: 100% in CSS or width="100%" in HTML.

This makes things mobile-friendly, but it makes things less-friendly performance-wise as it requires a page reflow once the image metadata (width and height specifically) loads.

Ideally we would be abl…

Suggested by Chris Graham on 10th June 2019

core: Theme options specifying which CSS/JS files to merge into 'global'

0 votes

Vote

Raised 0% of 18 credits
(18 credits = 3 hours or $128.76)

If CSS/JS files are consistently used together, they can be merged.

Previously we tried to automatically detect what CSS/JS files were used on the home page. However, it was over-complex and unstable when caching is involved, making it very difficult to debug and making the code horrible.

A better ap…

Suggested by Chris Graham on 10th June 2019

core: Support Google Translate API v3

0 votes

Vote

Raised 0% of 48 credits
(48 credits = 8 hours or $343.35)

https://cloud.google.com/translate/docs/intro-to-v3

They offer a free tier (I don't believe they did so before).
They provide support for defining terms... so we could provide some kind of editable master-list of terms that should not be translated.

Suggested by Chris Graham on 8th June 2019