[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    [websites/digikam-org/dev] content/about/meta: Add to /meta/writing.md
From:       Pat David <null () kde ! org>
Date:       2017-04-01 3:14:42
Message-ID: E1cu9Uw-0004Hj-9K () code ! kde ! org
[Download RAW message or body]

Git commit 45be6765ff87cbea5169107d3f3dfd5219305245 by Pat David.
Committed on 01/04/2017 at 03:14.
Pushed by patdavid into branch 'dev'.

Add to /meta/writing.md

M  +33   -1    content/about/meta/writing.md

https://commits.kde.org/websites/digikam-org/45be6765ff87cbea5169107d3f3dfd=
5219305245

diff --git a/content/about/meta/writing.md b/content/about/meta/writing.md
index 911034c..8477fbe 100644
--- a/content/about/meta/writing.md
+++ b/content/about/meta/writing.md
@@ -5,4 +5,36 @@ author: "Pat David"
 description: "Meta page about www.digikam.org"
 ---
 =

-Writing new content for the website is a bit different than using a CMS.
+Writing content for the website is a bit different now than using a CMS (l=
ike the previously used [Drupal][]).
+The biggest change is that the website data is now being tracked in a vers=
ion control system, [Git][].
+
+[Drupal]: https://www.drupal.org/
+[Git]: https://git-scm.com/
+
+
+Contributors that want to write content for the site only need to write th=
eir content as a [markdown][] file.
+This file and any associated assets required (such as images) can then be =
delivered to responsible team members to be checked and then published.
+
+[markdown]: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatshe=
et
+
+[Get the repo][]
+
+[Get the repo]: {{< ref "about/meta/index.md#git-repository" >}}
+
+
+### File Naming Convention
+
+News items have been using a naming convention:
+
+`YYYY-MM-DD_The_News_Item_Descriptive_Name.md`
+
+
+### Markdown
+
+
+
+### Publishing Changes
+
+If your account is a developer account (has push access to the repository)=
, you can publish news items by committing them to the repository and pushi=
ng.
+This should normally be done against the `dev` branch first to check that =
everything works and looks good.
+If so, it can then be merged into the `master` branch.
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic