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.

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

添加了新特性:支持设置各页面与每篇博文的封面 #1330

Open
wants to merge 31 commits into
base: master
Choose a base branch
from

Conversation

BearD01001
Copy link

@BearD01001 BearD01001 commented Dec 27, 2016

花了一两天时间改造了大大的Hexo主题,添加了页面封面与博文封面的设置,更大气一些哈
由于第一次使用Swig与Stylus,一边改造一边学习,可惜改动蛮多的,已与原版不兼容_(:зゝ∠)_
做了响应式处理,基本没什么大问题嘞~

页面封面设置

# /themes/nextd/_config.yml
# Page covers for follow pages, whom height is greater than 400px.
# Home cover is required, which is default cover for other pages.
cover:
  home: /images/home_bg.jpg
  tag: /images/tag_bg.jpg
  archive: /images/archive_bg.jpg
  category: /images/category_bg.jpg
  # post: 
  # about: 
  # pages: 

效果:
页面封面效果

博文封面设置(效果预览>从零开始:现在开始用ES6写代码 | 熊D博客):

---
title: 从零开始:现在开始用ES6写代码
date: 2016-09-30 18:46:45
categories: JavaScript
tags: [JS,JavaScript,ES6,ECMAScript6,ES2015,Babel,Gulp,NodeJs]
cover: banner-write-in-es6.jpg
---

博文封面效果借鉴了 Hux 大大博客的效果,谢谢~

效果:
博文封面效果

setSidebarMarginTop(getSidebarTop());
}
});
var sidebarTop = $('.header-inner').height() + 10;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'sidebarTop' is defined but never used.

@geekrainy
Copy link
Contributor

这已经没 next 主题的样子了。

@monster-wang-aws
Copy link

monster-wang-aws commented Dec 27, 2016

@geekrainy 有同感
Hux 的 blog 确实很酷炫,之前看到也觉得很好
不过这个定位和风格多少和 next 本身有出入?
以及 @HiDino9 这个是三种主题都支持吗?

@BearD01001
Copy link
Author

BearD01001 commented Dec 28, 2016

@geekrainy @monster-gump
确实改动蛮大的,不过感觉NexT整体960px的宽幅稍大一点的屏幕就会显得空白过多,所以才有了这个修改的初衷,算是融合了NexTHuxBlog吧。
主题是基于NexT.Pisces修改的哈

@ivan-nginx
Copy link
Collaborator

ivan-nginx commented Dec 29, 2016

Renamed lib on vendors? Again? Why?

And what with config file?

OMG, no.

@BearD01001
Copy link
Author

BearD01001 commented Dec 29, 2016

@ivan-nginx
Opps! Sorry! Maybe I made NexTD from NexT that is the elderly version.
Perhaps this feature can be modified in _config.yml, resetting vendors._internal ?

@ivan-nginx
Copy link
Collaborator

ivan-nginx commented Dec 29, 2016

@BearD01001 perhaps, before doing pull request need to merge latest master branch from original to your repo? And after that do all changes.

@BearD01001
Copy link
Author

@ivan-nginx thank you for your advice. I'm so sorry for my fault and I will correct it as soon as possible. really sorry.

@BearD01001
Copy link
Author

BearD01001 commented Dec 29, 2016

@ivan-nginx after checked my local repository I found that there are both vendors and lib directiry. Σ( ° △ °|||)︴
this change didn't casuse a conflict. it's so minor that not get my enough attention.
even so, thank you for your advice and I have improved it.

@iissnan
Copy link
Owner

iissnan commented Mar 2, 2017

Nice work. It seems there are tons of changes you have done for the new look. I would like to suggest you to implement them as a new scheme. 🍺

@ivan-nginx
Copy link
Collaborator

ivan-nginx commented Apr 20, 2017

@ivan-nginx ivan-nginx added this to the v5.2.0 milestone Apr 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants