NexT

Theme for Hexo

Posted on Disqus:

Happy April Fools' Day Guys \(^_^)/

💥 Breaking Changes

  • Now quicklink will load on demand by default.
  • Add quicklink: true in Front-matter for those pages or posts you want.
  • Home page and archive page can be controlled through home and archive option.
quicklink:
  enable: true
- per_page: true
+ home: true # enable or disable quicklink on home page
+ archive: true # enable or disable quicklink on archive page
# Add `quicklink: true` in Front-matter to enable quicklink on special page or post

Some options look more uniform in _config.yml (#643)

- #github_banner: https://github.com/yourname || Follow me on GitHub
+ github_banner:
+  enable: false
+  permalink: https://github.com/yourname
+  title: Follow me on GitHub

post_meta:
  updated_at:
-    enabled: true
+    enable: true

wechat_subscriber:
-  #enabled: true
+  enable: false

custom_logo:
-  enabled: false
+  enable: false

-cheers_enabled: true
+cheers: true

Usage of back2top button (#657)

sidebar:
-  # Back to top in sidebar.
-  b2t: false
-  # Scroll percent label in b2t button.
-  scrollpercent: false
+back2top:
+  enable: true
+  # Back to top in sidebar.
+  sidebar: false
+  # Scroll percent label in b2t button.
+  scrollpercent: false

🌟 New Features

  • Range of font size and color to tagcloud (#648)
  • New video and warn when use exturl or extlink (#652)
  • Mermaid (#649)
  • Likely share (#678)
  • Chatra and Tidio chats service (#681)
  • safari_rainbow and custom_scrollbar (#686)
  • DisqusJS comment system (#705)

⭐ Features

  • Load quicklink on demand (#637)
  • Force language options to Gitalk comment system (#653)
  • New pdf tag (#659)
  • Amount option to tagcloud (#662)
  • Fancybox for group-picture and post-gallery (#667)
  • English support for Valine comment system (#676)
  • Expand all level option of post TOC (#679)
  • Icon option to sidebar chat button (#688)
  • New text_align option (#682)
  • Dynamic unlimited reward additions and animation option (#695)

🛠 Improvements

  • Fix bootstrap filename (#640)
  • Change the spacing between sidebar elements (#638)
  • Rename loader script for prevent wrong boostrap detection in Wappalyzer (#641)
  • Update CDN url in _config.yml (#664)
  • Remove ua_parser excess library (#671)
  • Make a few documentational edits (#672)
  • Move stylesheets from .swig to .styl files (#680)
  • Remove unnecessary CSS prefix & Update normalize.css (#683)
  • Make site-state-item centered using flex (#700)
  • Refactor Mist & Muse menu bar using flex (#702)
  • Remove qihu_site_verification and move some options to SEO Settings (#706)
  • Make CSS cleaner using tablet-mobile() (#724)
  • Remove redundant styles (#728)
  • Make CSS simpler using macro (#738)
  • Improve canonical path for vision in Google (#748)
  • Merge note.styl and note-modern.styl (#750)
  • Reduce the use of !important for GitHub banner (#744)
  • From now release drafts will maked automatically (#765)
  • Improve console warning for non-supporting (#766)
  • Change comparison for Release Drafter Bot

🐞 Bug Fixes

  • Diff code hightlight problem (#665)
  • Lost tracking_id in google_analytics (#668)
  • For long mathjax equations with short viewport horizontal scrollbar will appear (#669)
  • Colored link for modern notes with exturl (#685)
  • reward button vertical align text (#693)
  • back2top button on mobile, sidebar item margin and sidebar exturl link color (#684)
  • Right margin bug on mobile devices (#709)
  • Typo in Baidu transformation in _config.yml (#714)
  • Sidebar button style on Pisces and Gemini (#735)
  • Mathjax li style issue (#752)
  • Remove no-wrap style from label tag (#763)
  • Breadcrumbs now work with both *.html and index.html pages (#769)

📖 Documentation

  • Add more contributors to contributors list (#639)
  • Make ISSUE and PR template more readable (#644)
  • Add CII badge. (#729)
  • Move some docs from _config.yml to official website (#725)
  • Update README.md, remove unused URLs (#727)
  • Add «Reporting Security Bugs» sections. (#730)
  • Change Riot chat link. (#733)
  • Add stevenjoezhang as a contributor (#741)
  • Add «Thanks» section (#739)
  • Add 1v9 as a contributor (#742)
  • Add JiangTJ as a contributor (#743)
  • Update labels and Chinese translation of CONTRIBUTING.md (#747)
  • Add liolok as a contributor (#755)
  • Contributors per line: 6 instead of 7 (#756)
  • Add ivan-nginx as a contributor (#757)
  • Add Improvement Need label (#768)

🌍 Localization

  • New Crowdin translations (#647)
  • New Crowdin translations (#650)

For full changes, see the comparison between 7.0.1 and 7.1.0

Detailed changes for NexT v7.1.0

Posted on Disqus:

Features

  • Added another code block copy button variant (#631)
  • Added language option to creative_commons (#628)
  • Added quicklink support (#612, #625)
  • Added sidebar auto close when click any blank part (#607)
  • Added localhost filter for google analytics (#618)

Optimizations

  • Refactored code block copy (#632)
  • Optimized the displaying of fancybox, mathjax and schedule (#603)
  • Removed tinysou and duoshuo_share (#565)

Bug Fixes

  • Fixed #594: External links didn't get replaced in index page (#599)
  • Fixed #609: Code block css style error (#610)
  • Fixed #601: Ordered list nested in unordered list became unordered (#602)
  • Fixed #587: Make Markdown table scrollable (#598)
  • Fixed comment count and reward QR (#595)

For full changes, see the comparison between 7.0.0 and 7.0.1

Detailed changes for NexT v7.0.1

Posted on Disqus:

Optimizations

  • Added deployer details configuration (#588)
  • Reorganize #576, using macro (#582)
  • Using Template literals (Template strings) (#557)
  • Fix #271: Add comment_count option (#559)
  • Code style update (formatting) (#563)

Bug Fixes

  • Revert using template literals in client side scripts. (#590)
  • Make request time of leancloud saved and let concurrent requests pass (#519)
  • Edit Google Analytics reference file address (#580)
  • Fix #573: [Muse & Mist] Footer is not at the bottom of the page (#574)
  • Update Gitment URL to use jsDelivr CDN (#572)
  • Fix #569 (#570)
  • Improve styles of Gitalk & Gitment (#568)
  • Optimize the loading of comment systems (#566)
  • Optimize the style of busuanzi, tag cloud and read more button (#561)

For full changes, see the comparison between 6.7.0 and 7.0.0

Detailed changes for NexT v7.0.0

Posted on Disqus:

From this year we will start to development NexT v7. And NexT v6 will not be cutted-out for now. Instead of this, we will continue maintenance for version 6 with simultaneous development of version 7.

Versions Difference

What changes planned in that versions? Good question, here they are:

  • Development (v7) mean → all bugfixes, optimizations and features will be added in this version.
  • Maintenance (v6) mean → all bugfixes and optimizations (partially) only will be added in this version.

As we can see, v6 will be more stable version, unlike of v7. If someone want more stability with less features, recommended to use v6 without any fear about no maintenance for this version in the future.

Objectives of Version 7

There are several globally targets for NexT v7 changes planned:

  • Replace all Nested Strings by Template Literals. This bring to code more readable (example: #557)
  • Cut out all possible 3rd-party libraries for provide minimum weight and maximum generation speed
  • Targets, described in NexT v7.x Roadmap.

Branching Models

All last year there are no problem with branching model management. All was simple:

  1. We had master branch, which at the same time was development and production branch.
  2. Changes created in separate temporarily branches were merged into master branch via pull request's.
  3. Once per month we made tag releases from current master branch.

It was when NexT development came with single version. For now, we must support multiple versions: v6.x and v7.x, what bring some complicated as for maintainers and for users too.

Last several days I thinking a lot about this and it seems the right way was successfully founded. And before understand my decision, let's see on all articles I finded.

  1. A successful Git branching model → https://nvie.com/posts/a-successful-git-branching-model/
    image
  2. Cactus model → https://barro.github.io/2016/02/a-succesful-git-branching-model-considered-harmful/
    image
  3. OneFlow model → https://www.endoflineblog.com/oneflow-a-git-branching-model-and-workflow
    image
  4. A stable mainline branching model → http://www.bitsnbites.eu/a-stable-mainline-branching-model-for-git/
    image
    image

So, lets comment this models:

  1. A little bit complicated for development. master branch keep only releases versions, but we already have tags once per month. And I read some negative responses about this branching model.
  2. Only one thing let me get to doubt: rebased branches. Yes, on local branches anyone can do what he's want, but we talking about remote branches, how we will working with them. This model is good, but need some changes to use it.
  3. Again: rebase + merge --no--ff – only with a little difference with allow to minimize merged commits history. Anyway, history will not linear.
  4. So, this is similar to our model, with except – releases created not only under the tags, but under branches too. As I understand, branches serve for temporary maintenance multiple software versions. And this model exactly what we need! With some changes, of course...
Read more »
0%