bounties
bounties copied to clipboard
rchain
member.site content *Under Construction*
member.site * Under Construction *
Specific: we have a Wordpress instance running for content input. Measurable: the goal is to have the MVP site structure realized as defined in: Short-term: Members Site Achievable: a few activists are working on it, but design and content input are needed. Realistic: end of the month is an appropriate deadline, but the KYC app is an unknown. Timely: improving onboarding is a top priority.
Measure of Completion: MVP site is live Suggested Budget: $5000 (125 collective hours)
Status
Last weekend @dckc and friends got the dev Wordpress site running and configured with a default theme. It's not lovely but perfectly suitable for inputting content. Design mockups can happen in parallel.
There's a YouTube portlet plugin that works great. It pops up an overlay, and that keeps the user in the site. √
Recent changes:
- Nav bar menu configured with the top level links in order
- Fine tuned the sidebar, removed useless elements
- Testing having nav in the sidebar as opposed to a header bar, need another sidebar
- Setup the Support page with content
- Added social media icons menu
- Configured app icon (favicon)
Hi @Barkov-F, at this point we're working on a Minimal Viable Product of the member.site which doesn't include multi-language support.
Personally I don't know anything about the Polylang plugin. Their issue tracker does not inspire confidence: https://wordpress.org/support/plugin/polylang
Calendar
One of the key aspects of the member.site is the Calendar. I'm sure we can find a plugin that'll embed a remote (Google) calendar.
The question could be: which existing calendar do we want to embed? @patrick727?
Or the question is: shall we create a calendar especially for the member.site? It could subscribe to existing calendars and list all events that potential Members might find interesting (e.g. working group meetings). In which case we should prob spin off this issue into its own.
Somebody tell me a story about the calendar? What does the world look like when it's working?
Bonus points for telling the side of the story where material gets added to the calendar as well as when the calendar is read.
I was about to get into technical stuff (i.e. I don't think one Google calendar can subscribe to others) but without some sense of use cases / requirements, there's no way to judge.
As of March 24, we were using Pats take on member.rchain.coop slides to define the MVP. I hope the difference doesn't matter, but I did make a point to be sure all my issues were noted there.
Some progress:
- We have a site hierarchy created that follows the MVP site map.
- The “Get Involved” section is filled in, including embedded video.
Please welcome Maarten van Domburg, aka @Andrekuipers on Github. Maarten is an experienced web developer with Wordpress knowledge and will be pitching in on the setup and theming of the Member site.
In the RAM meeting I got access to a 'main' (for lack of a better word) calendar, so I'll integrate it into the Calendar page.
We also discussed getting the About section fleshed out. For nav purposes we may not want it go too deep, so we might make each sub-page a sort of SPA that contains all the content in sections.
We should continue to develop content in the https://coop-member-v1.rchain.me/ site, @Ojimadu (and anybody else). The content will be selectively migrated to the theming dev site. #615
The top page of About has content now: https://coop-member-v1.rchain.me/?page_id=48 Critique welcome, underlying linked pages not yet.
Was drafting a doc on the about page. I would have to merge this one with mine and reorganize while continuing on other aspects of page.
Status on the 1st of May: we have draft content (i.e. ready for review/improvements) on Home and these top level pages: About, Get Involved. Membership, Support. ToDo is the top level Calendar page which requires a plugin to embed a Google Cal.
Still to be created, both content and layout, are the subpages in About. These subpages will serve as a template for future subpages in Membership, etc.
On weds May 2nd we'll move everything from the dev instance to the rchain.me instance (#615).
Excerpt from a Telegram convo:
kitblake, [02.05.18 07:35] I also want to use 'slugs' (WP jargon) for links, instead of those horrible '?page_id=133' arguments
Ojimadu, [02.05.18 09:17] Lol, yeah, that'll be better.
Today I polished the upper level content, subpages of About are still ToDo.
I'm struggling to make sense of this:
The RChain platform is powered by a Turing complete, byzantine fault-tolerant Rho Virtual Machine
help? I thought the BFT related stuff was in a protocol layer above the VM (casper).
The explainer video on https://coop-member-v1.rchain.me/bounties/ is below the fold... so much of the audience won't see it. Please move it up.
The explainer video has been moved up, above (your) fold. It was visible above mine (on a 1920x1200 monitor).
In #615 @dckc wrote:
In our March 24 MVP, I don't see anything regarding subpages for About. submenus makes me nervous... I guess I should look into this further.
Don't worry about the submenus, they're in stock. WordPress is the Ikea of the web.
@pmoorman @dckc The MVP site structure we're following is in: https://docs.google.com/document/d/1JXM8k-fzf78Y_GbfkDdsekmdeVqqifC4VM0zEMBDxDw/edit Scroll to the end for outline # 3. Items in gray don't have content ready and are not in the MVP.
Anybody have any content for the Member site?
We're almost done and will request that the site gets reviewed before launch, so if you have anything (to add, or to improve) please get on it.
I worked with @kitblake and @Andrekuipers on content today. The MVP is release-ready from a content perspective, but blocked on a few other fronts.
@kitblake will take the lead on resolving subdomain structure / DNS control, and will sync with Patrick about approval & release. (did I miss anything, Kit?)
For now, no new content is needed... although once we're live there are many things that could be improved upon or potentially even tested for better conversions.
Few points that I've made in private chat with @kitblake that are maybe worth recording here (or we might forget):
why do we use all those different CTAs throughout the pages? Sometimes we say "join the coop" then "get involved" then "I'd like to join" and so on.
Shouldn't we stick with a consistent "become a member" (because that's really the next step)?
Of course we also have secondary CTAs like "contact us" or "join the discord", but that's a good idea. Shouldn't we make "contact us" point to Discord more aggressively?
I wonder if the "contact us" link to a support page is going to convert anyone
-
I have another altogether crazy idea (but here we're getting squarely into marketing territory): I wonder how a single long-form page would convert against an entire website. I wouldn't be too surprised if a single long form "sales page" (for lack of a better word) would out-pull this configuration. But this is something to test once we 1) have an MVP up and running and 2) agree on what we'd measure as a success KPI
-
Another idea that I think would work well on the member website are CTAs along the line of "talk to the team" and stuff of that sort. In my opinion RChain is differentiated against other projects for it's openness and inclusiveness: you can easily hang out here in Discord and talk directly to Nash, Medha, Ian and other "key players" whereas in other crypto projects you probably wouldn't have such opportunities.
Great!
I have thought about the first point. Because it is more of a kind of footer that comes back on every page I would keep the text the same everywhere. I think it creates more peace and unity for the user.
Point 4 sounds as a really good selling point for RChain. I think it is a 'must' to show this more on the website. People will trust it more quickly and feel more welcome :)
@pmoorman writes:
... will sync with Patrick about approval & release.
Recall it's @ian-bloom who the executive committee said we need to coordinate with.
For the record, the company descriptions on the Ecosystem page have been approved, by @llerner and GregH and @ leaf/Nash.
@kitblake see Dan's comment above. You check with either Patrick or Ian (or both), right?
...
@Andrekuipers nice let's go for a unified 'footer' then, if we both think that makes sense. What I've said to Kit before (and I still feel the same) is that these changes are more like 'nice to have' than essential to the MVP. Same for idea #4 which I wouldn't classify as a "must" either. This shouldn't delay us in getting the MVP live.
@pmoorman Oke cool!
Before we migrate the website and going live I only need to check if everything is working responsive. I will do that today.
@pmoorman Yes, Patrick is already teaming up for review. I'll be contacting @ian-bloom for the subdomain, but before any infrastructure changes, we want a signoff on the content. Otherwise this could slide into summertime.