scikit-learn / scikit-learn/blog

Blog Theme & Design Discussion: Requests, Suggestions, Decisions

Open
#67 7 comments 1 reaction 2 assignees View on GitHub

@reshamas is already working on this.

Since Feb 4, 2022.

documentation
Dominant language
SCSS
Stars
24
Forks
30
Avg merge
6d 2h
Merged PRs (30d)
1

Description

Creating a new issue to log design requests, suggestions, and decisions. Please comment with new requests/suggestions or add your thoughts on the current requests/suggestions listed below.

CC: @reshamas @adrinjalali @jjerphan @ogrisel @thomasjpfan


Production

V1: blog.scikit-learn.org


Theme Options

Current Theme

Other Themes

Reference

Other Blogs

Current Design
Menus
  • Header: scikit-learn.org, Calendar, Resources
    • Dropdown: Install, User Guide, API, Examples
  • Sidebars
    • Social Media links
    • Archives: Category, Tag, Year
    • scikit-learn: About Us, FAQ, Code of Conduct
    • Mailing List: Subscribe, Archive
  • Footer: Social Media links, Feed
Home Page
  • Hero Banner: featured image, text
  • Recent Posts Queue
    • Request: Display posts' featured image
    • Author, read time
  • Twitter sidebar (currently hidden if viewer using adblock)
Posts
  • Display authors
  • Display Category, Tag
Pages
  • Calendar: embedded public scikit-learn event calendar
  • Resources

Requests & Suggestions
Previous Discussions
Requests
  • Request: show earlier posts to viewers
    • We currently have Category, Tag and Year archives. If you have suggestions of an alternative way to display earlier posts, please comment and provide a reference link if available.
  • Request: display the number of posts
    • Where should we display blog statistics?
    • Number of posts by category/tag/year? Total number?
  • Request: display posts' featured image in recent/archived posts queue
  • Do we want comments?
    • How would we deal with moderation?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.