High level tasks for D8 alpha port

[soniktrooth]

As discussed with @andrewmallis and I, @labboy0276 please outline some high level tasks that will need to happen for our MVP alpha.

e.g.

• abstract class
• porting theme functions to twig tpls
  etc.

[labboy0276]

I am staring at all this today and writing on a game plan and then will import it here

[labboy0276]

OK, so I went through each file and gave a quick synopsis of what we should do. The general flow is we create a broad Abstract class that any framework can inherit and do their magic. So initial efforts will be heavy, but once we got it, implementing most of this below will be easy peasy and beautiful:

CSS

• Panopoly.css (remove)
• Tweaks.css (edit and remove unneeded, keep file)

Images

• Pretty sure we can remove this

Includes

• Config.inc
• If we are keeping the subtheme generator then it needs to be
  moved to a D8 form interface then the actual subtheme generation
  should become its own abstract class so we can extend it to all
  different frameworks as need be, good amount work here in
  general
• Core.inc
• These will need to be converted to preprocesses and TWIG files,
  all the theme_ functions, status report ones can wait if
  need be. Maybe we can convert this to some sort of interface or
  abstract class so that we only have to convert this once, use
  preprocesses to call the class and do what needs to be done, etc
• Fapi.inc
• Same as core.inc
• Fields.inc
• Same as core.inc
• Libraries.inc
• See notes in config.inc, also if we proceed, look how the
  Bootstrap theme converted hook_libraries_info() into an
  anootation plugin, we would have to do the same
• Menu.inc
• Same as core.inc
• Panels.inc
• A lot of this needs to be rewritten for D8, do we need all this,
  need to investigate this a lot more.
• Utils.inc
• A lot of this file depends on what we are doing with config.inc.
  The Grid functions probably need to be converted into the
  Kalatheme Abstract Class
• Views.inc
• All these functions are bootstrap dependent. Need to Create a
  class to handle the general tweaks and have KalathemeBootstrap
  Class extend them as needed.

JS

• Kalatheme-modal.js (edit and remove unneeded, kep file if need be)

Styles

• Kalacustomize (remove / check if we can still use this in d8 before
  we do)

Templates

• Core
• Convert to twig, remove unneeded ones, check core
• Panels
• Convert to twig, remove unneeded ones, check core
• Panopoly
• Remove
• Views
• Convert to twig, remove unneeded ones, check core

Views

• Plugins
• Do we still need this? If so convert to a D8 plugin

Kalatheme.authorize.inc

• Are we still keeping the subtheme generator, if so, then this will
  have to become a class of its own

Kalatheme.drush.inc

• Are we still keeping the drush commands, if so convert to D8
  standards, make class of its own

Kalatheme.info

• Convert to d8 standard

Kalatheme.updater.inc

• What is this and do we still need it, if so convert to d8 standard

Template.php

• Most of this will get moved into KalathemeBootstrap Class,
  preprocesses can be left initially or rewritten for D8.

Theme-settings.php

• We need to go through this and see what settings we are keeping
  based on what is going on with the includes folder and convert this
  file to D8 form standard.

[soniktrooth]

@labboy0276 this is great—thanks for this. I'm going to start creating separate issues out of this so we can move things along.