aletheia-foundation / aletheia-foundation.github.io Goto Github PK

http://aletheia-foundation.io/blog lists all blog posts. Currently it works, but is a bit basic.

Lets make it better. A few basic improvements:

1. Style more fitting with the rest of the site
2. Include a bit more detail.. e.g. first paragraph, with a "read more.." (not sure if this is possible with Jekyll)
3. Pagination (there is only one post at the moment, so this is maybe not a pressing issue

Any other ideas welcome, keeping in mind that a future site redesign may happen soon.

I confirm:

• I've read the contributing guidelines and the code of conduct
• I've checked that this issue applies to this repo
• I've checked the existing issues, no one else has reported this
• I've got a clear and descriptive title for the issue

Suggest an enhancement - delete this section if not suggesting an enhancement

To make your enhancement suggestion as useful to others as possible, please consider the below and try to answer as many of them as possible:

• Provide a step-by-step description of the suggested enhancement in as many details as possible.
  An additional page that lists the names of financial backers above a set teir on Patreon to recognise everyone who supports with creating Aletheia

• Provide specific examples to demonstrate the steps. Include copy/pasteable snippets which you use in those examples, as Markdown code blocks if possible.
  It should go here:
  

• Describe the current behaviour and explain which behaviour you expected to see instead and why.
  There is no contributors section, we want there to be one

• Include screenshots which help you demonstrate the steps or point out the part of Aletheia which the suggestion is related to.
  Above

• Explain why this enhancement would be useful to most Aletheia users.
  Everyone feels good about being recognised for the financial support they do, supporters that feel good make the world and better place and make them more likely to contribute further

• List some other applications where this enhancement exists.
  Unsure

• Specify which version of Aletheia you're using.
  N/A

• Specify the name and version of the OS you're using.
  N/A

I confirm:

• I've read the contributing guidelines and the code of conduct
• I've checked that this issue applies to this repo
• I've checked the existing issues, no one else has reported this
• I've got a clear and descriptive title for the issue

Suggest an enhancement - delete this section if not suggesting an enhancement

To make your enhancement suggestion as useful to others as possible, please consider the below and try to answer as many of them as possible:

• Provide a step-by-step description of the suggested enhancement in as many details as possible.
  An additional page that lists contributors names to recognise everyone who assists with creating Aletheia

• Provide specific examples to demonstrate the steps. Include copy/pasteable snippets which you use in those examples, as Markdown code blocks if possible.
  It should go here:
  

• Describe the current behaviour and explain which behaviour you expected to see instead and why.
  There is no contributors section, we want there to be one

• Include screenshots which help you demonstrate the steps or point out the part of Aletheia which the suggestion is related to.
  Above

• Explain why this enhancement would be useful to most Aletheia users.
  Everyone feels good about being recognised for the work they do, contributors that feel good make the world and better place and make them more likely to contribute further

• List some other applications where this enhancement exists.
  Unsure

• Specify which version of Aletheia you're using.
  N/A

• Specify the name and version of the OS you're using.
  N/A

I confirm:

• I've read the contributing guidelines and the code of conduct
• I've checked that this issue applies to this repo
• I've checked the existing issues, no one else has reported this
• I've got a clear and descriptive title for the issue

My response:

Is any one working on contributor page. If not let me know I am happy to work

I confirm:

• I've read the contributing guidelines and the code of conduct
• I've checked that this issue applies to this repo
• I've checked the existing issues, no one else has reported this
• I've got a clear and descriptive title for the issue

Suggest an enhancement - delete this section if not suggesting an enhancement

To make your enhancement suggestion as useful to others as possible, please consider the below and try to answer as many of them as possible:

• Provide a step-by-step description of the suggested enhancement in as many details as possible.
• Provide specific examples to demonstrate the steps. Include copy/pasteable snippets which you use in those examples, as Markdown code blocks if possible.
• Describe the current behaviour and explain which behaviour you expected to see instead and why.
• Include screenshots which help you demonstrate the steps or point out the part of Aletheia which the suggestion is related to.
• Explain why this enhancement would be useful to most Aletheia users.
• List some other applications where this enhancement exists.
• Specify which version of Aletheia you're using.
• Specify the name and version of the OS you're using.

My response:

• We need a link to our Patreon page on our website https://www.patreon.com/Aletheia_f
• Would be nice if it could be placed here
  
• It's not there currently
• We need to generate funds to sustain the project
• N/A
• N/A
• N/A

So Kade can start writing content

We're using GitHub pages for our website and we have our own purchased domain. We need to point the domain to the website.

Want to appear when people are looking for articles and/or journals

Background image is not displaying on lower resolution mobiles.

This is the case on my Samsung Galaxy S5, but not on a recent iPhone (not sure of versions yet)

Possibly a useful article: https://stackoverflow.com/questions/23586530/css-background-image-not-displaying-on-mobile

I confirm:

• I've read the contributing guidelines and the code of conduct
• I've checked that this issue applies to this repo
• I've checked the existing issues, no one else has reported this
• I've got a clear and descriptive title for the issue

Report bugs - delete this section if not reporting a bug

To make your bug report as useful to others as possible, please consider the below and try to answer as many of them as possible:

Explain the problem and include additional details to help maintainers reproduce the problem:

• Describe the exact steps which reproduce the problem in as many details as possible.
• Describe the behaviour you observed after following the steps and point out what exactly is the problem with that behaviour.
• Explain what behaviour you expected to see instead and why.
• Include screenshots where possible.
• If you're reporting that Alethia crashed, include a crash report with a stack trace from the operating system if possible. Include the crash report in the issue in a code block, a file attachment, or put it in a gist and provide link to that gist.
• If the problem is related to performance, include a CPU profile capture and a screenshot with your report if possible.
• If the problem wasn't triggered by a specific action, describe what you were doing before the problem happened and share more information using the guidelines below.

My response:

Provide more context by answering these questions:

• Can you reproduce the problem in safe mode?
• Did the problem start happening recently (e.g. after updating to a new version of Aletheia) or was this always a problem?
• If the problem started happening recently, can you reproduce the problem in an older version of Aletheia? What's the most recent version in which the problem doesn't happen?
• Can you reliably reproduce the issue? If not, provide details about how often the problem happens and under which conditions it normally happens.

My reponse:

Include details about your configuration and environment:

• Which version of Aletheia are you using?
• What's the name and version of the OS you're using?
• Are you running Aletheia in a virtual machine? If so, which VM software are you using and which operating systems and versions are used for the host and the guest?
• Are you using Aletheia with multiple monitors? If so, can you reproduce the problem when you use a single monitor?
• Which keyboard layout are you using? Are you using a US layout or some other layout?

My response:

Suggest an enhancement - delete this section if not suggesting an enhancement

To make your enhancement suggestion as useful to others as possible, please consider the below and try to answer as many of them as possible:

• Provide a step-by-step description of the suggested enhancement in as many details as possible.
• Provide specific examples to demonstrate the steps. Include copy/pasteable snippets which you use in those examples, as Markdown code blocks if possible.
• Describe the current behaviour and explain which behaviour you expected to see instead and why.
• Include screenshots which help you demonstrate the steps or point out the part of Aletheia which the suggestion is related to.
• Explain why this enhancement would be useful to most Aletheia users.
• List some other applications where this enhancement exists.
• Specify which version of Aletheia you're using.
• Specify the name and version of the OS you're using.

My response:

To make Visual Search engine optimization I need writing rights to repository

I confirm:

• I've read the contributing guidelines and the code of conduct
• I've checked that this issue applies to this repo
• I've checked the existing issues, no one else has reported this
• I've got a clear and descriptive title for the issue

Suggest an enhancement - delete this section if not suggesting an enhancement

To make your enhancement suggestion as useful to others as possible, please consider the below and try to answer as many of them as possible:

• Provide a step-by-step description of the suggested enhancement in as many details as possible.
• Provide specific examples to demonstrate the steps. Include copy/pasteable snippets which you use in those examples, as Markdown code blocks if possible.
• Describe the current behaviour and explain which behaviour you expected to see instead and why.
• Include screenshots which help you demonstrate the steps or point out the part of Aletheia which the suggestion is related to.
• Explain why this enhancement would be useful to most Aletheia users.
• List some other applications where this enhancement exists.
• Specify which version of Aletheia you're using.
• Specify the name and version of the OS you're using.

My response:

• The website currently uses HTTP, it needs to use HTTPS by default.
• Example
  

• current behaviour is traffic to the site is not encrypted and if we add in donation facilities, log ins etc these can be compromised. The behaviour required is using HTTPS, traffic to the site and any information submitted to the site will be encrypted which is why this upgrade would be useful.
• Examples of HTTPS
  
  

Website needs to be prettyafied

I confirm:

• I've read the contributing guidelines and the code of conduct
• I've checked that this issue applies to this repo
• I've checked the existing issues, no one else has reported this
• I've got a clear and descriptive title for the issue

Suggest an enhancement - delete this section if not suggesting an enhancement

To make your enhancement suggestion as useful to others as possible, please consider the below and try to answer as many of them as possible:

• Provide a step-by-step description of the suggested enhancement in as many details as possible.
• Provide specific examples to demonstrate the steps. Include copy/pasteable snippets which you use in those examples, as Markdown code blocks if possible.
• Describe the current behaviour and explain which behaviour you expected to see instead and why.
• Include screenshots which help you demonstrate the steps or point out the part of Aletheia which the suggestion is related to.
• Explain why this enhancement would be useful to most Aletheia users.
• List some other applications where this enhancement exists.
• Specify which version of Aletheia you're using.
• Specify the name and version of the OS you're using.

My response:

• I'm in the process of creating a Flattr account for Aletheia and we will need to add things to the website to make it Flattrable (I will update once I know what those things are...)
  Update: A tag needs to be added to the site that I can send to you
• Would be nice if it could go here
  
• It's not there currently
• N/A
• N/A
• N/A

I confirm:

• I've read the contributing guidelines and the code of conduct
• I've checked that this issue applies to this repo
• I've checked the existing issues, no one else has reported this
• I've got a clear and descriptive title for the issue

Report bugs - delete this section if not reporting a bug

To make your bug report as useful to others as possible, please consider the below and try to answer as many of them as possible:

Explain the problem and include additional details to help maintainers reproduce the problem:

• Describe the exact steps which reproduce the problem in as many details as possible.
• Describe the behaviour you observed after following the steps and point out what exactly is the problem with that behaviour.
• Explain what behaviour you expected to see instead and why.
• Include screenshots where possible.
• If you're reporting that Alethia crashed, include a crash report with a stack trace from the operating system if possible. Include the crash report in the issue in a code block, a file attachment, or put it in a gist and provide link to that gist.
• If the problem is related to performance, include a CPU profile capture and a screenshot with your report if possible.
• If the problem wasn't triggered by a specific action, describe what you were doing before the problem happened and share more information using the guidelines below.

My response:

Provide more context by answering these questions:

• Can you reproduce the problem in safe mode?
• Did the problem start happening recently (e.g. after updating to a new version of Aletheia) or was this always a problem?
• If the problem started happening recently, can you reproduce the problem in an older version of Aletheia? What's the most recent version in which the problem doesn't happen?
• Can you reliably reproduce the issue? If not, provide details about how often the problem happens and under which conditions it normally happens.

My reponse:

Include details about your configuration and environment:

• Which version of Aletheia are you using?
• What's the name and version of the OS you're using?
• Are you running Aletheia in a virtual machine? If so, which VM software are you using and which operating systems and versions are used for the host and the guest?
• Are you using Aletheia with multiple monitors? If so, can you reproduce the problem when you use a single monitor?
• Which keyboard layout are you using? Are you using a US layout or some other layout?

My response:

Suggest an enhancement - delete this section if not suggesting an enhancement

To make your enhancement suggestion as useful to others as possible, please consider the below and try to answer as many of them as possible:

• Provide a step-by-step description of the suggested enhancement in as many details as possible.
• Provide specific examples to demonstrate the steps. Include copy/pasteable snippets which you use in those examples, as Markdown code blocks if possible.
• Describe the current behaviour and explain which behaviour you expected to see instead and why.
• Include screenshots which help you demonstrate the steps or point out the part of Aletheia which the suggestion is related to.
• Explain why this enhancement would be useful to most Aletheia users.
• List some other applications where this enhancement exists.
• Specify which version of Aletheia you're using.
• Specify the name and version of the OS you're using.

My response:

As I am new to this org I may have different idea about UI design which may contradict your previous own so, please let me know any UI guidelines