Hi,
Le mardi, mars 3, 2020 1:16 PM, Dag a écrit :
> Great work!
>
> old-components are propably ok, although we have not actually axed flow and
> braindump yet. They will however, go on next release, if somebody does not
> step up to maintain them.
>
> So, probably we should consider a new release soonish...
Considering how long, there wasn't any Calligra release this is a good idea. I
create a phab task for that https://phabricator.kde.org/T12787. Please feel
free to add any other subtasks. The promo team and I can help with writting the
announcement and promoting it to the social medias.
> As for web site access, probably a couple of more maintainers would like
> access, but I'm sure they can speak up for themselves :)
I will wait a few more days before creating a sysadmin request, otherwise
access can still be granted later with a normal sysadmin request.
Cheers,
Carl
> ---
>
> Cheers,
>
> Dag
>
> Carl Schwan skrev den 2020-03-02 16:42:
>
> > Hello,
> > the website progressed a lot during Season of KDE and it was completly
> > updated. Thanks a lot to Anuj Bansal for his work on that and in improving
> > the Jekyll theme with new components.
> >
> > It now use the Jekyll KDE theme, the screenshots are all updated with the
> > latest version of Calligra and use the Breeze theme. A demo version is
> > available at https://irl.carlschwan.eu/. It would be nice, if someone could
> > take a look at it and reports any errors or problems found. Particulary if
> > the information present on https://irl.carlschwan.eu/old-components/ are
> > correct.
> >
> > The website git repository is located at
> > invent.kde.org/anujbansal/calligra-website/ and will be moved to
> > invent.kde.org/websites/calligra-org in the future, after the review.
> >
> > For the sysadmin request and the deployment, I will need to know who need
> > to access the website. From reading the logs, I think it should be at least
> > Jarosław Staniek and danders, but if anyone else want access please let me
> > know. Just make sure you have an account in invent.kde.org (just login with
> > your identity.kde.org identifier one time), otherwise Sysadmin can't grant
> > you access :-).
> >
> > I hope not many problems will be found. My plan will be to deploy the
> > website before the end of this month, so that it can appear on my second
> > monthly KDE web news :-)
> >
> > Cheers,
> >
> > Carl Schwan
> > https://carlschwan.eu
> > KDE Web developer
> >
> > ‐‐‐ Original Message ‐‐‐
> > Le mardi, janvier 7, 2020 9:53 PM, Carl Schwan a écrit
> > :
> >
> > > Hi,
> >
> > > I already spoke a bit about it with Leinir, but I will mentor a Season of
> > > KDE project about updating the Calligra website. The idea of updating the
> > > Calligra website was really popular and I received more than 10 proposals
> > > for the website. I choose Anuj Bansal since he already contributed to the
> > > juk.kde.org website and he is familiar with the current KDE web tooling.
> >
> > > The goal of the new website is to bring new users and new contributors to
> > > Calligra.
> >
> > > The website update will be focused around the content, the design, and
> > > the infrastructure.
> >
> > > - Content:
> > > - the screenshots need to be updated to use the Breeze theme
> > > - the text need be checked to see if it is still actual
> > > - Url should remain the same for compatibility with the old links
> > > - Old content needs to be ported. We should not lose any
> > > announcements
> > > - The planet feature is easy to reproduce using the Jekyll planet
> > > component.
> > > - Add get-involved page with links to developer information and
> > > other useful information to start hacking on Calligra ;)
> > > - Design:
> > > - The updated website will use the Aether theme. This is the theme
> > > used for kde.org and was designed for KDE.
> > > - Potentially we could use some small variation from the main theme
> > > to make the website more unique.
> > > - A good example about how the website could look in the future is
> > > kontact.kde.org
> > > - New design will be also compatible with mobile phone.
> > > - Infrastructure:
> > > - The new website will use Jekyll a static site generator (the CI
> > > build the website and the server only serve plain html content). This
> > > means the website will be faster to load for the visitor and more secure.
> > > - All the content is stored in git as markdown files and this makes
> > > it easier to contribute to the website (we can use gitlab as CMS)
> > >
> >
> > > As the first step for Anuj, I think the best would be to set up a
> > > repository in invent.kde.org and create the base structure with a lot of
> > > boilerplate content (copied from the existing website) and the basic
> > > Jekyll configuration. When we can iterate over the con
