Skip to content

Commit fb016c1

Browse files
authored
Merge branch 'main' into chore/download
2 parents 61024b5 + 7cadafb commit fb016c1

File tree

15 files changed

+97
-31
lines changed

15 files changed

+97
-31
lines changed

blog/answer-1.5.0-release/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
date: 2025-04-30
3-
title: "Answer 1.5.0: New Sidebar Layout & Tag Merge Feature"
3+
title: "Apache Answer 1.5.0: New Sidebar Layout & Tag Merge"
44
authors: [shuai]
55
category: Release
66
featured: true
@@ -50,4 +50,4 @@ Added a tag merge feature for administrators and moderators. After merging, ques
5050
A big thanks to all contributors who helped develop this release (sorted by GitHub ID):
5151
[@hgaol](https://github.com/hgaol), [@LinkinStars](https://github.com/LinkinStars), [@seiyab](https://github.com/seiyab), [@shuashuai](https://github.com/shuashuai), [@sy-records](https://github.com/sy-records), [@xuthus5](https://github.com/xuthus5)
5252

53-
Your contributions made this release even better! 🚀
53+
Your contributions made this release even better! 🚀

blog/answer-1.5.1-release/index.md

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
date: 2025-06-03
3+
title: "Apache Answer 1.5.1: Now Available with Improvements and Fixes"
4+
authors: [LinkinStar]
5+
category: Release
6+
featured: true
7+
8+
description: "Answer 1.5.1 Enhanced Navigation, Admin Menu Improvements & Key Bug Fixes"
9+
---
10+
11+
# Version 1.5.1 Release Notes
12+
13+
We're excited to announce the release of version **1.5.1**! This update brings several improvements and bug fixes to enhance usability and stability. Below are the key changes in this release.
14+
15+
---
16+
17+
## 🔧 Improvements
18+
19+
- **Separate Background Color for Navigation**
20+
The navigation bar now has a distinct background color for better visual separation and improved user experience. *(Thanks @shuashuai & @LinkinStars [#1346](https://github.com/apache/answer/pull/1346))*
21+
22+
- **Enhanced Admin Menu**
23+
The admin menu has been refined for better organization and usability. *(Thanks @shuashuai [#1345](https://github.com/apache/answer/pull/1345))*
24+
25+
- **Refined Command Usage Statements**
26+
Command-line tool usage descriptions have been improved for clarity. *(Thanks @Octobug [#1330](https://github.com/apache/answer/pull/1330))*
27+
28+
- **Comprehensive Tests for KV Storage Plugin**
29+
Added thorough testing for the key-value storage plugin to ensure reliability. *(Thanks @sosyz [#1344](https://github.com/apache/answer/pull/1344))*
30+
31+
---
32+
33+
## 🐞 Bug Fixes
34+
35+
- **Google Login Users Losing Image Access**
36+
Fixed an issue where users logging in via Google connector couldn't access images. *(Thanks @Giorgio-Bonvicini-R4P [#1334](https://github.com/apache/answer/pull/1334))*
37+
38+
- **Username Minimum Length Inconsistency**
39+
Resolved a mismatch where the admin panel still enforced a 4-character minimum despite the setting being reduced to 2. *(Thanks @sy-records [#1341](https://github.com/apache/answer/pull/1341))*
40+
41+
- **Code Snippet Layout Breakage**
42+
Fixed a bug where code snippets could disrupt the page layout. *(Thanks @shuashuai [#1329](https://github.com/apache/answer/pull/1329))*
43+
44+
- **Image Placement When Copying Mixed Content**
45+
Corrected an issue where pasted images would always appear at the end of copied text-and-image content. *(Thanks @shuashuai)*
46+
47+
---
48+
49+
## ❤️ Thanks to Our Contributors
50+
51+
A huge thank you to all the contributors who helped improve this release (sorted by GitHub ID):
52+
[@Giorgio-Bonvicini-R4P](https://github.com/Giorgio-Bonvicini-R4P), [@LinkinStars](https://github.com/LinkinStars), [@Octobug](https://github.com/Octobug), [@shuashuai](https://github.com/shuashuai), [@sosyz](https://github.com/sosyz), [@sy-records](https://github.com/sy-records)
53+
54+
Your contributions make this project better with every update! 🚀
55+
56+
---
57+
58+
**Upgrade now** to enjoy these improvements and fixes! If you encounter any issues, please report them on [GitHub](https://github.com/apache/answer/issues).
59+
60+
Happy browsing! 🎉

blog/deploy-answer-https/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
date: 2024-01-26
33
title: "How to Access Answer Using HTTPS"
44
authors: [LinkinStar]
5-
category: Tech
5+
category: Tutorials
66
featured: true
77
88
description: "Got your Answer server up and running? Now, let's take it to the next level with HTTPS with the tutorials."
@@ -99,4 +99,4 @@ your.answer.domain {
9999
}
100100
```
101101

102-
Of course, you can also install Caddy using other methods, such as using the binary file, etc. All in all, I wish you can follow this blog to deploy Answer with HTTPS successfully. If you have any questions, please feel free to leave a question on [Meta](https://meta.answer.dev/). We will try our best to help you.
102+
Of course, you can also install Caddy using other methods, such as using the binary file, etc. All in all, I wish you can follow this blog to deploy Answer with HTTPS successfully. If you have any questions, please feel free to leave a question on [Meta](https://meta.answer.dev/). We will try our best to help you.

blog/why-the-answer-plugin-system-was-designed-this-way/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
date: 2023-07-22
33
title: The Packaging Process for Answer Plugins
44
authors: [LinkinStar]
5-
category: Tech
5+
category: Tutorials
66
featured: true
77
88
description: "Let's discuss the design and implementation of the plugin system for Answer, and know why we design this way."
@@ -80,4 +80,4 @@ Using [xcaddy](https://github.com/caddyserver/xcaddy/) can easy to make custom b
8080
In this blog post, we discussed the design and implementation of the plugin system for Answer, a popular open-source Q&A platform.
8181
We discussed the motivation behind the design, and the features and principles of the plugin system, and provided a step-by-step guide on implementation.
8282
If you are interested in developing plugins for Answer, please feel free to leave us a comment.
83-
We will also write an article on how to implement an Answer plugin from scratch, so stay focused!
83+
We will also write an article on how to implement an Answer plugin from scratch, so stay focused!

docs/getting-started/command-line.md

Lines changed: 16 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ slug: /command-line
66

77
:::tip
88

9-
Apache Answer binary support some command-line options
9+
Apache Answer binary supports some command-line options
1010

1111
:::
1212

@@ -15,23 +15,26 @@ Apache Answer binary support some command-line options
1515
`answer command [command or global options] [arguments...]`
1616

1717
```shell
18+
Answer is a minimalist open source Q&A community.
1819
To run answer, use:
1920
- 'answer init' to initialize the required environment.
20-
- 'answer run' to launch the application.
21-
- 'answer upgrade' to upgrade the application
21+
- 'answer run' to launch application.
2222

2323
Usage:
2424
answer [command]
2525

2626
Available Commands:
27-
build used to build answer with plugins
28-
check checking the required environment
29-
dump back up data
27+
build Build Answer with plugins
28+
check Check the required environment
29+
completion Generate the autocompletion script for the specified shell
30+
config Set some config to default value
31+
dump Back up data
3032
help Help about any command
31-
init init answer application
32-
plugin prints all plugins packed in the binary
33-
run Run the application
34-
upgrade upgrade Apache Answer version
33+
i18n Overwrite i18n files
34+
init Initialize Answer
35+
plugin Print all plugins packed in the binary
36+
run Run Answer
37+
upgrade Upgrade Answer
3538

3639
Flags:
3740
-C, --data-path string data path, eg: -C ./data/ (default "/data/")
@@ -95,6 +98,7 @@ All global options can be placed at the command level.
9598
- `answer dump -p /tmp/`
9699

97100
### build
101+
98102
> build a new Apache Answer with plugins.
99103
100104
- Options
@@ -103,12 +107,14 @@ All global options can be placed at the command level.
103107
- `answer build --with plugin1 --with plugin2`
104108

105109
### plugin
110+
106111
> prints all plugins packed in the binary.
107112
108113
- Examples
109114
- `answer plugin`
110115

111116
### config
117+
112118
> restore some config value to default.
113119
114120
- Options

i18n/zh-CN/docusaurus-plugin-content-blog/why-the-answer-plugin-system-was-designed-this-way/index.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -2,31 +2,31 @@
22
date: 2023-07-22
33
title: The Packaging Process for Answer Plugins
44
authors: [LinkinStar]
5-
category: Tech
5+
category: Tutorials
66
featured: true
77
88
description: "Let's discuss the design and implementation of the plugin system for Answer, and know why we design this way."
99

1010
---
11-
> 1. Why is Answer's plugin system designed in such a way that it seems a bit of difficulty to use?
11+
> 1. Why is Answer's plugin system designed in such a way that it seems a bit difficult to use?
1212
> 2. How can I implement plugin functionality using Golang?
1313
> 3. What exactly does Answer's plugin system do when it is compiled and packaged?
1414
1515
## Background
16-
You can build a Q&A community using answer easily. However, the basic features of Answer may not sufficiently support to every use case.
16+
You can build a Q&A community using Answer easily. However, the basic features of Answer may not sufficiently support to every use case.
1717
Therefore, we need to design a plugin system to extend its features.
1818
As you may know, Answer is built using `React.js` and `Golang`. Both these languages require compilation. So designing a plugin system is a bit difficult.
1919

2020
## Goal & Features
2121
The goal of Answer's plugin system is to provide a **flexible** and **extendable** architecture that can accommodate a wide range of use cases. Some of the key features of the plugin system include:
2222

2323
### Connectors
24-
By default, Answer supports login via email and password. Withing the plugin system, developers can easily integrate other authentication, such as GitHub.
24+
By default, Answer supports login via email and password. Within the plugin system, developers can easily integrate other authentication, such as GitHub.
2525

2626
<img src={require('./answer-plugin-connector.png').default} alt="install-choose-language" width="400"/>
2727

2828
### Storage
29-
Out of the box, Answer stores files in the local file system. However, there could be scenarios where users might prefer to save their uploaded files to a cloud storage service like `S3`. This can be achieved by plugin system.
29+
Out of the box, Answer stores files in the local file system. However, there could be scenarios where users might prefer to save their uploaded files to a cloud storage service like `S3`. This can be achieved by the plugin system.
3030

3131
<img src={require('./answer-plugin-storage.png').default} alt="install-choose-language" width="400"/>
3232

@@ -58,18 +58,18 @@ Here are the reasons behind our design choices:
5858
> This is the main reason why the plugin system is designed this way.
5959
6060
`React.js` and `Golang` both these languages require compilation. They are not dynamically executable like some other scripting languages.
61-
So the plugin system should be static compilation, which means that the application and plugins are compiled together, resulting in a single binary that can be easily distributed and deployed.
61+
So the plugin system should be a static compilation, which means that the application and plugins are compiled together, resulting in a single binary that can be easily distributed and deployed.
6262

6363
#### Fixed Functionality
6464
The plugin system allows users to add features that are fixed for their specific use cases without changing the core system.
6565
Furthermore, these functionalities persistently remain operational once they are employed.
6666
Therefore, it is sufficient to deliberate on the necessities of their incorporation at the initial stage, and subsequently, package them accordingly.
67-
In the future, we can build a Docker image that contains all officially plugins, thereby enabling users to access the entire range of features. The enablement or disablement of these functionalities can be managed through the plugin control interface.
67+
In the future, we can build a Docker image that contains all official plugins, thereby enabling users to access the entire range of features. The enablement or disablement of these functionalities can be managed through the plugin control interface.
6868

6969
#### Extension
70-
The most important capability of a plugin system is actually its extensibility.
71-
It is impossible for a program to provide all the functions that every user wants.
72-
However, with a plugin system, users can develop their own plugins to help them achieve the functions that they want.
70+
The most important capability of a plugin system is its extensibility.
71+
A program can't provide all the functions that every user wants.
72+
However, with a plugin system, users can develop their plugins to help them achieve the functions that they want.
7373

7474
## Reference
7575
The Caddy is a great open-source software that inspired the design of the Answer plugin system.
@@ -78,6 +78,6 @@ Using [xcaddy](https://github.com/caddyserver/xcaddy/) can easy to make custom b
7878

7979
## More
8080
In this blog post, we discussed the design and implementation of the plugin system for Answer, a popular open-source Q&A platform.
81-
We discussed the motivation behind the design, the features and principles of the plugin system, and provided a step-by-step guide on implementation.
81+
We discussed the motivation behind the design, and the features and principles of the plugin system, and provided a step-by-step guide on implementation.
8282
If you are interested in developing plugins for Answer, please feel free to leave us a comment.
83-
We will also write an article on how to implement an Answer plugin from scratch, so stay focus!
83+
We will also write an article on how to implement an Answer plugin from scratch, so stay focused!

static/data/latest.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
{
22
"release": {
3-
"version": "1.5.0",
4-
"date": "2025-05-06",
5-
"url": "https://github.com/apache/answer/releases/tag/v1.5.0"
3+
"date": "2025-06-03",
4+
"version": "1.5.1",
5+
"url": "https://github.com/apache/answer/releases/tag/v1.5.1"
66
}
77
}

static/img/blog/[email protected]

4.79 KB
Loading

static/img/blog/[email protected]

22 KB
Loading

static/img/blog/[email protected]

3.89 KB
Loading

0 commit comments

Comments
 (0)