Examples:

• Margins should be different when one section ends and another begins from
  when a sub section is starting.
• Margins shnould collapse so that there is a different margin before and after
  headings.

This is a fantastic project but the output isn't mobile friendly. Can it please can updated to respond to different mobile screen sizes?

Hi,

Thank you for the awesome css which I have used always. Here is an issue that I have found.

Here is the CSS included, but after export the Org file to HTML, the SRC (for example XML) paragraph is not rendered.

(setq org-html-head-extra "<link rel="stylesheet" href="http://thomasf.github.io/solarized-css/solarized-dark.min.css\" type="text/css" />")

Could you help on this?

Env: Mac OS 10.10.5 + Emacs 25.1 + Org 8.3.1

Thanks,
James.

Hi there,

I found your project on Google, and I thought you might be interested in this:

https://github.com/alphapapa/solarized-everything-css

It also uses Stylus, so it should be familiar to you. I'd be happy to accept PRs if you feel like adding to it. :)

Hi

I tried to apply this css style on a page in the researchcatalogue (a hobby art project of mine) and I get this weird box on top that follows when scrolling. Do you know what that might be and what I should remove in the css to not have it there?

https://www.researchcatalogue.net/view/392580/561469

Hello,

I could not find a licence for this project and hence I am unsure about whether this code can be used in other projects. It would be great if this could be clarified.

Thanks!

There might be very usable templates for this.. look it up!

Should also make it easier to do builds that can be inlined into org html exports.

Horisontal scroll overflow for tables could solve this:

Possibly more torublesome using the dark version of the theme.

Currently the produced HTML file when using the hosted version fails on Firefox, as the stylesheet is loaded over HTTP and blocked due to mixed content. Even when changing to using the HTTPS url to load the stylesheet, several fonts in the hosted stylesheet are still loaded over HTTP, causing them to be blocked.

Thanks for providing this example.

The test/html.html file has a broken <img> element. The images/css_gods_language.png file isn't in the repository.

Hi

In the file solarized-css/test/org-hacks.org you have published has some neat functions and tips.
I noticed that https://thomasf.github.io/solarized-css/test/org-hacks.html#sec-1-7 has some functions to preserves the logic of level groupings and tags when archiving.

The line (with-current-buffer (find-file-noselect (org-extract-archive-file)) now has an error helm-M-x: Symbol’s function definition is void: org-extract-archive-file.
org-extract-archive-file and org-get-local-archive-location have been removed from org-archive.el. org-archive--compute-location has to be used instead.

Here is an example of how someone else applied the changes. daviderestivo/galactic-emacs@cb439c9

I am a org mode novice and I found the tips in you document very informative.

• More of the tags and todo states that come from inside org-mode.
• Tags like issue / bug / enhancement / ....

The issue only happens when I have evil-org on.
I'm using spacemacs with the org layer.

The issue is:
when I export to html and open it in my web browser,
I can see everything before the first headline, but the rest is hidden.
None of the keybindings work n/p m/X F/f etc (I tried all to make sure),
and the HELP "toggle" doesn't appear, since the headlines don't show up.

The issue resolves itself when I remove the following line:

#+INFOJS_OPT: view:t toc:t ltoc:t mouse:underline buttons:0 path:http://thomasf.github.io/solarized-css/org-info.min.js

In other words, the CSS works just fine regardless of whether I'm in evil-org-mode or not.

(I just started with emacs, so I'm sorry if I'm wrong about something. Also really enjoying the project. Thank you everybody)

Because its more common

Some kind of image viewer should be added. This was the full size images can be accessed quickly even if they are scaled down in the normal document flow.

• Make sure headings under level three are easier to recognize.
• Use even less colors for headings (if possible)
• Try using emphasized foreground colors and/or face variations instead.