[Snowdrift-dev] connecting model data to the front end with splices
I've heard some questions and concerns about front end development
waiting on back end variables. I can understand why these questions
might arise. The final version of a page's template must use #{..}
splices that get read and compiled to Haskell. The values referred to
in those splices need to really exist for the website to compile, run,
and show values from the database. So, the front end depends on the
back end.
But here's the thing: the back end depends on the front end, too! In
fact, the back end has a *more important* dependency. While the front
end depends on values existing, the back end depends *knowing what
values need to exist*.
The front end is where the requirements flow from. It is closer to the
user, closer to the purpose of the website. The back end only exists
to serve the website's needs.
So, rather than holding up the front end to wait on back end
variables, I think it is much better to use {{placeholderValues}} if
the real values aren't available yet. Then, any new back end values
will definitely be serving a purpose, and won't be a useless waste of
time and resources.
So, don't be afraid to design new pages when the back end values don't
exist yet. Doing so will be better for the project, anyway.
-b
signature.asc
Description: PGP signature
___
Dev mailing list
Dev@lists.snowdrift.coop
https://lists.snowdrift.coop/mailman/listinfo/dev
Re: [Snowdrift-dev] [Snowdrift-design] Preliminary Review of Dashboard Prototype
On 08/05/2017 08:07 AM, Bryan Richter wrote: > On Tue, Aug 01, 2017 at 07:37:59AM -0500, Jason Harrer wrote: >> Not sure how the dev list got removed, but adding it back in at this point. >> >> It sounds like there was consensus on this overall limit (just not project >> limits). That being said, I'm going to open up a ticket on GitLab so we on >> the Dev team can track adding that in. This is a requirement before we can >> get the Dashboard page finished. > > Can you explain why it's a requirement? > > As far as I understand it, the page simply has to say that a limit > exists. > > My point, that I'm making here and elsewhere, is that implementing an > automatic cutoff is not a necessary step for alpha. The process can > remain manual for the time being. > > There are a lot of other manual things I'd rather automate first. > > I agree with Bryan. The requirement is that the limit actually is respected, not that it be in the code per se. Since we face little real-world risk of hitting the limit during alpha and will know for sure if we're approaching it, we're fine. No extra requirement needed for alpha. For beta, it will matter more because people could then pledge to multiple projects and thus approach their limit with fewer patrons in the system. signature.asc Description: OpenPGP digital signature ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev
