ubill.github.io

Date

Well, after 'StackEdit Revisited', now I got StackEdit to show a preview using the actual CSS of my site's theme - as opposed to the default themes of StackEdit, which do not directly reflect how things would look like when coming under the actual CSS of my Pelican site.

To do that, I followed StackEdit's own guide on 'creating a custom theme', and put in the LESS files that would be going to my Pelican site.

  • The first set of CSS generated would be for the StackEdit theme i.e. the preview panel.
  • The second set of CSS will be generated from the same LESS source files that StackEdit uses - but with different imports. The output from that will be used in my Pelican theme.

Note: So it's not actually me bringing my Pelican site's theme to StackEdit - rather, I do that only once right at the start, then later, I will modify the source LESS only on StackEdit - then use lessc to generate the CSS files which I will copy into my Pelican theme.

In other words,

Less sources -> use in StackEdit -> use lessc to generate CSS files -> copy CSS files to Pelican theme.

So there's only one source of truth, one place to edit and maintain.