Generator pain points

[bartoszmajsak]

This issue is intended to collect pain points of the current build process / stack so that we can plan and improve it.

[bartoszmajsak]

Uncertain status of Lanyrd.

• It might be going away any time
• 500 was very frequently failing a build
• it's read-only most of the times https://twitter.com/DeveloperSteve/status/910951236186251264

[MatousJobanek]

From my side:

generation points:

• Fine tune website generation steps #377
• there is no way to look at the changes introduced in some PR - solutions:
  • take a screenshot and upload to the PR as a comment
  • deploy the whole generated pages to separated directory as it is done in ST
    • not sure if it is possible to do it because of permissions / tokens
• the developer's mapping and registering accounts is not flexible - any change (new developer, removed account) can break the build

design/content:

• the modules page is not very clear - the containers adapters part is very long
  • idea is to shrink all adapters related to one container into one line and have it expandable
  • the same can be applied to the whole groups (extensions, adapters, etc) - have it expandable
• Getting started guides are outdated

as for the Lanyrd - I've fixed the backup some time ago, and it is automatically used by the generation process if Lanyrd is not available: https://github.com/arquillian/arquillian.github.io/blob/develop/_scripts/prepare_build_prod_and_run.sh#L61-L68
But it can be improved by using the cache directories provided by Travis - to use the latest data retrieved from the previous build.