Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Version 6 discussion :) #24

Open
2 of 10 tasks
danmindru opened this issue Sep 8, 2016 · 0 comments
Open
2 of 10 tasks

Version 6 discussion :) #24

danmindru opened this issue Sep 8, 2016 · 0 comments
Labels
idea planning
Milestone
Version 6

Comments

@danmindru
Copy link
Owner

danmindru commented Sep 8, 2016 •
edited
Loading

Better way to handle <head> CSS

  • Because of inline styles, most properties in <head> have to be !important.
  • There's no access to pre-processor variables in <head>

Ideally, both would be fixed by processing the CSS in head (which stays as-is atm).
Looking into webpack or rollup might reveal some clever solutions.
(can do email-transform and make a special template, allow require(...) / import)

Preview & test

  • Simple gh-pages demo
  • Generate repo-style emails with preview & summary (as README)
  • use puppeteer to make previews

Build / performance

  • allow selective building (not all templates at once as it is now)
  • update code (get rid of fsx, convert to ES6)
  • update node (V6/7)

DX

  • browser sync for dist?
  • allow setting up & running using npx?
@danmindru danmindru added this to the Version 5 milestone Sep 8, 2016
@danmindru danmindru changed the title Better way to handle <head> CSS Version 5 discussion Sep 8, 2016
@danmindru danmindru changed the title Version 5 discussion Version 6 discussion :) Aug 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
idea planning
Projects
None yet
Milestone
Version 6
Development

No branches or pull requests
1 participant
@danmindru