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

Ideas for 1.5+ #4

Closed
92 tasks done
mayamcdougall opened this issue Nov 30, 2015 · 0 comments
Closed
92 tasks done

Ideas for 1.5+ #4

mayamcdougall opened this issue Nov 30, 2015 · 0 comments

Comments

@mayamcdougall
Copy link
Owner

Packaging

  • Provide sample config in a file.
    • Remove from ReadMe
    • "include" php and separate config file?
  • Include theme variants as Overrides in release.
    • WritingDesk
      • Menu Styles
      • Bullet Styles
      • Other Updates
    • SideBar
      • Sterilize Theme, move personal styles into a separate file.
      • New Background
      • Ribbon
      • Fix for Clearing Widgets Include note in readme.
  • Tag Cloud is another reason for TwigGetUrl
  • Update Readme
  • Spell Check All Files
  • Syntax Check All Files
  • Known Issues Section
  • Upgrade Instructions (replace config and migrate options as needed)
  • Temporary plugin
  • Alternate Readme's for sample themes. Used Lorem ipsum instead.
    • Sample tags, Documentation and Themes
    • Themes Subfolder for Header.
  • ToC Section change for new recursive mode (no _title)

Easy

  • Change "Defining" configs to True/False?
    • Change Facebook dark theme to True/False.
  • Fix SideBar Ribbon Zoom (partial)
  • Reverse Numerical Tag order. Right now, default is lowest first.
  • If statements for the Tag Widget Headers
  • Standardize Config Commas?
  • Capitolize "Theme: default" for consistancy?
  • Improved Recursive Navigation
  • Input validation for tags.cloud.levels? (prevent divide by zero, negatives)
  • Tag List is the only Bulleted list. Inconsistent.
  • Config.css array.
  • Move disabling options to a Disable array.
  • Blog posts aren't in Tag Cloud. Fixed.
  • Background Color for all elements (Especially Main. For fallback / loading)
  • Transitions for a:hover. feels slow... bad UX
  • Add a new "User Overrides" style sheet, independent of new themes.
  • Description rendering is triggered if not on front page when using TwigGetUrl....
  • New Variable for processed pages (widgets & etc removed) to simplify "page in pages" loops.
  • Padding and/or <hr> above bottom_links / search navigation buttons.
  • Custom font embed.
  • Configurable description length.
  • Max width instead of width for responsive design.
  • Option to hide ToC widget entirely.
  • Facebook Comments alternative to discuss.
    • Make sure Moderation and AppID works
    • Add Additional Facebook Options
    • NoScript Text (But FB Comments only work with blank tag)
  • Add Facebook's Debug page to readme for OG Image.
  • Other OG Options from variables
  • Option to disable page header
  • Option to turn off Display of Date (ribbon)?
  • Changed bottom_links.enabled == 'Blog' to 'blog' for consistency.
  • Investigate blog button behavior. At present, buttons still navigate to non-blog pages, trapping the user there.
  • YAML Error Message Notification

Medium

  • Themes
    • Include an override folder config option? This would allow multiple themes for NotePaper, emphasizing NotePaper as more of a layout / structure than a set theme.
    • Use meta header for per-file override!
    • {{ base_url ~ "assets/override/" ~ config.NotePaper.css_override ~ "/override.css" }}
    • Must decide before continuing: Dedicated Theme folder or use config options?
      • If I'm including some themes (internally or externally), they either need to be set in stone or the user has to correctly configure them...
    • Name them "themes" instead of override(s)? Is this too confusing?
    • An option to ignore override and load default theme, per file.
  • og:description from content or meta.description.
  • Fix Date Ribbon alignment if no page author.
    • Give article header a minimum size.
  • Tag List (create array of unique tags then print)
  • Tag Cloud (precount occurrences then break into sizes by percent. Config option for number of sizes?)

Hard

  • Combine front page and regular page code. If front page, swap meta.* for page.*, loop at end.
    • Refine, try to accomplish without Macro.
  • Option to move widgets to the Left side (using alternate CSS class)
  • Recursive Sub-navigation. Use an if _title function to detect a new layer of navigation instead of having it hard-coded to two levels of <ul>.
    • Sub-navigation Error Protection (Pico Shortcoming?)
    • Test against new "Ignore YAML parse errors" code in Pico
  • Recursive Folder Navigation (semi-experimental)
    • Incorrect rotation on Odd stickies.

Requires Pico Change / Plugin

  • Search Feature. Likely requires url access through php, either via plugin or an upstream change in Pico.
    • Simplify Front Page and search (and maybe regular page and comic layout) with a function that accepts different rendering conditions.
    • Refine and debug search.
    • Fix layout of short pages.
    • Fix search buttons.
  • Use Pico to generate link-able id's on headers. Handled by Markdown Extra
  • Better Pagination. Either work with Pico / write a plugin to get URL access or work with Pagination plugin to add a way to exclude Widgets.
    • For url access method, read url and advance loop count page-number * front-page-limit times before writing to front page.
    • Refine Pagination Bottom Links code.
      • Make bottom links hide on front page if no TwigGetUrl
      • Option to manually disable bottom links on front page
    • Should Bottom Links be automatically enabled in Front Page Mode? Should they be mandatory or have an optional toggle to disable? Yes, they are automatic (if FPM and TGU), but have an option to disable.
    • Prevent Out-of-Bounds on Front Page and search. (Move Precount up and check against it.)

Remember not to break things in point versions. Use a new version number for things that break.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant