Add a new default theme which is responsive and widely reusable

[naturallymitchell]

In this issue I would like to solve:

• 668 (A mobile aware theme) where there is interest in adding a theme that works across display sizes, aka responsive.

• 516 (theme notmyidea should use the simple theme) where there is agreement that Pelican's default theme(s) should reuse its own inheritable features.

• The visions of justmay - August 6th 2013 and kylef - 7 months ago for a new theme in core that other themes can reuse.

This issue builds on #1092 (Inherit from arbitrary theme) which makes !simple's inheritance functionality available to themes such as this one.

I don't have a PR yet, but here's the code:

• base theme - a highly organized, highly reusable starter theme which makes great use of Jinja's blocks functionality
• fixed_sidebar theme - a common blog pattern
• top_welcomebar theme - a basic Ghost theme
• corkboard theme - a template targeted for collaboration sites

These three examples demonstrate the base theme, and while not absolutely necessary, I believe that these three example themes, or some other ones, would be very useful for demonstrating the foundation code and driving adoption. Not just that.. Having more options out-of-the-box would improve usability, where users can choose how they'd like to begin using Pelican. Also, it would increase the diversity of looks-n-feels of Pelican.

I'm not an HTML/CSS expert, so before these themes are ready, they will need some care.

[jsonbecker]

Would it be better to submit these themes in pelican-themes and then when they are looking good to go request these be used as defaults?

[naturallymitchell]

@jasonpbecker, I'll happily meet you half way at https://github.com/getpelican/pelican/issues/1488. Please voice support there if you agree.

[leotrs]

What happened to those themes? Themes already live in a different repo.

[leotrs]

@jsonbecker @mitchtbaum ^

[justinmayer]

I would like to choose a Pelican theme as a test case for community-maintained themes, much like we have done under the Pelican Plugins organizational banner.

@DragonSerw mentioned Papyrus, which could be a potential starting point.

@aleylara: Would you be open to relocating the Papyrus theme under the https://github.com/pelican-themes organization so the broader Pelican community can collaborate on it and enhance it further? As the original author, you would of course continue to have full commit permissions in the new repository, and if interested, you could continue to guide the theme's development there. What do you think?

[aleylara]

Hi @justinmayer

That would be fine. Let me know how you want to proceed.

[justinmayer]

That's wonderful, @aleylara. Would you please follow these transfer instructions? In step four, select Specify an organization or username and then enter pelican-themes as the organization name.

Would you please let me know once that has been completed? Then I can take the next steps and ensure you have full permissions there. ✨

[aleylara]

Hi @justinmayer , It's done up until step 4.

[justinmayer]

I'm sorry — I probably wasn't clear enough. Once you select Specify an organization or username and then enter pelican-themes as the organization name in step four, please then continue with steps five and six to complete the process. 😊

[pauloxnet]

I proposed a different approach in #3233 with a similar goal