Things to do - Revision history

Thaumechanic: /* Site look/ layout of interest */ adding two specific actions

2026-04-25T23:48:29Z

Site look/ layout of interest: adding two specific actions

← Older revision		Revision as of 23:48, 25 April 2026
Line 26:		Line 26:

	The ER Discord #art-build channel has folks who can make graphics on request. We don’t need to steal art or use gen AI :-)		The ER Discord #art-build channel has folks who can make graphics on request. We don’t need to steal art or use gen AI :-)

			* We need a site logo
			* Colors, fonts, etc. should be chosen

	== Site landing concepts to consider ==		== Site landing concepts to consider ==

Thaumechanic: Fixing general formatting

2026-04-25T23:45:31Z

Fixing general formatting

← Older revision		Revision as of 23:45, 25 April 2026
Line 1:		Line 1:
	== ER wiki ideas - Elaine, 23-Apr-2026 ==		== ER wiki ideas - Elaine, 23-Apr-2026 ==
	~~● The “Support an argument” framework that Rob explained to me is really interesting, and Chris thinks~~ so ~~too. However, Chris seemed hesitant that~~ we ~~would dive in to that without him taking time to make~~ it ~~perfect~~. ~~Nevertheless, I’m going~~ to ~~type in a draft like that anyway as a landing page idea~~.		I feel like wikis are infinite so it’s not a question of “can we have this on the site” so much as “how will we sensibly find it and what should be on top”. Great to have your expertise.

	~~● It’ll be something~~ like ~~what’s on~~ the ~~next slide~~.		== Supporting an argument ==
			We would like to create a set of pages that present an argument, and allows the reader to click through to the supporting ideas behind the argument. Chris thinks this is interesting, but seemed hesitant that we would dive in to that without him taking time to make it perfect.

	~~● Other slides in this deck will be wish list for the wiki in no particular order, hoping you can extract requirements and “desirements” for the architecture!~~		=== Argument format straw model ===

	~~● I feel like wikis are infinite so it’s not a question of “can we have this on the site” so much as “how will we sensibly find it and what should be on top”. Great to have your expertise.~~

	== Argument ~~example ==~~

	~~=== “the argument” placeholder words~~ ===
	STATES SHOULD USE THEIR POWERS		STATES SHOULD USE THEIR POWERS

