Git Product home page Git Product logo

marketplace's Introduction

Marketplace packages

A packages manager for Logseq marketplace plugins.

How to write a plugin for Logseq?

This repo contains sample code illustrating the Logseq Plugin API. You can read, play with or adapt from these samples to create your own plugins.

Plugin APIs: https://plugins-doc.logseq.com/.

⚠️ To avoid loading plugin failures occasionally and for performance reasons, it is recommended to keep the plugin SDK @logseq/libs as up-to-date as possible.

Ensure that your plugin has a publish.yml file, so when you create a release from a tag, it will do the build dance and make you a zip file. Then make a tag (something like v0.0.1), and create a release from it. Ensure the following are true before submitting your plugin:

  • The release has a zip file attached in addition to the "Source code (zip)" link. (It might take a minute for build system to create the zip after creating the release.)
  • It's clear from your README what the plugin does, and how to use it.
  • It has at least one image or gif showing it in action.

How to submit your plugin?

  1. Fork this repo to your Github account.
  2. Create a package directory under ./packages root based on your plugin name.
  3. Write a manifest.json file to the package root. Valid fields as follows:
    • title- A title for plugin list item display.
    • description- A short description about your plugin.
    • author- The author's name.
    • repo- The GitHub repository identifier, like {user}/{repo}.
    • icon- [optional] A logo for better recognition. default: ""
    • theme- [optional] A theme plugin? default: false
    • sponsors - [optional] Sponsor external links. default: []
    • effect - [optional] Whether the sandbox is running under the same origin with host. default: false

      ⚠️ effect? - it's not recommended to turn on this option if you don't need a specific feature (the current built-in plugin API does not satisfy), which may affect the stability of the program. If it does need to be turned on, the market review process will be more strict, while there is no guarantee that it will not be allowed to be turned on in the future.

  4. Make a Github Pull Request :)

How to update plugins' stat?

Note: This step is optional!

To update the plugins' stat, you need run scripts/build.mjs script with a valid GitHub access token. Assuming you have a token, take the following steps:

yarn install
cd scripts
LSP_MK_TOKEN=YOUR_TOKEN ./build.mjs --stat

Ensure only stats.json file is updated. If errors.json is changed, rerun the steps to ensure no plugin is missed.

marketplace's People

Contributors

adxsoft avatar ahangarha avatar ahonn avatar b-yp avatar benjaffe avatar benjypng avatar candideu avatar cannibalox avatar debanjandhar12 avatar duydl avatar freder avatar haydenull avatar isosphere avatar natsustan avatar pengx17 avatar phildenhoff avatar qwxlea avatar rcvd avatar renatocaliari avatar sawhney17 avatar sethfair avatar sethyuan avatar stdword avatar tankcool avatar usoonees avatar vipzhicheng avatar xyhp915 avatar yoyurec avatar yu000jp avatar zyrohex avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

marketplace's Issues

How a theme update reaches the marketplace?

Hello :)
I updated my theme, but I'm not sure how to proceed.
What would be the necessary steps to the update gets into the marketplace?
I hope that question is not too dumb 😅

Sending love and blessings 🙏

Filter plugins by license

I am only interested in installing plugins with Free Software licenses. Ideally there would be a facets for licenses, but even a filter would be a major upgrade. There are a big handful of plugins, and I think this would make the marketplace a little bit better for privacy focused people like myself who use licensing as a qualitative indicator of whether or not the relationship with the developers is going to work for me.

Tasks

No tasks being tracked yet.

Installation issues with the latest logseq release

With the latest releases, users are encountering.

[Error]<logseq-allday-theme> :release-channel-issue "Github API Failed(404) {\"message\":\"Not Found\",\"documentation_url\":\"https://docs.github.com/rest/reference/repos#get-the-latest-release\"}"]

I tried to investigate but couldn't find an issue on my side. Since nothing changed and other themes or plugins that hold the same pattern continue to work, I assume it must be an upstream issue. is there anything I can do on my side?

Related: ttytm/logseq-allday-theme#19

Plugin still shipping with effect: false

Hello sorry for the inconvenience, but when I first submitted my plugin in #476 I forgot to add effect: true and I did with #477, but the plugin still ships with effect: false in package.json and setting it manually fixes the cors error. So does it take a while to re-update the system with effect: true or do I need to resubmit the plugin. again sorry for the inconvenience it's my first time developing a plugin 😅

[enhancement] use a popularity metric instead of total number of downloads

[WIP]
image

The total number of downloads metric does not really provide useful information to the user at this point. Many plugins that have existed for a long period of time have numerous downloads and stars. This does not mean that the plugin is a high quality plugin or if it's still being actively used by logseq users.

Its best to implement a popularity metric based on how many times the package was downloaded or by number of votes.

Fro example; Popularity can be calculated as the sum of all votes with each vote being weighted with a factor of 0.98 per day since its creation

The idea is still work in progress; this issue is for tracking and discussion purposes

install logseq-drawio-plugin with error

when installing logseq-drawio-plugin occur same error on windows at logseq 0.9.6. I install other plugin without this error.
maybe it is too large(20M+)?
I install logseq using scoop.
image

Process for deprecating a plugin?

I wrote a plugin and, later, an improved alternative for it which works differently. I do not wish to support the former. Is this just a pull request which deletes my previously added plugin?

I wasn't sure how doing this would affect the user experience. Does my deleting a plugin cause it to be automatically uninstalled from user systems?

emacs client

I am having some problems opening embedded org files in emacs client. Logseq seems to want to open emacs launching my .emacs file every time (which takes a while in my case). Any suggestions??

Enabling plugins without html is broken

It cannot create entry upon plugin import. The error is

instrument.js:112 [Load Plugin Error]  Error: Not existed method #write_dotdir_file

Looks like it tries to add index.html from built-in template anyways, but fails to write it to file system.

workflow: add a github action to auto build plugins.json

Developers make pr changing their own package directory, but usually they don't run script.

Can we introduce Github action to refine this workflow? Because any changes to the package director will not work until the script get executed.

Update repository url of `logseq-plugin-automatic-url-title` plugin

The original repo is unmaintanined and it's buggy: https://github.com/0x7b1/logseq-plugin-automatic-url-title

This fork fixes the bugs, I think the url should be updated: https://github.com/abtris/logseq-plugin-automatic-url-title

Please, I'm tired of this bug and don't know how to add custom github repos =(
image

I don't think it's a good idea to send buggy plugins to users, specially when there is a patch around.

I didn't sent PR because I'm not sure if the author should be updated also.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.