Re: Future of the dot

Looking nice but switching between content management systems is always a
tricky process.

Are the URLs intended to be compatible?  This story is different for example
/2020/02/12/videos-from-kde-talks-at-fosdem/
/2020/02/12/videos-kde-talks-fosdem

Looking at https://irl.carlschwan.eu/2020/01/16/plasma-518-lts-beta/ I see
obvious formatting problems.  We can choose to just accept those and move
on if we want.

This loses all the old comments and the ability to comment.  Comments have
become much less used in recent years because logging in is now more faffy
and there's other places to have those discussions.  So we can decide that
none of the old comments are useful enough to keep and no more new
comments.  It would however be nice to link to a place such as a post on
Reddit where people can discuss the item, I'm not sure if there's an easy
way to do that.

Jonathan



On Thu, 2 Apr 2020 at 13:10, Carl Schwan <[email protected]> wrote:

> Hello everyone,
>
> the current dot.kde.org website is still using the old web design and an
> old version of the Drupal CMS. I have been working on an updated version of
> the dot using Hugo instead.
>
> The updated dot as the following advantage, it uses the current theme used
> in other websites, it is faster to load, is more secure and need less
> maintenance.
>
> A current demo is available here: https://irl.carlschwan.eu/.
>
> This will require some change in our editing workflow for a new article
> since the content is now stored in git and Gitlab. There is two different
> way how we could draft article without making then public on the web.
>
> * Using the GitLab workflow for stuff that are not sensitive. This means
> to create a new issue for each new dot article, click on the "create merge
> request" button and then open the web IDE to get a powerful text editor and
> merging when we want to publish. This won't make the text draft invisible
> to all since people can still see all the open merge requests if they want.
> But for stuff that we discuss in the Promo channel and are technically
> visible for all, this won't change anything.
>
> * For stuff that really needs to be invisible until the announcement (e.g.
> big donations, collaboration announcements), the best way would be to
> create a shared document on share.kde.org and share it with the people
> who should see it only and then copy it in Gitlab when this should be
> visible.
>
> This is a bit more complex but allows for some interesting improvement in
> our workflow. For example, we get issue tracking for each article we want
> to post with time tracking. This allows also people who are not dot editor
> to submit an article for review. And we get the powerful code review
> features from GitLab for the articles (adding comments and suggesting
> changes). The editing will also be done in markdown, this should be easier
> than editing HTML like in the current interface (HTML is also supported).
>
> For those, we dot editor access, please log at least one time in
> invent.kde.org with your identity credential, so that an invent account
> is created and that sysadmin can grant you access to the repository.
>
> Cheers,
> Carl