Line 20:		Line 15:

	== Site look/ layout of interest ==		== Site look/ layout of interest ==
			I like the look and feel of these pages:
			* [https://commonslibrary.org commonslibrary.org]
			* [https://commonslibrary.org/about commonslibrary.org/about]
			Either of these would work for a landing page structured as:

	* ~~I like these pages at commonslibrary.org and commonslibrary.org/about~~		* the argument = what’s this about
	* Either of these would work for a landing page structured as: – the argument = what’s this about – more stuff = actions+research		* more stuff = actions+research
	* It looks like the orange rectangles are containers that work with the header to enclose any content?
	* The ER Discord #art-build channel has folks who can make graphics on request. We don’t need to steal art or use gen AI :-)		It looks like the orange rectangles are containers that work with the header to enclose any content?

			The ER Discord #art-build channel has folks who can make graphics on request. We don’t need to steal art or use gen AI :-)

	== Site landing concepts to consider ==		== Site landing concepts to consider ==
Line 44:		Line 45:

	== Existing ER+togetherfoundation pages ==		== Existing ER+togetherfoundation pages ==
			We need links back to existing pages.
			* https://apps.togetherfdn.us/html/er/legislation/portal.html
			** might be best as a link from wiki
			** want to be able to maintain a neutral look for this regardless of wiki site design
			** legislators are pointed here, don’t want them navigating to a flurry of pages in progress by mutliple volunteers
			* https://apps.togetherfdn.us/html/er/campaigns/firstcontact.html#
			** public campaign landing page, suggest migrate into dedicated wiki space
			* https://apps.togetherfdn.us/html/er/elected/officials.html
			** this resource is for the ER team. not sure it should be findable for visitors

	* <nowiki>https://apps.togetherfdn.us/html/er/legislation/portal.html</nowiki>		== Tabular content ==
	** might be best as a link from wiki		There are at least two areas, maybe more, where the content the team is coming up with could be usefully constructed as tables, not as the only way to display it, but as a helpful “finder” or a visual communication having impact.
	** want to be able to maintain a neutral look for this regardless of wiki site design
	** legislators are ~~pointed here~~, ~~don’t want them navigating to a flurry of pages in progress by mutliple volunteers~~
	* <nowiki>https://apps.togetherfdn.us/html/er/campaigns/firstcontact.html#</nowiki> – public campaign landing page, ~~suggest migrate into dedicated wiki space~~
	* <nowiki>https://apps.togetherfdn.us/html/er/elected/officials.html</nowiki> – this resource is for the ER team. not ~~sure~~ it ~~should be findable for visitors~~

	== ~~about “grids” as content~~ ==		=== State Scorecard ===
	There are ~~at least two areas~~, ~~maybe more~~, ~~where the content the team is coming up with could be usefully constructed as a grid – not as the only way to display~~ it~~, but as a helpful “finder” or a visual communication having impact.~~		There are many states and many issues, an amazing picture will develop when we know which issues are “activated” in which state houses, and build it graphically

	~~=== State Scorecard ===~~		* This is Elaine’s pet project, work in progress. Lots of data being bookmarked. It would be cool to have
	~~There are many states and many issues, an amazing picture will develop when we know which issues are “activated” in which state houses, and build it graphically –~~ This is Elaine’s pet project, work in progress. Lots of data being bookmarked. It would be cool to have “tickets” so folks can throw news article links at this. A tool to help me build the first rev would be AWESOME.		** “tickets” so folks can throw news article links at this.
			** A tool to help me build the first rev would be AWESOME.

	=== Communications strategy ===		=== Communications strategy ===

	* Sabrina_A Decling Democracy came up with a rubric, Chris/ Troy are reviewing		* Sabrina_A Decling Democracy came up with a rubric,
			* Chris/ Troy are reviewing
	* The two axes are “who we communicate to” and “what we say to them”		* The two axes are “who we communicate to” and “what we say to them”

	== Checklists: Site not complete without ==		== Checklists: Site not complete without ==

	=== ~~IDENTITY~~ ===		=== Identity ===

	* ✔ The ER brand, but this is a volunteer or support site, and it is not the TERPAC.		* ✔ The ER brand, but this is a volunteer or support site, and it is not the TERPAC.
Line 73:		Line 81:
	* ✔ Direction to: (1) Substack (2) TER BuyMeACoffee (3)		* ✔ Direction to: (1) Substack (2) TER BuyMeACoffee (3)

	=== TERPAC ~~VISITOR SEES WE ARE ACTION BASED~~ and can participate ===		=== TERPAC visitors see we are action based and can participate ===

	* ✔ Our action based intent is indicated from landing page(s)		* ✔ Our action based intent is indicated from landing page(s)
Line 89:		Line 97:
	* ✔ state based ones		* ✔ state based ones

	=== TBC ~~ISSUES~~ ===		=== TBC issues ===

	* ✔ Hot issues (topical + perennial)		* ✔ Hot issues (topical + perennial)

Thaumechanic: initial insert

2026-04-25T23:24:37Z

initial insert

New page

== ER wiki ideas - Elaine, 23-Apr-2026 ==
● The “Support an argument” framework that Rob explained to me is really interesting, and Chris thinks so too. However, Chris seemed hesitant that we would dive in to that without him taking time to make it perfect. Nevertheless, I’m going to type in a draft like that anyway as a landing page idea.

● It’ll be something like what’s on the next slide.

● Other slides in this deck will be wish list for the wiki in no particular order, hoping you can extract requirements and “desirements” for the architecture!

● I feel like wikis are infinite so it’s not a question of “can we have this on the site” so much as “how will we sensibly find it and what should be on top”. Great to have your expertise.

== Argument example ==

=== “the argument” placeholder words ===
STATES SHOULD USE THEIR POWERS

* Pro, urgency: we're in trouble but can get out [read more..]
* Pro, moral: democracy is good [read more ...]
* Pro, feasible: states already do this [ read more ...]
* Con, this looks like a fight: [sub-arguments >> use state power anyway]
* Con, we'd rather be optimistic and wait it out: [sub-arguments >> use state power anyway]

== Site look/ layout of interest ==

* I like these pages at commonslibrary.org and commonslibrary.org/about
* Either of these would work for a landing page structured as: – the argument = what’s this about – more stuff = actions+research
* It looks like the orange rectangles are containers that work with the header to enclose any content?
* The ER Discord #art-build channel has folks who can make graphics on request. We don’t need to steal art or use gen AI :-)

== Site landing concepts to consider ==

=== Landing idea 1: informational ===

* “the argument”
* more about ER – Chris’ sites landing; substack index; glossary; tag cloud
* ready to activate? actions landing – includes campaigns
* our research landing – issues and states
* team & communications stuff

==== Landing idea 2: dashboard ====

* wiki hosted action of the day, a rolling page that someone has responsibility to contruct. Can access an archive.
* embed discord #action-of-the-day announcements channel
* embed Chris’ substack feed (notes + posts)
* currently active ER multi-week campaign, rolling page or similar

== Existing ER+togetherfoundation pages ==

* <nowiki>https://apps.togetherfdn.us/html/er/legislation/portal.html</nowiki>
** might be best as a link from wiki
** want to be able to maintain a neutral look for this regardless of wiki site design
** legislators are pointed here, don’t want them navigating to a flurry of pages in progress by mutliple volunteers
* <nowiki>https://apps.togetherfdn.us/html/er/campaigns/firstcontact.html#</nowiki> – public campaign landing page, suggest migrate into dedicated wiki space
* <nowiki>https://apps.togetherfdn.us/html/er/elected/officials.html</nowiki> – this resource is for the ER team. not sure it should be findable for visitors

== about “grids” as content ==
There are at least two areas, maybe more, where the content the team is coming up with could be usefully constructed as a grid – not as the only way to display it, but as a helpful “finder” or a visual communication having impact.

=== State Scorecard ===
There are many states and many issues, an amazing picture will develop when we know which issues are “activated” in which state houses, and build it graphically – This is Elaine’s pet project, work in progress. Lots of data being bookmarked. It would be cool to have “tickets” so folks can throw news article links at this. A tool to help me build the first rev would be AWESOME.

=== Communications strategy ===

* Sabrina_A Decling Democracy came up with a rubric, Chris/ Troy are reviewing
* The two axes are “who we communicate to” and “what we say to them”

== Checklists: Site not complete without ==

=== IDENTITY ===

* ✔ The ER brand, but this is a volunteer or support site, and it is not the TERPAC.
* ✔ No candidates are implied to be on board or being supported here.
* ✔ What we are about; make soft secession welcoming with whatever words work
* ✔ Paths to learn more about ER
* ✔ Direction to: (1) Substack (2) TER BuyMeACoffee (3)

=== TERPAC VISITOR SEES WE ARE ACTION BASED and can participate ===

* ✔ Our action based intent is indicated from landing page(s)
* ✔ Landing page for campaigns is public
* ✔ Campaign toolkits are public
* ✔ Reinforce that unlike many orgs, we call STATE legislators, Sec of State, AG offices, Cty Atty’s...
* ✔ Resist the urge to redirect to too many “find your leg” external sites

=== Research and information that makes Chris’ writings more accessible ===

* ✔ Our index of Chris’ writings and videos is made human readable somehow
* ✔ Glossary of Chris’ ER terms
* ✔ Sister orgs and campaigns that reinforce soft secession going mainstream:
* ✔ statefutures.org
* ✔ state based ones

=== TBC ISSUES ===

* ✔ Hot issues (topical + perennial)
* ✔ Issues supported by specific ER campaigns and/or model legislation
* ✔ Issues compendium, including those being researched but not supported by campaigns yet
* ✔ Suport for future “State Scorecard” indexing of issues
* ✔ TBD: score purple-ness of states; maps including clickable someday

=== Legislative campaign support ===

* ✔ Campaign landing page
* ✔ Four Laws / First Contact toolkit
* ✔ Team members can construct new toolkits. Ideally a tool prompts them for (use First Contact model):
* ✔ action overview; audience; set stage; time frame; audience; plan; scripts; resources; tools
* ✔ Sandbox status for unpublished toolkit for QA by volunteer team (organize in Discord, QA at site)

=== Organizing tools (preliminary; provide support for future content?) ===

* ✔ Find an ER teammate near you
* ✔ Start an ER club locally
* ✔ Path to Discord onboarding (Troy is responsible for getting more of an onboarding committee going and figuring out better vetting)

=== Index and search ===

* ✔ Glossary of ER terms
* ✔ Glossary of legislative terms
* ✔ Dictionary to assist in tagging. I don’t know the best practices, do we seed the site with some predefined tags so we don’t have too much duplication at the start?
* ✔ Tag cloud page for navigation, fun
* ✔ Other kinds of search and tag navigation – I’m not knowledgeable

=== Wiki team management ===

* ✔ Authentication
* ✔ Communituy guidelines or equivalent for team creating pages
* ✔ How to join / how to contact us ✔ Ticket systems for “easy” inputs and suggestions
* ✔ Other?
* ✔ Will page comments be prominent? Could be distracting in our scenario of team + visitors