Hi @thien-do, please update env vars:

UPSTASH_REDIS_REST_URL
UPSTASH_REDIS_REST_TOKEN

To values taken from https://cloud.keva.dev/console

Notice: please destroy & re-create the instance before getting the credentials, click Connect button:

UPSTASH_REDIS_REST_URL => https://cloud-rest-api.keva.dev UPSTASH_REDIS_REST_TOKEN => token (without Bearer)

(remove Bearer string for the token value)

Looking at the code: https://github.com/thien-do/memos-pub/blob/514de8d64339c41690986f57ed2a8b6d363eaa0b/lib/blog/dir/entry.tsx#L16

d = new Date("03.22.2022");
> Tue Mar 22 2022 00:00:00 GMT+0700 (Indochina Time)
d.toISOString()
> '2022-03-21T17:00:00.000Z'

Some blogs have date in their article titles:

At the moment there is no special treatment for them. However we'd like to separate them visually from the rest of the title, like this:

Not all blog uses the same format, or have date, so we just try to support yyyy mm dd, and do nothing if none match:

yyyy-mm-dd title
yyyy/mm/dd title
yyyy.mm.dd title

So I guess the regex is:

^\d{4}[-/.]\d{2}[-/.]\d{2} 

The change should happen around here:

https://github.com/thien-do/memos-pub/blob/2601f453bac69d2440a68dfa16b260626fccfc7b/lib/blog/dir/entry.tsx#L17-L21

I have some questions:

• Does Google find my blog on the internet?
• Can I add Google Tag Manager / Google Analytics to my blog?
• Can I add sitemap to my blog?

[Link](https://memos.pub/)

Current: Links in markdown files open in the same tab. Expected: I think it's better if links in markdown files default to open in a new tab.

What

Change mono font from Cascadia to Cascadia Mono. Initially I want to use font-variant-ligatures: none; but that could affect incoming features where users can have custom memos.pub settings in their repo, including changing default fonts?

*but the more I think about it, isn't memos.pub's goal is to keep everything simple and it just works? So maybe custom settings shouldn't be a feature? I don't know 🤷

Why

Cascadia has ligatures enabled by default, which can trigger some people (me).

Comparison

Before

After

In repo root, the user can add configuration via memos.json or .memos or memos.config.js or something else.

What does configuration file do?

• Setting fonts, themes
• Relative assets path if needed
• Date and title format, even sorting order
• ...

Currently, memos-pub show every file in a folder. This led to a situation where the folder only has 1 markdown file, for example, README.md, we still list that file.

notes
└ post-001
  └ README.md

For example https://ledongthuc.memos.pub/notes/leetcode/binary-search-tree-iterator

A good way to go about this situation is using Github's default behavior, always render the content of README.md file in a folder. There will be a case where the user want to navigate into subfolders, in this case we can skip the render.

So, to summarize, I think we should adopt a render behavior as follow:

• If a folder has nothing but a README.md file, we can just render that file out.

  notes
  └ post-001
    └ README.md
  
  URL: /notes/post-001 -> Render the README.md
  URL: /notes/post-001/README.md -> Also render the README.md
  

• If the folder does not have any markdown file, render the folder as a list

  notes
  └ post-001
    └ a-sub-folder
  
  URL: /notes/post-001 -> Render the folder list
  URL: /notes/post-001/a-sub-folder -> Render empty list
  

  The empty folder case can be handled in #6

• If the folder contains both README.md file and other files/folders, render the folder as a list

  notes
  └ post-001
    └ README.md
    └ other.md
    └ subfolder
      └ README.md
  
  URL: /notes/post-001 -> Render the folder as a list
  URL: /notes/post-001/README.md -> Render the README.md
  URL: /notes/post-001/subfolder -> Render the subfolder/README.md 
  

• (Nice to have) If the folder contains both README.md file and other files, but none of them are markdown file, we should consider rendering the README.md file as default:

  notes
  └ post-001
    └ README.md
    └ img.png
    └ virus.exe
  
  URL: /notes/post-001 -> Render the README.md 
  

I navigate from this site to the article inside, but the waiting time so long, a little confused about is this page being navigated?

I think adding a loading icon or process bar will get a better experience for users.

What

Example: https://notes.ancaois.me/notes/404

Currently "Go home" in page 404 is linked to https://memos.pub/. It should be linked to the hosted homepage, e.g. https://notes.ancaois.me in this case.

Some quick notes:

Namespace:

• https://github.com/gitlabhq/gitlabhq

API:

• https://docs.gitlab.com/ee/api/repository_files.html#get-file-from-repository
• https://gitlab.com/api/v4/projects/gitlab-org%2Fgitlab/repository/files/README.md?ref=master
• https://gitlab.com/api/v4/projects/gitlab-org%2Fgitlab/repository/tree

Tests:

• https://gitlab.com/gitlab-com/gl-infra/scalability/-/tree/master/doc
• https://gitlab.com/gitlab-com/gl-infra/ci-runners/deployer
• https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc
• https://gitlab.com/gitlab-org/gitaly
• https://gitlab.com/gitlab-org/gitaly/-/blob/master/doc/sidechannel.md
• https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/development/cicd/img/ci_architecture.png (has image)

Hi @thien-do, please update env vars to integrate with Keva Cloud:

UPSTASH_REDIS_REST_URL
UPSTASH_REDIS_REST_TOKEN

Please note that Keva Cloud is completely compatible with Redis and Upstash Redis client

Log in to the cloud console at https://cloud.keva.dev/console

Here something that memos.pub benefits from github app:

• github app use its own api token

  A GitHub App acts on its own behalf, taking actions via the API directly using its own identity, which means you don't need to maintain a bot or service account as a separate user.

• repo configuration become easy with single file permission

• invalidated cached with webhook (github app can subscribe to repo's event)

• increase visibility through github marketplace

• still "without setup or sign up" since user's content already hosted on github, installing a github app is as easy as enabling github page

links: about apps, permission, example, ko-fi

Memos.pub instantly makes a blog out of any public GitHub repo, with beautiful typography, MDX support, custom domain, and more.

Is there any guide to setting up a custom domain for now? I think it can be just simple as in Netlify, just point your domain CNAME record to some-blog.memos.pub.

Also, the 404 error happened on the org link:

https://keva-dev.memos.pub/blog

Not sure if this is a bug or an expected behavior

I think, to increase user adoption, we can support them in customizing their page's CSS styles.

It could be done after #18 is implemented. We could either put the custom style inside the JSON file (a horrible approach) or let the user create their own memos.css something.

Think about the Yahoo 360-era.

Some example of a similar service with support for custom styles:

• https://thoughts.page/webring
• https://bearblog.dev/discover/

We should let user to increase/decrease the font size or spacing in FE & save the setting to local storage/cookies.

Perhaps also letting repo owner to set default setting in their repo config?