To-Do
| Title | Description | Type | Difficulty | Priority | Status |
|---|---|---|---|---|---|
| New table interface | Replace inMenu, inList, template properties, with groups. | Core | Medium | High | Next up |
| Backlinks | Core | Difficult | Medium | Next up | |
| Simplify deployment procedures | Extension | Medium | High | Proposal | |
| Seperate page data downloading and HTML rendering stages | In order to implement Nested sub-pages and enable the usage of any content at any place (now only metadata has this freedom). | Core | Medium | Medium | Proposal |
| Support Svelte as a template engine | Svelte is a easy-to-use framework with many attractive characteristics: built-in scoped CSS, the concept of component, efficient, writing less and cleaner code, etc. It is more ideal than React for building personal websites. But the hard part to integrate Svelte is the need to use its internal compiler API to get the effect I want — compile the components in a theme, then emit prerendered HTML, bundled CSS and JS. Note that for just SSR like GatsbyJS there is Sapper, but it does not fit well into Notablog's desired workflow. | Extension | Difficult | Medium | Proposal |
| RSS | Create a Notablog extension module that generates RSS feed. | Extension | Medium | Medium | Proposal |
| Nested sub-pages | Currently, Notablog does not generate static pages for nested sub-pages but links them to their original Notion page. This proposal wants Notablog to generate static pages for the nested sub-pages, so they get the same smooth viewing experience. | Core | Difficult | Low | Proposal |
| Be able to use markdown files as content source | See page content. | Core | Difficult | Low | Proposal |
| New theme structure | See page content. | Extension | Medium | Low | Proposal |
| Full-site Search | Create a Notablog extension module that generates a JSON containing all information about the site and add a client-side search component. | Extension | Medium | Low | Proposal |
| Favicon | Need to handle both emoji and image. | Other | Medium | Low | Proposal |
| Non-linear viewing structure | Expose the tree structure to the user so they can use their own rendering mechanism to generate non-sequential representation of their data. The ideas include but not limited to: a graph that shows connections between pages, a tree that shows TOC of an article, parallel pages, timeline for exploring changes. | Other | Difficult | Low | Proposal |
| Be able to integrate content from other Notablog tables | Treat Notablog as a pool for all information one is interested in, and one can remix the collected information to build something one would like to present. | Other | Difficult | Low | Proposal |
| Theme builder | A tool to develop theme. Get inspiration from Storybook or Blockly. | Other | Difficult | Very Low | Proposal |
| Option to mark updated portions when a user views a page | See page content. | Other | Difficult | Very Low | Proposal |
| Integrate W3C Web Annotation | Other | Unknown | Very Low | Proposal | |
| Adopt data model of Ghost | https://ghost.org/docs/concepts/posts/ | Rejected | |||
| Notablog extension module architecture | Core | Difficult | Medium | Rejected | |
| Checkbox for publishing | A checkbox to decide if a post should be published. | Completed | |||
| Set the template to use | Per post setting about which template to use. | Completed | |||
| Manually set date | Useful when importing older posts from other platforms. | Completed | |||
| Clickable tags | Click a tag to jump to an index page listing all posts with the tag. | Completed | |||
| Migrate to TypeScript | Core | Medium | Very High | Completed | |
| Supprt EJS as a template engine | In order to be able to include partials directly in templates | Extension | Easy | High | Completed |