FairCoopWebsite issueshttps://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues2024-03-04T11:41:44Zhttps://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/36Set english as main languages2024-03-04T11:41:44ZencosianimaSet english as main languagesEnglish is supposed to be the main languages, however, when translation is not available, contents are shown in Spanish. That happens when Spanish was the first version saved for each post. In any case, there must be a way to control tha...English is supposed to be the main languages, however, when translation is not available, contents are shown in Spanish. That happens when Spanish was the first version saved for each post. In any case, there must be a way to control that behaviour :Dhttps://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/35MarkDown formatting syntax not working in summary2024-03-04T11:41:44ZencosianimaMarkDown formatting syntax not working in summarywhen putting text on Summary MD format is not supported, that would make, for example, this bit:
FairCoop, taking up the call from [Internationalist Commune of Rojava]( https://internationalistcommune.com/riseup4rojava-call-for-global-da...when putting text on Summary MD format is not supported, that would make, for example, this bit:
FairCoop, taking up the call from [Internationalist Commune of Rojava]( https://internationalistcommune.com/riseup4rojava-call-for-global-days-of-action-on-27-and-28-january-2019/) of the 2 days actions on 27-28 January #RiseUp4Rojava to stand for DFNS, because, *by defending the Rojava revolution together, we defend all our hopes*.
wouldn't show: [Internationalist Commune of Rojava]( https://internationalistcommune.com/riseup4rojava-call-for-global-days-of-action-on-27-and-28-january-2019/)
as well as:
*by defending the Rojava revolution together, we defend all our hopes*.
only square and round bracket with their contents and *two asterisks instead of italic*https://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/25Maintenance with a responsible and reports2024-03-04T11:43:23ZAl-DemonMaintenance with a responsible and reportsPermanent task for good maintenance
This task is too in the other Project manager https://org.fair.coop/issues/63Permanent task for good maintenance
This task is too in the other Project manager https://org.fair.coop/issues/63Phase 4 Mantenance and improvehttps://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/17Define design of each structure2023-07-06T16:04:14ZAl-DemonDefine design of each structureBoth for the writing part and for the sample part already finished, you will have a design of each form.
* Example: Blog
* Design fill article:
* Fields to be filled in list:
* Title
* image to upload
* text description with wyswyg...Both for the writing part and for the sample part already finished, you will have a design of each form.
* Example: Blog
* Design fill article:
* Fields to be filled in list:
* Title
* image to upload
* text description with wyswyg tools
* field separated by commas
* date
* Author
* to post
* Add mockup
Design shown:
* Title centered on H2 size 20px
* Large Image size 100x200
* Text in black with serif font
* Placing the text in justified
* After the categories in bubbles
* Add mockup
* [ ] Design Form Page (static page)
* [ ] Design Form Article blog
* [ ] Design Form News
* [ ] Design Form Other
* [ ] Design Form Local nodes sitePhase 2 Development2018-03-04https://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/16Define article structure blog / wiki / cover2024-03-04T11:43:23ZAl-DemonDefine article structure blog / wiki / cover### Define article structure blog / wiki / cover
#### Define how we want the forms
Each type of article or page must have its own characteristics so we facilitate writing and the separation between design and content .. Obviously you sh...### Define article structure blog / wiki / cover
#### Define how we want the forms
Each type of article or page must have its own characteristics so we facilitate writing and the separation between design and content .. Obviously you should always see some flexibility that can be given for always personalized items ...
Example: Blog must always carry:
* Title field
* Description and content field
* Representative image field
* Category field
* Writing recommendations
Example on design of the backend
![imagen_backend_grav](https://www.journalisten-tools.de/wp-content/uploads/2017/08/grav_backend_artikel.png)
In grav we need to define the continent by coding but later is easy to edit from backend we can try to replicate this forms
- Page (static page)
Fields:
- Title
- Description and content field with edit tool bar (allow coding page)
- Category field
- Uploads field
- Article blog
Fields:
- Title
- Summary
- Description and content field with edit tool bar
- Representative image field to put in the blog page (eg.800x400)
- Category field
- Upload field
- News (different design for news... we need a meeting to propose)
Fields:
- Title
- Summary
- Description and content field with edit tool bar
- Representative image field to put in the blog page (eg.800x200)
- Upload field
Other:
- Clear syntax to add video / music / images inside the description content
- Allow not use the main image in article page
- Add share links?¿
- external links open directly in other tab
- Local nodes news (different design for news... we need a meeting to propose)
Fields:
- Title
- Summary
- Description and content field with edit tool bar
- Representative image field to put in the blog page (eg.800x200)
- Local node from relationship
- Upload field
Other:
- Clear syntax to add video / music / images inside the description content
- Local node search by using letter
- Allow not use the main image in article page
- Add share links?¿
- external links open directly in other tab
- Local nodes site
Fields:
- Name
- Summary
- Description and content field with edit tool bar
- Representative image field to put in the localnodes page (eg.800x400)
- Address
Other:
- external links open directly in other tab
#### Define design of each structure
Both for the writing part and for the sample part already finished, you will have a design of each form.
* Example: Blog
* Design fill article:
* Fields to be filled in list:
* Title
* image to upload
* text description with wyswyg tools
* field separated by commas
* date
* Author
* to post
* Add mockup
Design shown:
* Title centered on H2 size 20px
* Large Image size 100x200
* Text in black with serif font
* Placing the text in justified
* After the categories in bubbles
* Add mockup
* [ ] Fine Form Page (static page)
* [ ] Fine Form Article blog
* [ ] Fine Form News
* [ ] Fine Form Other
* [ ] Fine Form Local nodes sitePhase 2 Development2018-02-28