diff --git a/v3/feed.rss b/v3/feed.rss index af0f671..b99cfc0 100644 --- a/v3/feed.rss +++ b/v3/feed.rss @@ -2,8 +2,8 @@ GNU social V3https://gnusocial.rocks/v3/index.html Development blog where we announce our progress.en -Thu, 19 Aug 2021 03:09:11 +0100 -Thu, 19 Aug 2021 03:09:11 +0100 +Thu, 19 Aug 2021 03:15:08 +0100 +Thu, 19 Aug 2021 03:15:08 +0100 Updates: V3 blog @@ -25,6 +25,7 @@ forget to subscribe!</p> + <!-- text end --> ]]></description><link>https://gnusocial.rocks/v3/updates-v3-blog.html</link> <guid>https://gnusocial.rocks/v3/./updates-v3-blog.html</guid> @@ -115,6 +116,7 @@ functionality with more stability.</p> + <!-- text end --> @@ -216,6 +218,7 @@ any remote URL being shared in a note.</li> + <!-- text end --> @@ -297,6 +300,7 @@ Updates: Finish the Avatar component + <!-- text end --> @@ -308,23 +312,16 @@ Updates: Finish the Avatar component Milestone: Documentation and Tests Infrastructure WIKI Milestone entry

+

>WIKI Milestone entry

GNU social now has its documentation available in https://docs.gnusocial.rocks/. It features four -different books. It is automatically generated from the source using mdBook.

+different books. These are automatically generated from the source using mdBook.

-

Only the development book is in an elaborated state, the other books are +

+

Only the development book is in an elaborated state, the other books are holding for more ready code.

- -

Two of them are updates from existing documentation:

- - +

And two of them are new:

@@ -333,79 +330,23 @@ from the "Unofficial GNU social docs" by Thomask who Designer is the most recent of the four and came from a necessity of keeping some standardization between templates and ensuring the same principles are kept in mind when designing new themes. +

And two of them are updates from existing documentation:

+ + +

Together with the documentation we've introduced a wiki. Its purpose is to walk-through decisions, -convention, terminology. It's where we document the reasoning the dev team went +convention, terminology. It's where we document the reasoning the development team went through before implementing more sophisticated functionalities.

Finally, when the documentation doesn't explain, and to ensure the whole code is properly tested, we have the -tests. And the coverage is available here.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +tests. And the coverage is available here. At the time of writing the coverage has 98.76% code lines tested.

@@ -457,6 +398,7 @@ The key ones are:

documentation.

+ ]]>https://gnusocial.rocks/v3/milestone-port-media-handling-from-v2.html https://gnusocial.rocks/v3/./milestone-port-media-handling-from-v2.html diff --git a/v3/milestone-documentation-and-tests-infrastructure.html b/v3/milestone-documentation-and-tests-infrastructure.html index 5f5ee33..b7259a0 100644 --- a/v3/milestone-documentation-and-tests-infrastructure.html +++ b/v3/milestone-documentation-and-tests-infrastructure.html @@ -43,23 +43,16 @@ GNU social development team -

WIKI Milestone entry

+

>WIKI Milestone entry

GNU social now has its documentation available in https://docs.gnusocial.rocks/. It features four -different books. It is automatically generated from the source using mdBook.

+different books. These are automatically generated from the source using mdBook.

-

Only the development book is in an elaborated state, the other books are +

+

Only the development book is in an elaborated state, the other books are holding for more ready code.

- -

Two of them are updates from existing documentation:

- - +

And two of them are new:

@@ -68,79 +61,23 @@ from the "Unofficial GNU social docs" by Thomask who Designer is the most recent of the four and came from a necessity of keeping some standardization between templates and ensuring the same principles are kept in mind when designing new themes. +

And two of them are updates from existing documentation:

+ + +

Together with the documentation we've introduced a wiki. Its purpose is to walk-through decisions, -convention, terminology. It's where we document the reasoning the dev team went +convention, terminology. It's where we document the reasoning the development team went through before implementing more sophisticated functionalities.

Finally, when the documentation doesn't explain, and to ensure the whole code is properly tested, we have the -tests. And the coverage is available here.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +tests. And the coverage is available here. At the time of writing the coverage has 98.76% code lines tested.

