feat:blog - #100
Draft
luoliwoshang wants to merge 9 commits into
Draft
feat:blog#100luoliwoshang wants to merge 9 commits into
luoliwoshang wants to merge 9 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Member
Author
|
use > goplus.org@0.1.0 build:widgets
> tsc widgets/global/loader.ts && node widgets/build.js && rm widgets/global/loader.js
node_modules/@types/node/globals.d.ts:72:13 - error TS2403: Subsequent variable declarations must have the same type. Variable 'AbortSignal' must be of type '{ new (): AbortSignal; prototype: AbortSignal; abort(reason?: any): AbortSignal; timeout(milliseconds: number): AbortSignal; }', but here has type '{ new (): AbortSignal; prototype: AbortSignal; }'.
72 declare var AbortSignal: {
~~~~~~~~~~~
node_modules/typescript/lib/lib.dom.d.ts:2071:13
2071 declare var AbortSignal: {
~~~~~~~~~~~
'AbortSignal' was also declared here.
Found 1 error in node_modules/@types/node/globals.d.ts:72 |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Like Go's official blog system (References: https://go.dev/blog/ and https://github.com/golang/website)
Design
Blog List Page
Path: goplus.org/blog/
Like https://go.dev/blog/
"More articles" button/link that leads to the complete blog list
Path: goplus.org/blog/all
Like https://go.dev/blog/all
Blog Post Format
Following Go's blog post structure, each blog post should be written in Markdown with a metadata header:
The Go website sorts blog posts based on the Date field in their metadata, using the
YYYY-MM-DDformat. While this approach includes a secondary sort by title, it may not always reflect the precise posting order.Although introducing an ID field could solve this, it would add unnecessary cognitive overhead for post authors.
I believe the current time-based sorting offers a significant advantage: it allows authors to write posts in a natural Markdown style (despite requiring metadata), similar to how they would write any other Markdown document.
However, I suggest using the
YYYY-MM-DD HH:mm±HH:mmformat for the date field. This would:Blog Detail Page
Path: goplus.org/blog/article/[slug]
Like https://go.dev/blog/swisstable
Renders the corresponding md_name.md file
Includes navigation links to previous and next blog posts
Image Handling
Two approaches for handling images in blog posts:
1.Standard Markdown Format (Current GoPlus approach):
Note: For now, maintain the current markdown image syntax without modification. Use default styling for markdown images.
Expect Markdown source structure
in /goplus.org/articles
Implement
react-markdown not render the heading's id remarkjs/react-markdown#69 and it's not the basic markdown feature.
maybe support it in another pr.