- Updated readme
- Used double quotes instead of single quotes
- Increase blog content width
Before
After
- Added subscribe and community components to buttom of the blog post page.
Loading:
Post sent:
Mobile:
Reviewed-on: https://gitea.com/gitea/blog/pulls/272
Co-authored-by: HesterG <hestergong@gmail.com>
Co-committed-by: HesterG <hestergong@gmail.com>
as title
Reviewed-on: https://gitea.com/gitea/blog/pulls/269
Co-authored-by: HesterG <hestergong@gmail.com>
Co-committed-by: HesterG <hestergong@gmail.com>
- Found one author whose account is 404 on gitea.com now, so removed url and image url
- Fix blog links
- Use svg instead of png for favicon
- Changed number of post per page to 12
- Hide toc and show "recent post" sidebar on post pages
- Fix active status missing for tags when on pagination
Before (active status missing if not on first page of certain tag's page)
After:
Reviewed-on: https://gitea.com/gitea/blog/pulls/268
Co-authored-by: HesterG <hestergong@gmail.com>
Co-committed-by: HesterG <hestergong@gmail.com>
# Notes
- date must not have double quotes, e.g., should be like `date: 2022-10-30T18:25:00+09:15`
- Updated header.
- Used customized blog plugin to get all tags with reference to [plugins/blog/index.js](https://github.com/questdb/questdb.io/blob/master/plugins/blog/index.js). Filter by tag section, tag list page.
- Added coverImage to frontmatter to assgin cover image, e.g., `coverImage: "/img/blog-covers/test.jpeg"`
And on blog page, cover image will appear on top if `coverImage` added to frontmatter, e.g.,
- authors are managed by the `authors.yml` file. [reference](https://docusaurus.io/docs/blog#global-authors)
- [ejected](https://docusaurus.io/docs/swizzling#ejecting) `@docusaurus/theme-classic BlogListPage` and `@docusaurus/theme-classic BlogPostPage`, which are marked as `unsafe` by docusaurus, so need to maintain these components. ([original BlogListPage](https://github.com/facebook/docusaurus/blob/main/packages/docusaurus-theme-classic/src/theme/BlogListPage/index.tsx), [original BlogPostPage](https://github.com/facebook/docusaurus/blob/main/packages/docusaurus-theme-classic/src/theme/BlogPostPage/index.tsx))
- [referenced repo](https://github.com/questdb/questdb.io)
# How to test
```
npm i
npm run start
```
# Build and serve
```
npm run build
npm run serve
```
# Help Needed
Deploy and preview steps
# More Screenshots
Mobile:
# TODO
- [x] Add Banner to blog page
Reviewed-on: https://gitea.com/gitea/blog/pulls/266
Co-authored-by: HesterG <hestergong@gmail.com>
Co-committed-by: HesterG <hestergong@gmail.com>
anyone else who made edits to this post, please feel free to add your name to authors :)
Reviewed-on: https://gitea.com/gitea/blog/pulls/260
Reviewed-by: John Olheiser <john+gitea@jolheiser.com>
Reviewed-by: yardenshoham <yardenshoham@noreply.gitea.io>
Reviewed-by: silverwind <silverwind@noreply.gitea.io>
Co-authored-by: techknowlogick <techknowlogick@gitea.io>
Co-committed-by: techknowlogick <techknowlogick@gitea.io>
Now that we have a JSON endpoint for posts, tagging posts can aid in filtering that data in the future.
For example, the docs could list any posts tagged `tutorial` or `feature` somewhere.
Reviewed-on: https://gitea.com/gitea/blog/pulls/259
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Reviewed-by: pat-s <pat-s@noreply.gitea.io>
Co-authored-by: jolheiser <john.olheiser@gmail.com>
Co-committed-by: jolheiser <john.olheiser@gmail.com>
This will expose a JSON endpoint with all the pages and some meta.
It would allow us to, for example, filter posts by `tag` and maybe link to them from our main docs.
e.g. a follow-up PR to tag any "feature preview"-style posts and then link to them from our docs.
Reviewed-on: https://gitea.com/gitea/blog/pulls/249
Reviewed-by: delvh <dev.lh@web.de>
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: jolheiser <john.olheiser@gmail.com>
Co-committed-by: jolheiser <john.olheiser@gmail.com>
cc: @delvh not sure if you want to add yourself as an author for this too, as I believe you provided edits to the draft
Reviewed-on: https://gitea.com/gitea/blog/pulls/247
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Reviewed-by: John Olheiser <john+gitea@jolheiser.com>
Reviewed-by: delvh <dev.lh@web.de>
Co-authored-by: techknowlogick <techknowlogick@gitea.io>
Co-committed-by: techknowlogick <techknowlogick@gitea.io>
Reviewed-on: https://gitea.com/gitea/blog/pulls/245
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.io>
Reviewed-by: 6543 <6543@obermui.de>
Co-authored-by: Jason Song <i@wolfogre.com>
Co-committed-by: Jason Song <i@wolfogre.com>
Following the example repo at https://gitea.com/gitea/website-pr-preview, this PR will allow for automatically generated PR previews.
Required drone secrets:
- [ ] `GITEA_ACCESS_TOKEN`
- [ ] `AWS_ACCESS_KEY_ID`
- [ ] `AWS_SECRET_ACCESS_KEY`
I've also adjusted the old pipeline to only run for pushes to the default branch to avoid unneeded runs.
Co-authored-by: pat-s <patrick.schratz@gmail.com>
Reviewed-on: https://gitea.com/gitea/blog/pulls/237
Co-authored-by: pat-s <pat-s@noreply.gitea.io>
Co-committed-by: pat-s <pat-s@noreply.gitea.io>
The original PR was labeled as `breaking`, however the backport was labeled `security` (both of which are technically true) and so we didn't end up adding it to the breaking changes section.
Co-authored-by: jolheiser <john.olheiser@gmail.com>
Reviewed-on: https://gitea.com/gitea/blog/pulls/234
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Reviewed-by: yardenshoham <yardenshoham@noreply.gitea.io>
After reaching out, using the personal site for attribution was preferred.
Co-authored-by: jolheiser <john.olheiser@gmail.com>
Reviewed-on: https://gitea.com/gitea/blog/pulls/231
Reviewed-by: delvh <dev.lh@web.de>
Reviewed-by: yardenshoham <yardenshoham@noreply.gitea.io>
Release blog for 1.18.1
Co-authored-by: jolheiser <john.olheiser@gmail.com>
Reviewed-on: https://gitea.com/gitea/blog/pulls/227
Reviewed-by: Andrew Thornton <art27@cantab.net>
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io>
Co-authored-by: John Olheiser <john+gitea@jolheiser.com>
Co-committed-by: John Olheiser <john+gitea@jolheiser.com>
1. Someone from the community brought up the prominence (or lack of) for breaking changes, so I brought it to the top before features.
2. I changed "Important Features" to "Feature Highlights"
All features are important, but these are the ones being highlighted on the release post. 🙂
Co-authored-by: jolheiser <john.olheiser@gmail.com>
Reviewed-on: https://gitea.com/gitea/blog/pulls/224
Reviewed-by: KN4CK3R <kn4ck3r@noreply.gitea.io>
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
HesterG
techknowlogick
techknowlogick
6543
Lunny Xiao
jolheiser
techknowlogick
John Olheiser
Zettat123
sillyguodong
Jason Song
delvh
pat-s