Skip to content
This repository has been archived by the owner on Sep 16, 2019. It is now read-only.

Feature request: Make it possible to import new themes #5

Closed
ghost opened this issue Jul 12, 2016 · 17 comments
Closed

Feature request: Make it possible to import new themes #5

ghost opened this issue Jul 12, 2016 · 17 comments
Labels
enhancement Supports in Marp Next The tagged issue has/would resolved in repos on @marp-team, and might close in near future.

Comments

@ghost
Copy link

ghost commented Jul 12, 2016

At the moment this requires rebuilding the app. It would be great if I could make a theme for my university and upload it somewhere and people could just download and import it.

@abunsen
Copy link
Contributor

abunsen commented Jul 13, 2016

👍

@tobloef
Copy link

tobloef commented Jul 13, 2016

Definitely looking forward to this feature 👍

@adamprocter
Copy link

Perhaps take a look at the way Ulysses app has created a theme system for export.

@metbril
Copy link

metbril commented Aug 17, 2016

I would prefer being able to add a reference to a .css file (that I can put next to the .md file and any image file). Let's keep things simple.

(see #1)

@dialex
Copy link

dialex commented Oct 10, 2016

I want this so badly!! It would absolutely destroy Deckset.

@pascaliske
Copy link

👍🏻

@NicolasWebDev
Copy link

Indeed, a much needed feature.
I support the css file reference, to make things simple.

@Svenito
Copy link

Svenito commented Apr 20, 2017

👍 for this too. Pluggable themes would be great. Or simply allowing users to include a custom css alongside their project

@flashpixx
Copy link

This is a very useful feature, my proposal is a user-definied directory e.g. under Linux ~/.marp/theme and under OSX ~/Library/Application Support/Marp/theme. The theme (CSS file) can be stored under this directory and Marp appends the current (default) list with these themes from this directory

@robsalasco
Copy link

+1

2 similar comments
@brunitto
Copy link

+1

@kode7
Copy link

kode7 commented Nov 20, 2017

+1

@kelein
Copy link

kelein commented Apr 10, 2018

I'm looking forward for more colourful theme of Marp. 😺

@rakshazi
Copy link

Hello!
Any update on this?
It's really must-have feature. In our company all presentations must be with company's template (color, fonts, images, etc). So we can't use Marp without additional actions (I mean, we build it with our custom theme every time)

@fredtempez
Copy link

Hi,
just import some CSS in your markdown and voila.

@yhatt yhatt added the Supports in Marp Next The tagged issue has/would resolved in repos on @marp-team, and might close in near future. label Sep 15, 2018
@yhatt
Copy link
Owner

yhatt commented Sep 20, 2018

I'm sorry to have kept you waiting. In order to support much better custom themes, we are develpoing the next-gen Marp tools for a long time.

Today, we have released a CLI interface of the next-gen Marp, that has supported importing the custom theme CSS based on our new Marpit framework. It is still an early-alpha release, but you can try to create custom theme for new Marp with with live-previewing.

If you have installed Node, you can try the command like this:

npx @marp-team/marp-cli --theme your-theme.css --watch slide.md

Please refer to the documentation of Marpit to learn how to create theme. Marpit has the CSS theming system that can design slides with clean markup.

In future, the planned GUI interfaces at the next-gen Marp, like online version (marp-web) and Desktop version (marp-electron), would become to support custom theme. You can create your custom theme in CLI until these are ready. (coming soon)

@yhatt
Copy link
Owner

yhatt commented Jul 14, 2019

We close this issue because theme CSS support for Marp Next tools (based on Marpit framework) is getting stable (#267).

@yhatt yhatt closed this as completed Jul 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Supports in Marp Next The tagged issue has/would resolved in repos on @marp-team, and might close in near future.
Projects
None yet
Development

No branches or pull requests