KitaitiMakoto
KitaitiMakoto pushed to fix-translations at plume/documentation 2020-12-20 12:47:46 +00:00
d6d2215465 Fix translation file path
e822296002 Add deploy tasks
e5dee1e72e Reset build tasks
KitaitiMakoto deleted branch url-link from plume/documentation 2020-12-20 10:17:48 +00:00
KitaitiMakoto merged pull request plume/documentation#110 2020-12-20 10:17:41 +00:00
Make URI a link
KitaitiMakoto merged pull request plume/documentation#110 2020-12-20 10:17:37 +00:00
Make URI a link
KitaitiMakoto pushed to main at plume/documentation 2020-12-20 10:17:37 +00:00
9ab9ae743a Merge pull request 'Make URI a link' (#110) from url-link into main
5c0a595e5a Make URI a link
Compare 2 commits »
KitaitiMakoto created pull request plume/documentation#110 2020-12-20 10:17:26 +00:00
Make URI a link
KitaitiMakoto pushed to url-link at plume/documentation 2020-12-20 10:15:59 +00:00
5c0a595e5a Make URI a link
KitaitiMakoto commented on issue Plume/Plume#850 2020-12-20 08:05:53 +00:00
XMLHttpRequest for boost and likes

Development Guide also help you.

KitaitiMakoto commented on issue Plume/Plume#850 2020-12-20 07:11:31 +00:00
XMLHttpRequest for boost and likes

That sounds nice feature.

Plume's frontend development is a little complex.

  • HTML (Ructe template) files are present under templates directory
  • CSS (SCSS) files are included in themes. You can see about theme development at Creating a theme page
  • Sources of JavaScript (WASM) file are present under plume-front/src

Files of these types are compiled at Rust's compile time in build.rs.

Additionally, you might have to develop API endpoints for boost and like. That will be achieved mostly in src/routes directory.

Now Plume has API endpoints at /api/v1 URI. But they requires OAuth authentication to access and you will not prefer it.

  • You might send a request via XMLHttpRequest (or fetch) to /~/{BlogName}/{article-slug}/like, parse HTML in response and check if it succeeded or faild. Or,
  • You can add API endpoint for this purpose.

Is this enough information? Feel free to ask anything.

KitaitiMakoto closed issue plume/documentation#109 2020-12-19 14:50:10 +00:00
XMLHttpRequest for boost and likes
KitaitiMakoto commented on issue plume/documentation#109 2020-12-19 14:49:53 +00:00
XMLHttpRequest for boost and likes

@freyja_wildes Thank you for proposal. Could you re-create an issue at application repo because this is not about documentation issue but application feature.

KitaitiMakoto commented on issue Plume/Plume#845 2020-12-19 11:26:31 +00:00
Release v0.6.0

I pushed to release-0.6.0 branch manually.

KitaitiMakoto pushed tag 0.6.0 to Plume/Plume 2020-12-19 11:26:07 +00:00
KitaitiMakoto deleted branch release-0.6.0 from Plume/Plume 2020-12-19 11:25:46 +00:00
KitaitiMakoto merged pull request Plume/Plume#849 2020-12-19 11:25:06 +00:00
Release 0.6.0
KitaitiMakoto pushed to main at Plume/Plume 2020-12-19 11:25:00 +00:00
2a5a2ec4d2 (cargo-release) start next development iteration {{next_version}}
106e9417d3 (cargo-release) version {{version}}
2660efec16 Define tag-name for cargo-release
1eaa5a6e31 Add pre-release-hook to release.toml of subcrates to prevent running
b2c26f03e8 Pull master branch from Crowdin
Compare 12 commits »
KitaitiMakoto created pull request Plume/Plume#849 2020-12-19 11:24:30 +00:00
Release 0.6.0
KitaitiMakoto pushed to release-0.6.0 at Plume/Plume 2020-12-19 11:22:08 +00:00
46cdde8687 (cargo-release) start next development iteration {{next_version}}
6b0dfb729c (cargo-release) version {{version}}
75a4d1abf1 Define tag-name for cargo-release
984c0cda6b Add pre-release-hook to release.toml of subcrates to prevent running
902612a470 Pull master branch from Crowdin
KitaitiMakoto commented on issue Plume/Plume#845 2020-12-19 10:59:09 +00:00
Release v0.6.0

cargo-release pushes to main but Gite main branch is protected from pushing...

KitaitiMakoto commented on issue Plume/Plume#845 2020-12-19 10:26:12 +00:00
Release v0.6.0

I found crowdin pull is included in cargo-release's pre-release-hook.