Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[epic] Life Itself new integrated website 2022 #170

Closed
34 of 74 tasks
rufuspollock opened this issue Oct 29, 2022 · 2 comments
Closed
34 of 74 tasks

[epic] Life Itself new integrated website 2022 #170

rufuspollock opened this issue Oct 29, 2022 · 2 comments
Assignees
@rufuspollock @nathenf @ZybN
Labels
Epic Roadmap Wiser

Comments

@rufuspollock
Copy link
Member

rufuspollock commented Oct 29, 2022 •
edited by nathenf

We are doing a major update of the Life Itself website to. It consists of several interlocking parts:

  • Tech upgrade: switch from Wordpress to Flowershow both to provide a better (faster) experience, to allow for easier contribution and to set us up to add new features going forward (e.g. digital garden)
  • Content consolidate: consolidate and refactor bringing together content from various sites (e.g. tao, ecosystem) into main site and doing a bit tidy and improvement to reflect current activities and make material more accessible
  • Add a new digital garden with a wiki-like where we can publish more informal material and can have community contribution

Underpinning

  • Content migration: migrate content from old site to new site
  • Consolidation: get all our content into one site integrate content from dispersed other sites e.g. tao, sutras, cultural-values
  • Content refactor: refactoring and cleaning up our content to
  • Digital garden section: ...

Key Documents

Acceptance

Migration and integration

Improvements and next steps

Digital garden extra

  • Digital garden improvements e.g. a special theme for this section that flags you are in digital garden and that some things are incomplete
  • /notes/ works and introduces the wiki/garden
  • Section clearly marked as such so people know less polished / developed
    • maybe even mark individual pieces as more or less polished

Maybe

  • Forum??

Inbox (Tasks)

NB: 🚩 thes are not tasks to do so much as inbox. Tasks that are substantial and prioritized move to acceptance and get their own issue.

Content

UX

Misc

  • ➕2023-02-21 add link to facebook in our social media
  • support for posted attribute in front matter (which is url of post on blog or elsewhere)
  • ➕2022-12-18 evaluate forum software and good features of specific ones e.g. ForumMagnum 🚧2022-12-18 see https://app.excalidraw.com/s/9u8crB2ZmUo/16qvtKbcHwg
  • fix all lifeitself.us links to lifeitself.org links (and preferably relative links)
  • Tidy up co-x in notebook
  • clarify what is difference between project/stream and item in notebook (e.g. is co-x a project/stream or just and entry in the notebook)
  • Update notebook/spaces and what it is
  • in merging ecosystem how do we merge stuff
    • what do we do with current content at lifeitself.org/ecosystem? (migrate to markdown and relcoate somehow?) e.g. Move to an old blog post?
    • what do we do with navbar of current site
      • how does sub-navigation within a project work - e.g. does ecosystem get its own navigation (and how does that work)
  • Deprecate https://lifeitself.org/notes/projects/digital-garden-2022 @rufus 💤
    • Process content out of here into A10 or epic?

Ecosystem

Following on from #167 which did basic content migration.

  • How do we want ecosystem to integrate into the main site - is it a separate mini-section or more central. e.g. do we connect with notebook entries on particular orgs. e.g. when writing notes about an org do we put it in ecosystem or in notebook? TODO: write some job stories here ✅2023-02-16 ❌ for now i think we leave things as they are and see how they go
  • what do we do with current content at lifeitself.org/ecosystem? (migrate to markdown and relcoate somehow?) Or move to an old blog post? 🔼 2023-02-16 this is worth doing i think mainly as back-blogging but also some relocation.
  • how do we make editing and contributing super easy? ;
    • could we add commenting perhaps to these pages? ✅2023-02-16 ❌ wontfix. not priority. would be good to have some comment about how to give feedback which is probably just posting on the forum.
  • should ecosystem folder move into the vault? Why? Why not? ✅2023-02-16 my instinct is yes, move this to the vault. no real issue in doing so and it means we can link things more easily. imagine this is cheap to do e.g. ~1h
  • move ecosystem to the vault ⏫ i.e. ecosystem content in vault/ecosystem and images in assets/ecosystem

SEO

  • Submit new site map to Google
  • Update meta descriptions for all pages
  • Alt text for images
  • Add feature images to pages

Tasks archive

Developer oriented phase I

Content (only)

Misc

  • Set up web analytics ✅2022-10-30 add GA4 analytics associated to lifeiteslf.org
  • Consolidate on standard frontmatter e.g. authors or author ✅2022-10-30 go with author and it's an array
  • 404 page (with search if possible like we have today!) ✅ 2023-01-14 Done in PR New 404 page #262

Notes

Why not do the simplest thing possible: nextjs app at root and everything in content? (2022-10-29)

What's the simplest thing possible right now?

  • nextjs app at root
  • content folder is the folder for the site
    • put it in nextjs folder

Why don't we do this? ??

  • Probably don't want everything at root as messy and some stuff will arrive over time that isn't part of the app => have app at e.g. /site/

Questions

  • Do we have books as a subdirectory (or use a type? or use a category link?)
  • Why have tao and garden separate? what's the real difference? ✅2022-10-29 tao is our official guide to community etc whilst garden is more informal and in progress. tao can link to garden and vice-versa.
  • do we want whole site managed in obsidian or have sub-parts that are separate
    • If they are separate how do we deal with linking ...
      • between parts? no easy solution
      • have links even within a part deploy correctly e.g. if tao is it owns vault in obsidian then how do we have links work correctly? Ans: use relative link path formats. Sub-question: how does that work with e.g. assets and excalidraw?
rufuspollock added a commit that referenced this issue Oct 30, 2022
@rufuspollock
[site/config][s]: enable google analytics - refs #170.
052530a
This was referenced Nov 11, 2022
Closed
Closed
@rufuspollock rufuspollock mentioned this issue Nov 11, 2022
Closed
2 tasks
@rufuspollock rufuspollock mentioned this issue Dec 18, 2022
Open
15 tasks
@rufuspollock rufuspollock mentioned this issue Dec 21, 2022
Closed
20 tasks
rufuspollock added a commit that referenced this issue Dec 21, 2022
@rufuspollock
[site,vault,refactor,#170][s]: move few actual markdown content files…
69cd375 
… in site/content/ into vault and then symlink all content from vault into content.

Intention is to consolidate all content in vault. Not simply symlinking all of vault because:

- config.js is still in site/content (maybe we can just move)
- ecosystem is symlinked separately
- components and getters still in site/content (can easily move out components but not sure about getters)
@nathenf nathenf mentioned this issue Dec 23, 2022
Open
34 tasks
@rufuspollock rufuspollock mentioned this issue Jan 4, 2023
Closed
42 tasks
khalilcodes added a commit that referenced this issue Jan 10, 2023
@khalilcodes
[bugfix][components,ecosystem,#170][s]: remove async from useEffect
4d3631b 
* fix bug where page errors out on route change from ecosystem
khalilcodes added a commit that referenced this issue Jan 14, 2023
@khalilcodes
[site/pages,#170][s]: create new 404 page
4f347d5
@khalilcodes khalilcodes mentioned this issue Jan 14, 2023
Merged
@rufuspollock rufuspollock mentioned this issue Feb 2, 2023
Closed
21 tasks
@rufuspollock rufuspollock mentioned this issue Feb 16, 2023
Closed
32 tasks
@rufuspollock
Copy link
Member Author

rufuspollock commented Feb 16, 2023 •
edited

@nathenf i've done quite a bit of refactoring here e.g.

  • split acceptance into groups
  • tasks
    • moved most completed items down into tasks completed
    • created inbox and moved tasks there that aren't prioritized or analyzed (almost all that remained)

Various other stuff: most of this is now tracked as tasks in #334

@nathenf nathenf mentioned this issue Mar 14, 2023
Closed
13 tasks
@nathenf nathenf mentioned this issue Sep 6, 2023
Open
56 tasks
@nathenf
Copy link
Contributor

nathenf commented Oct 3, 2023

FIXED - The main bulk of website work has now be complete. Open tasks have now been merged into our ongoing website issue tracker #454

@nathenf nathenf closed this as completed Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rufuspollock rufuspollock

@nathenf nathenf

@ZybN ZybN

Labels
Epic Roadmap Wiser
Projects
Backlog (All)
Archived in project
Planning - Community
Status: ✅ Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rufuspollock @khalilcodes @nathenf @ZybN