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

Long road to 4.0 #271

Open
7 of 36 tasks
ikalnytskyi opened this issue Jan 21, 2022 · 0 comments
Open
7 of 36 tasks

Long road to 4.0 #271

ikalnytskyi opened this issue Jan 21, 2022 · 0 comments

Comments

@ikalnytskyi
Copy link
Owner

ikalnytskyi commented Jan 21, 2022

  • frontmatter processor
    • use --- for YAML format (hugo/zola style)
    • use +++ for TOML format (hugo/zola style)
    • autodetect format
    • allow delimiter overwrite
    • auto detect YAML/TOML by delimiter
  • commonmark processor
    • replace misletoe with markdown-it-py
    • support optional markdown-it-py extensions
  • items refactoring
    • website item should be set on the application level
    • generators should be using the item class from application using some factory/clone function
    • items must be regular dictionaries
    • items should get a helper method to return URL (absolute and with hash trick)
  • jinja processor
    • add filter/function to introduce "hashed" assets to overcome caching issue
  • command processor
    • a processor that can invoke any command and acts as a passthrough
    • or maybe the result is used as a content? 🤔
  • image processor
    • Use Pillow to resize or chance format
  • git processor
    • get updated_at and created_at values from git
    • get author from git
  • some processor to extract published date
  • Some general blog processor that
    • Takes source directory as input
    • Takes output directory as input
    • Sets feed generation
    • Sets renderer engines
    • Uses frontmatter by default
    • Generates sitemap
    • Contains NO LOGIC, only invokes other processors
  • Use dataclasses instead of mappings for the document models inside pipeline
  • Set document model class in the configuration class (to support various use cases)
  • Ensure that basic blog workflows is super simple and does not require dozens processors
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant