Ideas for 1.6+

[mayamcdougall]

Easy

• New Search Widget
  • Reset default value when clicked out of, if no value.
• Debug: Displays no content without NP Config on Pico's Sample-Content
• Hide ToC on GitHub (Somehow comment it out without affecting Pico?)
• meta.css_override for per-page css overrides.
• Check Content length before adding ellipsis to description.
  • Debug to make sure it properly adheres to the description length cutoff
  • Move description code to a macro?
  • Actually render beginning of document in search instead of tag-stripped description?
    • Would probably break HTML flow (random headers, etc)
  • Move description to separate variable? (Would need to be an array/merged?)
• Move bottom_links.enabled = 'blog' to bottom_links.blog. (Permanent fix for issue 1.5.2 solves)
• Option to reverse front page order. (Careful not to reverse search order)
• Fixed in v1.5.1 overflow: hidden on SideBar's h1 was a bad idea ("g"s and etc get cut off)
• Facebook comments improvements.
  • Better / More consistant NoScript for both Discus and Facebook
    • Combine comment "Sections" into one shared section?
  • Creative, floating sticky note style NoScript. Separate element, floating over a padded comments section.
  • Loading Animation?
• Standardize Quotes
• Indicate current page of Table of Contents in a non-invasive way. Maybe a list-style-type image or a character (~) in ::before content.
• Always Display Sub-Navigation (config option)

Medium

• Animations for loading! Maybe. It'll be an option to enable.
• Recent Posts Widget
• SideBar: Fix for Clearing Widgets
• Better Processing of Tags: Trim leading/trailing spaces and escape middle ones.
• Fix for Tags all being the largest size if they're all the same number (eg one of each)
• Custom widget types using css_override and {{ page.meta.widget }} as an html class.
  • Built in styles / formatting options (such as centered text) to stack with regular widget styles.
    • How would sticky_num work in this situation? Only for stickies? Or add a new, separate class?
• Webcomic Layout Option for Front Page.
• Date Ribbon Fixes
  • Fix title vertical alignment if no author.
  • Change Ribbon Margins to relative positioning? Move ribbon below title/author.
• Change widgets into different html element since they aren't really navigation. (Currently using <nav> tag).
• Use an Image in a page title. It would be defined with a Meta header and use the Title header as an alt tag. (designed for System Panic)
• Better Processing of search? Handle Spaces
  • Author Search
  • Combine Tag and Author Search into a universal "Search Type" variable.
  • Move enhanced search logic out of main loop.
• Alphabetical Sub-Ordering for Numerical Tag Order

Hard

• Make input validations write to NotePaper array directly instead of temporary variables.
• Simplify the Front Page logic to be less repetitive. Condense many tests (search, tags, etc) into one true/false variable. Maybe calculate this in advance and store it in an array (or np_pages).
• Front Page Excerpt Mode using Meta Description / page excerpts.
• Separate out "blog" pages into a separate navigation array? (Regular pages navigate to regular pages, blog pages navigate to other blog pages).
• An option to limit the Front Page to only display "blog" pages.
• Option to utilize Folder Menus for meta.toc's
• Images that resize around widgets.
• Include embedded fonts instead of Google fonts? (Performance?)
• Sub-Folder Front Page (A index page that combines only items in that subfolder)
  • Should there then be an option to hide sub-folder pages from the main front page?
• Folder Menu Z-Index Issues
• Option to disable individual bottom_link buttons, but only on front page
• Find a better way to make bottom links hide on front page if no TwigGetUrl, without additional variable
• Fix for the "Kind of awful" ampersand2 in url generation
  • Loop on an array of query variables. ? on loop.first unless using rewrite engine.
• Fix SideBar Ribbon Zoom (size calculation differences on borders)

Fun (Stashed, not commited)

• Special Pages. The ability to parse a markdown file and insert twig code into main article area. Might not be currently possible with Pico. Might be able to accomplish with hooks in NotePaper's twig template that look for a file matching the name of a custom meta header.
  • Add an override to config to turn this off (for permission reasons). Should be disabled by default. Requires Plugin, so innately disabled by default.
  • Extend "Include" rendering to Search/Tag/OG Descriptions Impossible. Automatic descriptions could truncate a Twig tag and bring down the entire page.
    • Only possible if Template can be processed first, then returned to a string.
    • Might behave unexpectedly if meta is referenced since you're on a different page than the content. This also applies to Front Page Mode though, and so may already be an issue.
    • meta. is replaced with page. automatically, but this happens regardless of whether it appears in tags or content. Not a good solution.
  • Meta substitution with page.id.
  • If this is too messy, perhaps just disable Twig processing on Front/Search/Tag pages. Also, someone may want to use meta. in a widget to reference the current page and not have it converted to page. accidentally referencing the widget...
  • Use "Special Pages" to import Readme onto theme example pages.
  • Special Pages could also be used for dynamic widgets.
    • Tags widgets could potentially be external.

Other / Future

• Modularize Widgets, allowing a user to specify their order in NotePaper's config.
• Modularize NotePaper (features, widgets, etc) into a more customizable framework.
  • Separate features from their structure.
    • Features would be macros / code blocks that could be imported into a customized structure.
    • Ideally, this should allow completely rewriting of NotePaper into a new template without losing any features.
    • All features / code blocks would need to be capable of working independently of one another.
  • NotePaper may become a Theme/Structure of this new environment.
    • NotePaper's current features should continue being developed under the new system, while NotePaper (theme) and other templates would be able to utilize them.