kathyqian / crisp Goto Github PK

a little too indented on mobile devices

likely will be an optional feature

not a huge issue but worth a few extra lines of code

add related posts block under social share buttons

Although the lack of styling for the .kg-width-wide, .kg-width-full, .kg-gallery-container, .kg-gallery-row, and .kg-gallery-image CSS classes does not really affect the display of the minimalist style of this theme, it does throw an error upon theme activation.

currently not pulling most optimal description from posts

What's the easiet way to test changes made to the theme locally without having to update your actual ghost blog?

doesn't scale to fill up the row, svg icons don't show up

Use #FF3D1B for the color code of the Reddit Share button.

probably will not fix for IE6, continue to investigate issues in IE7

I am using Ghost 1.19.0.

Hi there,

I'm using ghost 1.1.2 with crisp and turns out that on my homepage there's only listed 5 items, can you please specify what is the setting that needs to be changed to list more than 5 items per page?

Thanks,
Javi.

I was wondering if Crisp will get any native AMP support. (ref. https://themes.ghost.org/docs/amp)

Hi!

Thank you for the update to 0.5.0 and the Ghost 0.5.x support :) I'm happy to see that this project is still up!

But, after I cloned and chose the new theme, I noticed that "code" tag (adada and the 4 spaces) have the font bigger than before, and I couldn't figure out how to put a lower font size.

Also (and I hope this is a Highlight.js problem) if I change the theme, only the 4 spaces indented code change its theme but not the asas stuff.

Thank you for your help!

currently spills over onto 2 lines, easily fixed by changing "older posts" to "older" and "newer posts" to "newer"

compress header more on phones and tablets (getting a little too thick)

issue on ipads, not blocking, probably not worth effort to fix

When using **bold markup** in a Ghost post, this correctly appears in published posts as <strong>bold markup</strong>. However, the Crisp CSS does not actually render the text as bold.

Adding strong { font-weight: bold; } within the CSS would resolve this.

I'm noticing a super strange bug wherein a couple of the RRSSB icons look really funky if and only if there is a single quote ' in the article title. Can anybody replicate this?

On larger screens when browsing through a blog post, the font size is quite large and since the text spans all the way across the larger screen - it's really hard to read the post with a good flow.

Example:

http://i.imgur.com/PlCVmrg.png

This is probably opinionated, but perhaps limiting the width of the blog post content would be a solution?

太酷了 --form BeiJing

Hello!

I want to ask if it's possible to add the "@username" in Twitter's share button. I don't know how to do it, anyone? Thanks in advance!

http://puu.sh/8z9ho/15542269f6.png

I'm on Ghost 0.4.2. Any help is appreciated. This theme looks lovely.

Hi Kathy,

In default.hbs the Google fonts are referenced via http explicitly:

[....]
        <link href='http://fonts.googleapis.com/css?family=Open+Sans:300italic,700italic,300,700' rel='stylesheet' type='text/css'>
            <link href='http://fonts.googleapis.com/css?family=Bree+Serif' rel='stylesheet' type='text/css'>
            <link href="//netdna.bootstrapcdn.com/font-awesome/4.0.3/css/font-awesome.css" rel="stylesheet">
[....]

As a result, if you browse to the blog via HTTPS, some browsers will refuse to load the fonts. Chrome shows errors like this as an example:

[blocked] The page at 'https://<blog>' was loaded over HTTPS, but ran insecure content from 'http://fonts.googleapis.com/css?family=Open+Sans:300italic,700italic,300,700': this content should also be loaded over HTTPS.
[blocked] The page at 'https://<blog>' was loaded over HTTPS, but ran insecure content from 'http://fonts.googleapis.com/css?family=Bree+Serif': this content should also be loaded over HTTPS.

A fix would be to mirror the font awesome line and use // <link href='//fonts.google[...] instead. This way the browser can use either http or https depending on how the page was loaded.

Thank you! I love your theme :)

add follow buttons under description (above navigation), add well for share buttons under posts (before comments), and clean up meta info for sharing

I noticed that your site, http://kathyqian.com/, has a nice circular profile image. Is this not part of the crisp theme? Does it need to be added manually?

Thanks!

Ghost will at some point require that all themes are bundled with a package.json file. The most basic one just has a name and a version. How is this theme versioned?

http://dev.ghost.org/new-for-themes-0-4-2/

Is there a particular reason to have the theme files in a separate crisp subdirectory?

I really love Crisp and am interested in using it as a submodule within an existing repository. I could get things to work as a submodule if the files were all in the root of the repo but as they're not, I can't see how I can do it at the moment (if I checked out this project I'd end up with a directory structure like content/themes/crisp/crisp/ instead of content/themes/crisp/).

The Casper theme in structured with the README in the root of the 'theme proper' as it were. Could Crisp do the same?

Ghost 0.4.2 introduced tag pages and it would be awesome to have a clean way to use them in the theme.

add google prettify script to process pre blocks and add line numbers and highlighting

Thank you for nice theme but when I try with Prism Syntax Highlighter in my ghost blog I got a css error and my codes looks bad.

Most ghost themes I've encountered have the theme files as the root of the repo. This makes it easier to clone into your themes folder.

You could externally host the screenshots and have the contents of /crisp on the root. Obviously this would require a repo name change, not sure if that's something you'd consider.

Nice theme!

excuse me , i like this theme very much ,thank you. but i hava a question , that is how can i add tags when i create a new post ?

With the release of Ghost 0.5 and its changes at theme's api, I'm asking myself if this theme will be updated to support them? =)

issues with fixed positioning and padding causing content to overlap