Pleroma frontend
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Dee ee2cd61cfd Merge branch 'develop' into underscore-world 1 week ago
build fix rgba css generation, add some tests to automatically verify that themes are 4 months ago
config Use target from the settings 10 months ago
docs Config setting is actually called disableChat 2 weeks ago
src Merge branch 'develop' into underscore-world 1 week ago
static Add missing settings: disableChat, greentext, hideFilteredStatuses, hideMutedPosts, hidePostStats, hideSitename 2 weeks ago
test add back mute prediction, add getter for relationships 1 month ago
.babelrc fix babelrc plugin config 5 months ago
.editorconfig Basic skeleton 3 years ago
.eslintignore Basic skeleton 3 years ago
.eslintrc.js all the manual fixes 10 months ago
.gitignore whoopsies 1 year ago
.gitlab-ci.yml use yarn, try to restart pipeline 6 months ago
.node-version Add .node-version 3 years ago fixup! Removed formattingOptionsEnabled in favor of relying on BE-provided list of accepted formatting options 11 months ago update changelog 2 weeks ago Update 3 years ago maybe i should actually add myself to contributors list? 1 year ago
LICENSE Add license 3 years ago final touches 1 year ago
index.html versioning the font resources through webpack 5 months ago
package.json Fix/popover performance 2 months ago
postcss.config.js revives autoprefixer which went AWOL during Webpack v1 -> v4 migration 9 months ago
yarn.lock Fix/popover performance 2 months ago


A single column frontend for both Pleroma and GS servers.


For Translators

To translate Pleroma-FE, add your language to src/i18n/messages.js. Pleroma-FE will set your language by your browser locale, but you can temporarily force it in the code by changing the locale in main.js.


You don't need to build Pleroma-FE yourself. Those using the Pleroma backend will be able to use it out of the box. For the GNU social backend, check out to see how to run Pleroma-FE and Qvitter at the same time.

Build Setup

# install dependencies
npm install -g yarn

# serve with hot reload at localhost:8080
npm run dev

# build for production with minification
npm run build

# run unit tests
npm run unit

For Contributors:

You can create file /config/local.json (see example) to enable some convenience dev options:

  • target: makes local dev server redirect to some existing instance's BE instead of local BE, useful for testing things in near-production environment and searching for real-life use-cases.
  • staticConfigPreference: makes FE's /static/config.json take preference of BE-served /api/statusnet/config.json. Only works in dev mode.

FE Build process also leaves current commit hash in global variable ___pleromafe_commit_hash so that you can easily see which pleroma-fe commit instance is running, also helps pinpointing which commit was used when FE was bundled into BE.


Edit config.json for configuration.


Login methods

loginMethod can be set to either password (the default) or token, which will use the full oauth redirection flow, which is useful for SSO situations.