papyrs / papyrs Goto Github PK

View Code? Open in Web Editor NEW

75.0 2.0 8.0 1.47 MB

Blog on web3

Home Page: https://app.papy.rs

License: Other

JavaScript 2.80% HTML 1.29% Svelte 44.44% TypeScript 51.34% SCSS 0.14%

articles blockchain blog blogging-platform dapp internetcomputer journalism smart-contracts sveltekit web3

papyrs's Introduction

Papyrs - Blog on web3

⚠️ Deprecated

Papyrs is still available for use, but new user sign-ups have been disabled. The platform is no longer being actively developed or maintained.

Papyrs

Papyrs is an open-source, privacy-first, decentralized blogging platform that lives 100% on chain. Papyrs runs on the Internet Computer, the world's first blockchain that runs at web speed and serves content on the web.

Links & Projects

Here are some useful links:

See the HACKING document to run locally the app or fetch published blog posts.
Reach out to us on Discord.
Wanna help? Check out the CONTRIBUTING guidelines.
Have a look at the LICENSE for information about licensing and limitation.

This repo is the web editor of Papyrs. It can be used as a standalone app but uses other projects we are developing to be fully deployed:

IC: canisters and sign-in providers
CDN: libraries and assets we are using across the platform
Unsplash-proxy: a proxy we have to use to query Unsplash
Stylo: another kind of rich text editor
Kit: the templates for the blog posts we deploy for the users
DeckDeckGo: various web components, utilities and the providers for the offline persistence and synchronization of the data

Other handy tools:

Papyrs to markdown: Chrome markdown-plugin that can be used to convert a blog post to markdown

Architecture overview

All programs on the Internet Computer are Wasm modules, or canisters (canister smart contracts). The Papyrs web editor is deployed on the IC through Fleek.

The web editor persists blog post data in the browser in indexedDB. This means that Papyrs can be used by anyone without any authentication. Blog posts can be loaded from and exported to the file system.

However, if users are interested in storing their data "in the cloud" automatically and sharing their blog posts online, authentication with Internet Identity will be required. Once authenticated each user gets two canisters:

a private "data" canister that contains raw blog post data, used in the editor, and
a "storage" canister that holds and publicly serves blog post and asset data (html, images, js, css, etc).

papyrs's People

Contributors

Stargazers

Watchers

Forkers

hokentech mrnmkmn neutronstarpro bytesun atanggeblog omahs haliacmon tuminfei

papyrs's Issues

nested list is breaking the editor UI

Expected Behavior

Nested list should have some limits in my opinion. If not, it should at least not break the editor UI.

Actual Behavior

Nested list does not have any limit and that is also causing UI issues in the editor.

Reproduction

Steps to reproduce:

Keep nesting the list in the editor

Screenshots

sr-2022-07-29_13.52.34.mp4

Environment

Browser(s): Chrome (Latest version)
Operating System (e.g. Windows, macOS, Ubuntu): Pop!_OS 22.04

fix: text link overflow (again)

To be fix in the github.com/papyrs/kit/

e.g. https://7ryfn-6qaaa-aaaal-abcca-cai.raw.ic0.app/d/prtrts-analysis

how do i delete an image

Expected Behavior

i expected to be able to delete an image

Actual Behavior

i have no idea how to actually delete an image

Reproduction

Steps to reproduce:

start a post
add image
try to delete it -- now way to select it or backspace through it

Environment

Browser(s):
Operating System (e.g. Windows, macOS, Ubuntu):
OS X / Chrome

fix: social image not rendered if uploaded to Papyrs

Actual Behavior

Twitter cannot render the social image if the image if uploaded to Papy. This is because crawlers are blocked and should not crawl the images folder because the images can be private.

e.g.

https://twitter.com/showying_art/status/1564126822199345154

https://jiypc-raaaa-aaaal-abb3a-cai.raw.ic0.app/d/c3f-japanese-ic-community

https://jiypc-raaaa-aaaal-abb3a-cai.raw.ic0.app/robots.txt

Disallow: /images/

Solution

simple: do not use Papy images for og meta tag but only the auto generated images
complicated: update robots.txt with list of images that can be crawler

Screenshots

feat: keep track of code options

Feature Description

It would be nice to keep track of code options - e.g. if I add a piece of code to an article and then set "c# and no line numbers", next time I add another piece of code, it should inherits the same settings until I change then again. It can make easier to write a blog post that is not about javascript.

We can probably handle the last code settings in session storage or local storage.

feat: better chinese support

Feature Description

Since many of them write in Chinese, it would be great if they could write from top to bottom (and, ideally, right to left).

feat: publish twitter etc. to kit

Feature Description

User social handles such as twitter, linkedin etc. are not published to the main index.html of the users' assets canister.

In addition to name, photo and description, it would be cool to add these social links too.

Note

All information are optional.

LaTeX formula input

Feature Description

Recently GitHub added support for LaTeX in markdown. It would be nice to see such a thing in papyrs too.

Use Case

If one wants beautifully typeset formulas in a blog article, inline or block LaTeX syntax gives the most bang for the buck.

build: cannot read directory "..": operation not permitted

Actual Behavior

Not stricto sensu a Papyrs issue but using sveltekit - vitejs in a macOS sandbox leads to an issue Cannot read directory "..": operation not permitted.

An issue in vitejs repo was reported 👉 vitejs/vite#7956

link overflow on iOS

Expected Behavior

No overflow, use the css luke:

overflow-wrap: break-word;
  word-wrap: break-word;

Actual Behavior

Link can lead to overflow on iOS

Reproduction

Steps to reproduce:

Go to https://hxev7-aiaaa-aaaal-aaona-cai.raw.ic0.app/d/do-daos-do on iOS

Screenshots

feat: delete action hidden - display message

Feature Description

Not displaying the "delete post" action on the posts page does not make obvious the action is not present because the current edited post cannot be deleted (that's given).

Instead of hiding the action, it should be displayed but display an information when clicked "sorry this post cannot be deleted, it is currently edited" (something like that).

Screenshot - Mockup

editing existing code with < and >

Bug Description

code editor is a little bit buggy - if you put an ampersand (&) into it, save and then try to edit the entry, it will replace the ampersand with & which is incorrect; and, actually, it doesn’t always highlight the syntax as it should - for example, JSON highlighting wasn’t working for me;

feat: language as publish metadata

Feature Description

When user publish / share a new article, he/she should be able to select the language (iso code, en etc.) of the article.

This language should then be applied to the metadata of the published post <html lang="LANG"/>

fix: prevent data overwrite

Feature Description

When user sign in, the document available locally - if it contains any changes - will be sync with the cloud.
If user has the document loaded on multiple devices, there is a chance that data are going to be overwritten.

Likewise, if use edit a post on multiple devices at the same time, data can be overwritten has there are no checks - currently - that the modified data is actually the current one.

That's why the store - the smart contract -should check updated_at dates before doing any updates - i.e. put and delete.

This has to be implemented in the Motoko code of the providers (https://github.com/papyrs/ic).

The dapp should be updated accordingly and should display only one - "cannot sync, maybe reload the document from the posts page..." in case of error.

Japanese writing not working well

Expected Behavior

Bug Behavior

Japanese text written on the title or body goes to next line and is duplicated because the enter key is pushed twice when Japanese is typed.

Reproduction

Steps to reproduce:

Write in Japanese
You can see duplicated text at the next line.

Video about the bug

Gif

Environment

Browser(s): Google Chrome
Operating System: macOS

Style spacing in list

Feature Description

Give a bit of spacing (maring) in ul li

e.g. https://bqz7y-oyaaa-aaaal-aa5sq-cai.raw.ic0.app/d/secure-access-to-the-ic

feat: sitemap & rss feed for blogs

Feature Description

It would be cool to have a rss feed per blog and of course to update the feed each time a new article is published

Auto-generated social card image font size

Feature Description

The auto-generated social image font size does not seems to always be correct, should be fixed.

See https://twitter.com/PapyrsApp/status/1552195309937332225

style: dark mode

Feature Description

I can probably look at following example of Webstorm to develop a dark mode.

Question is: should the dark mode be "just" another theme or a base on which current theme/colors can be applied?

Examples

https://github.com/nashamri/spacemacs-theme

https://github.com/nashamri/spacemacs-theme/blob/1ec73d68b0f120f92538d9a329a3a46e32f74510/spacemacs-common.el#L100

feat: display message about updating published content

Feature Description

It isn't clear for user that once published, every modifications should be re-published / updated too. Therefore Papy can maybe display a message "Your last modifications have not yet been sync" or something?

https://twitter.com/showying_art/status/1564144793097478144

if (doc.meta.published_at < paragraphs.updated_at most recent date) => display info

feat: access to plugins ("+") when selecting code blocks

Feature Description

When selecting / clicking on code blocks, there is no "+" displayed to access the plugin and add a new paragraphs after the element

Screenshot

fix: update index.html of blog on delete if post is published

docs: add markdown plugin to README

Feature Description

We've got a cool Chrome markdown-plugin (repo - web store) that can be use to convert a blog post to markdown but it isn't yet referenced in this README. Would probably be nice to mention it.

feat: "back" action to root if page is accessed directly through its url

Feature Description

The back button in Nav.svelte fallback to history.back() which isn't accurate if a page is accessed directly - e.g. accessig http://localhost:3000/posts through the url of the browser.

We should either fix the "back" action to root to home when there is no history or maybe even display a home button (?) instead.

papyrs / papyrs Goto Github PK

papyrs's Introduction

Papyrs - Blog on web3

⚠️ Deprecated

Papyrs

Links & Projects

Architecture overview

papyrs's People

Contributors

Stargazers

Watchers

Forkers

papyrs's Issues

Expected Behavior

Actual Behavior

Reproduction

Screenshots

Environment

Expected Behavior

Actual Behavior

Reproduction

Environment

Actual Behavior

Solution

Screenshots

Feature Description

Feature Description

Feature Description

Note

Feature Description

Use Case

Actual Behavior

Expected Behavior

Actual Behavior

Reproduction

Screenshots

Feature Description

Screenshot - Mockup

Bug Description

Feature Description

Feature Description

Expected Behavior

Bug Behavior

Reproduction

Video about the bug

Environment

Feature Description

Feature Description

Feature Description

Feature Description

Examples

Feature Description

Feature Description

Screenshot

Feature Description

Feature Description

Screenshot

Recommend Projects

Recommend Topics

Recommend Org