diff --git a/v3/milestone-documentation-and-tests-infrastructure.md b/v3/milestone-documentation-and-tests-infrastructure.md index 7d5c687..1eaa318 100644 --- a/v3/milestone-documentation-and-tests-infrastructure.md +++ b/v3/milestone-documentation-and-tests-infrastructure.md @@ -1,31 +1,31 @@ Milestone: Documentation and Tests Infrastructure -**[WIKI Milestone entry](https://agile.gnusocial.rocks/doku.php?id=milestones:initial_test_documentation_infrastructure)** +**[>WIKI Milestone entry](https://agile.gnusocial.rocks/doku.php?id=milestones:initial_test_documentation_infrastructure)** GNU social now has its documentation available in [https://docs.gnusocial.rocks/](https://docs.gnusocial.rocks/). It features four -different books. It is automatically generated from the [source](https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/docs) using [mdBook](https://rust-lang.github.io/mdBook/). +different books. These are automatically generated from the [source](https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/docs) using [mdBook](https://rust-lang.github.io/mdBook/). -Only the development book is in an elaborated state, the other books are -holding for more ready code. - -Two of them are updates from existing documentation: - -* The [User](https://docs.gnusocial.rocks/user) one is adapted -from the existing GNU social documentation for users that was provided in v2. -* The [Administrator](https://docs.gnusocial.rocks/administrator) one is adapted -from the "Unofficial GNU social docs" by Thomask who [asked us to make it official](https://notabug.org/diogo/gnu-social/issues/246). +> Only the development book is in an elaborated state, the other books are +> holding for more ready code. And two of them are new: * The [Developer](https://docs.gnusocial.rocks/developer) is both intended to guide third-party plugin developers and to make it easier of contributing to the code. * The [Designer](https://docs.gnusocial.rocks/designer) is the most recent of the four and came from a necessity of keeping some standardization between templates and ensuring the same principles are kept in mind when designing new themes. +And two of them are updates from existing documentation: + +* The [User](https://docs.gnusocial.rocks/user) one is adapted +from the existing GNU social documentation for users that was provided in v2. +* The [Administrator](https://docs.gnusocial.rocks/administrator) one is adapted +from the "Unofficial GNU social docs" by Thomask who [asked us to make it official](https://notabug.org/diogo/gnu-social/issues/246). + Together with the documentation we've introduced a [wiki](https://agile.gnusocial.rocks/). Its purpose is to walk-through decisions, -convention, terminology. It's where we document the reasoning the dev team went +convention, terminology. It's where we document the reasoning the development team went through before implementing more sophisticated functionalities. Finally, when the documentation doesn't explain, and to ensure the whole code is properly tested, we have the -[tests](https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/tests). And the coverage is available [here](https://coverage.gnusocial.rocks/). +[tests](https://code.undefinedhackers.net/GNUsocial/gnu-social/src/branch/v3/tests). And the coverage is available [here](https://coverage.gnusocial.rocks/). At the time of writing the coverage has 98.76% code lines tested. diff --git a/v3/milestone-port-media-handling-from-v2.html b/v3/milestone-port-media-handling-from-v2.html index b302002..3eab33e 100644 --- a/v3/milestone-port-media-handling-from-v2.html +++ b/v3/milestone-port-media-handling-from-v2.html @@ -83,6 +83,7 @@ The key ones are:

documentation.

+ diff --git a/v3/updates-finish-the-avatar-component.html b/v3/updates-finish-the-avatar-component.html index b814e87..cacc482 100644 --- a/v3/updates-finish-the-avatar-component.html +++ b/v3/updates-finish-the-avatar-component.html @@ -113,6 +113,7 @@ GNU social development team + diff --git a/v3/updates-implement-storeremotemedia-for-v3-and-port-embed.html b/v3/updates-implement-storeremotemedia-for-v3-and-port-embed.html index 5664f39..cec35c2 100644 --- a/v3/updates-implement-storeremotemedia-for-v3-and-port-embed.html +++ b/v3/updates-implement-storeremotemedia-for-v3-and-port-embed.html @@ -124,6 +124,7 @@ functionality with more stability.

+ diff --git a/v3/updates-improve-the-attachments-system.html b/v3/updates-improve-the-attachments-system.html index c799e3e..3318e4e 100644 --- a/v3/updates-improve-the-attachments-system.html +++ b/v3/updates-improve-the-attachments-system.html @@ -133,6 +133,7 @@ any remote URL being shared in a note. + diff --git a/v3/updates-v3-blog.html b/v3/updates-v3-blog.html index ba7063d..fc90ed7 100644 --- a/v3/updates-v3-blog.html +++ b/v3/updates-v3-blog.html @@ -59,6 +59,7 @@ forget to subscribe!

+