You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix queries (see error 500 on /all when logged out)
Separate into different module via interface
Migrations command
When entry does not exist in disk, simply remove it, no fail
Media endpoint: upload to /u/
Make CDN endpoint not hardcoded
Every time eagle starts, it can start with a flag "ensure consistency" where we check if all posts exist or not and remove non-existent ones
/dashboard page with some commands: rebuilt assets, clean cache, reload redirects, sync, new, etc.
Do not show listing override pages (like sections, tags, index) on search. Maybe use _index for those listings and add a boolean value to the Entry struct that is passed onto the database.
A very basic cache was implemented with a 1 day TTL. It does not cache pages with queries and its main goal is to serve listing pages as those are the ones that take slightly more time to render. Probably not really needed, not a lot of traffic. We'll see in production.
When code is stable and almost ready to deploy
Disable IPFS building on current website
Run migration script
Add /index.html on experiments on more page and more links in categories sections
Fix post images when src is relative to the page (make it relative to /)
Post /links as bookmarks and rename links to blogroll (redirect).
v2: After Release
(See other issues)
v2: File Structure
/app/source
/content --> For posts.
/my-post
index.md --> Post frontmatter and data.
my-file.jpg --> Some public file.
_webmentions.json --> Hidden from public eyes.
/static --> Directly served static files.
/assets --> Pre-processed files.
/layouts --> HTML templates and layouts.
The text was updated successfully, but these errors were encountered:
TODO
/u/
/dashboard
page with some commands: rebuilt assets, clean cache, reload redirects, sync, new, etc.Do not show listing override pages (like sections, tags, index) on search. Maybe use_index
for those listings and add a boolean value to theEntry
struct that is passed onto the database.{{< figure
to new syntax/static
,/content
/content2
to/content
<!--more-->
to single pages that show up in search.noSendInteractions
to some pages, such as /more, /watches, /listensDone
/stream
/all
/
/tags/{tag}
Code HighlightI don't do that many technical posts RN so I'll ignore this now. Can use https://github.com/yuin/goldmark-highlighting if needed./tags
properties.photo
are added tophotos
sectionAt $PlaceName
/new
page/section/feed.{json|xml}
to/section.{json|atom}
<head>
info such as alternateRenderData.Data
interface more and remove some vars (Entries, Terms, etc).After Deploying
/links
as bookmarks and rename links toblogroll
(redirect).v2: After Release
(See other issues)
v2: File Structure
The text was updated successfully, but these errors were encountered: