Port to Pelican about freshrss.org HOT 8 CLOSED

BTW, a new repository will have to be created to store Pelican theme and configuration.

from freshrss.org.

Here is the result of my work for now: http://dev.freshrss.org/. It is identical (with some minor changes) but generated by Pelican :)

from freshrss.org.

Question

For the moment I planned to host only freshrss.org content (i.e. before generation by Pelican). Should we:

• have a separated repository to host Pelican theme + instructions to build website?
• have a separated repository to host Pelican theme and put instructions in the current one (i.e. in the README)
• have a separated branch on this repository to host theme and instructions (or instructions in the README of the master branch) ?

Since theme is really specific to freshrss.org, a new branch seems ok to me. But a separated repository could improve reusability. I don't have any preference.

Any thought?

from freshrss.org.

I will go for 2 distinct repositories keeping in mind the HTML/CSS or Latex way of separating the content from the layout. My 2 cents.

from freshrss.org.

Having two distinct branches is also separating content from layout :p

from freshrss.org.

That's true.

from freshrss.org.

After some thoughts, I think I will create a new repository for the theme and instructions to install freshrss.org will be in the README of the current repository ;)

from freshrss.org.

README.md is up to date in my fork and theme is available at github.com/FreshRSS/Freshican.

The only line to adapt (until my PR is not merged) in the README is:

$ git clone [email protected]:FreshRSS/freshrss.org.git content
# to
$ git clone [email protected]:marienfressinaud/freshrss.org.git -b 11-port_to_pelican content

from freshrss.org.