<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.pine64.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Rjulian</id>
	<title>PINE64 - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.pine64.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Rjulian"/>
	<link rel="alternate" type="text/html" href="https://wiki.pine64.org/wiki/Special:Contributions/Rjulian"/>
	<updated>2026-04-17T23:07:48Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.37.1</generator>
	<entry>
		<id>https://wiki.pine64.org/index.php?title=User:Aarondabomb/PineNote_Documentation&amp;diff=13180</id>
		<title>User:Aarondabomb/PineNote Documentation</title>
		<link rel="alternate" type="text/html" href="https://wiki.pine64.org/index.php?title=User:Aarondabomb/PineNote_Documentation&amp;diff=13180"/>
		<updated>2022-06-12T16:20:05Z</updated>

		<summary type="html">&lt;p&gt;Rjulian: Added a few more items to needs to get done.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Under construction}}&lt;br /&gt;
&lt;br /&gt;
This space is intended to track the current status of documentation. As documentation is generated and organized in a more cohesive way, this may no longer be necessary.&lt;br /&gt;
&lt;br /&gt;
== Who Can Contribute ==&lt;br /&gt;
Hopefully anyone! These are people who are thinking especially hard about this:&lt;br /&gt;
* Aarondabomb&lt;br /&gt;
* rjulian&lt;br /&gt;
&lt;br /&gt;
== What needs to get done ==&lt;br /&gt;
# Reorganize the information that's already at [[PineNote Development]].&lt;br /&gt;
#: This means creating new pages, like [[PineNote: Getting Started]] that contains the important info.&lt;br /&gt;
# Create a getting started page&lt;br /&gt;
# Page to more clearly describe what &amp;quot;the project&amp;quot; even is&lt;br /&gt;
## Answer the question: Why does Pine64 sell the PineNote?&lt;br /&gt;
## There are a number of folks doing different things. There is no cohesive effort, but what someone else accomplishes may help you, and documenting/organizing these efforts can maximize the chances for cross-pollination.&lt;br /&gt;
# Outline how to get involved in the community.&lt;br /&gt;
#: We know there's chat, but that's not &amp;quot;active&amp;quot; involvement.&lt;br /&gt;
# Provide resources to learn about the technology behind the PineNote and development efforts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== End User Personas to Consider ==&lt;br /&gt;
When we think of &amp;quot;who may buy/use a PineNote&amp;quot;, we have to consider the personas who would purchase this: &lt;br /&gt;
* Hardware developers interested in e-ink and open source development&lt;br /&gt;
* Software developers who enjoy e-ink hardware and want to explore building software leveraging e-ink hardware. &lt;br /&gt;
* Technologists who understand the product category and want to experience/test out using the PineNote.&lt;br /&gt;
* Pure end users who want an open source/copyleft version of the remarkable 2. &lt;br /&gt;
* End users who have no clue about the product category (e.g. imagine they got this as a gift).&lt;br /&gt;
&lt;br /&gt;
Right now, of the above personas, none of them are getting effective documentation, with hardware developers getting the most information of the bunch.&lt;/div&gt;</summary>
		<author><name>Rjulian</name></author>
	</entry>
</feed>